{"id":7782,"date":"2021-04-22T15:29:17","date_gmt":"2021-04-22T19:29:17","guid":{"rendered":"https:\/\/blogs.mathworks.com\/community\/?p=7782"},"modified":"2021-04-22T15:29:17","modified_gmt":"2021-04-22T19:29:17","slug":"on-the-importance-of-software-to-research","status":"publish","type":"post","link":"https:\/\/blogs.mathworks.com\/community\/2021\/04\/22\/on-the-importance-of-software-to-research\/","title":{"rendered":"On the Importance of Software to Research"},"content":{"rendered":"

This week's post is by Mike Croucher. Mike is a member of the Customer Success Engineering team in the UK, working with academics around the country on their teaching and computational research. Mike has been a supporter of the Research Software Engineering movement since its inception and co-founded one of the first RSE groups in the UK. You can find Mike on Twitter (Mike Croucher (@walkingrandomly) \/ Twitter<\/a>) and LinkedIn (Mike Croucher | LinkedIn<\/a>)<\/em><\/p>\n

On the Importance of Software to Research<\/h2>\n

by Mike Croucher<\/em><\/p>\n

Anyone who has worked around academia for a long time will tell you that there are many roles in academic research that are vital-but-unrecognised.\u00a0 Software development used to be one of them!\u00a0 Back in 2012, a group of people decided to change this situation and created what has since become the Research Software Engineering (RSE) movement<\/a>. As I can personally attest, this movement has been a game changer for those of us who contribute most through research software rather than journal writing.\u00a0 Our place in the academic world now has a name, a career structure, fellowship opportunities, an international association and more.<\/p>\n

RSEs used to be relatively invisible in academia, a situation that wasn\u2019t helped by the fact that there used to be 200 different job titles<\/a> for what we now call Research Software Engineer.\u00a0 Much of the early work of the research software engineering pioneers was data collection. Conducting surveys, parsing through thousands of job adverts looking for mention of software development, reading through large numbers of papers looking for discussion of supporting software and so on.<\/p>\n

Step by step, the data revealed a story that could not be denied -- software is important to research and so are those who write it.<\/p>\n

The need for data collection continues<\/b><\/h3>\n

We are far from finished. While the importance of research software is better recognised than ever, it still lags far behind the almighty \u2018paper\u2019 in the pantheon of research outputs. Furthermore, can we repeat the RSE success story for other contributors such as technicians, librarians and research managers.\u00a0 Are there other vital-but-unrecognised roles that should be brought into the light and given better support and recognition?<\/p>\n

The Research Excellence Framework (REF)<\/a> is the official system for assessing the quality of research in UK Higher Education Institutions. Academics across the country are asked to submit their best research outputs out of 20 different categories and this leads to ranking the research quality of all institutions in the UK.\u00a0 These categories include the obvious such as \u2018Journal articles\u2019 and \u2018Book Chapters\u2019 but also things as diverse as \u2018Devices and products\u2019, \u2018Compositions\u2019 and, my personal favourite as a Research Software Engineer, \u2018Software\u2019.<\/p>\n

In practice, however, journal articles reign supreme. In the previous REF around 97% of all submissions were based on publications (data here<\/a>).\u00a0 Software submissions were so low that you can\u2019t even see them on a chart! The net effect of this is that you are officially only considered a good contributor to research if you\u2019ve published a lot of good papers. Everything else is just noise.<\/p>\n

\"\"<\/p>\n

What\u2019s needed is more data about all of the outputs that are not publications and this is where the UK\u2019s Hidden REF<\/b><\/a> comes in.\u00a0 Brought to you by some of the same team behind the Research Software Engineering campaign, the Hidden REF aims to bring these hidden contributions to the surface. The Hidden REF has many categories<\/a> including training materials and courses<\/b>, enabling access to facilities<\/b> and, of course software<\/b>.\u00a0 Possibly the most exciting, however, is the Hidden Role, <\/b>a placeholder for \u2018Stuff we didn\u2019t even realise was important and we need your help in finding it\u2019.\u00a0 Only one type of research output is forbidden -- publications!<\/p>\n

Since this is a MATLAB blog, I encourage anyone in the UK who has made a contribution to the File Exchange to write up how their software has positively impacted research and submit to the Hidden REF. Once you\u2019ve done that, forward this article to your technicians, librarians, facility managers and anyone else who you think should have their story told. We all know some unsung hero without whom our research would be impossible -- participating in the Hidden REF will allow them, and those like them, to be recognised which is the first step to being better supported.<\/p>\n

To enter Hidden REF (Note: you need to be affiliated with a UK based institution<\/strong>), head over to https:\/\/hidden-ref.org\/submission-and-review-process\/<\/a> and write a simple summary of the output of no more than 300 words in length. The deadline for submission is 14th May 2021.<\/p>\n

Researchers outside of the UK are not eligible to enter but if you\u2019d like to tell your story anyway, I\u2019d love to hear it so feel free to post a comment here.<\/p>\n","protected":false},"excerpt":{"rendered":"

<\/div>\n

This week's post is by Mike Croucher. Mike is a member of the Customer Success Engineering team in the UK, working with academics around the country on their teaching and computational research. Mike... read more >><\/a><\/p>\n","protected":false},"author":69,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"_links":{"self":[{"href":"https:\/\/blogs.mathworks.com\/community\/wp-json\/wp\/v2\/posts\/7782"}],"collection":[{"href":"https:\/\/blogs.mathworks.com\/community\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.mathworks.com\/community\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.mathworks.com\/community\/wp-json\/wp\/v2\/users\/69"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.mathworks.com\/community\/wp-json\/wp\/v2\/comments?post=7782"}],"version-history":[{"count":3,"href":"https:\/\/blogs.mathworks.com\/community\/wp-json\/wp\/v2\/posts\/7782\/revisions"}],"predecessor-version":[{"id":7790,"href":"https:\/\/blogs.mathworks.com\/community\/wp-json\/wp\/v2\/posts\/7782\/revisions\/7790"}],"wp:attachment":[{"href":"https:\/\/blogs.mathworks.com\/community\/wp-json\/wp\/v2\/media?parent=7782"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.mathworks.com\/community\/wp-json\/wp\/v2\/categories?post=7782"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.mathworks.com\/community\/wp-json\/wp\/v2\/tags?post=7782"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}