As part of our ongoing review of processes around GALA, we have decided to try and make better use of some of the features of the software. We hope that a minor change to our existing review practices will improve the university\u2019s management of compliance with internal and external policies, and help to increase the turnaround of items under review. <\/p>\n\n\n\n
With REF 2021\u2019s submission date only six months away, there has been a not insignificant increase in the number of deposits to GALA. This has been experienced at other institutions, so we are certainly not alone in this. Indeed, we are excited that GALA is being used by a broad range of users, including many who have been recruited throughout 2020. <\/p>\n\n\n\n
However, with the increased volume of deposits comes and increased management of processes. As part of our review of all<\/strong> <\/em><\/strong>deposits into GALA, we perform a range of checks to ensure that the university is not breaching any copyright restrictions (e.g. the sharing of published Versions of Record which publishers have been given copyright of) and to try and support compliance with the university\u2019s Publications Policy, the REF 2021 open access policy, and various research funder policies as applicable. <\/p>\n\n\n\n This disparate range of criteria often require us to contact individual academics via email to clarify that certain aspects of metadata are accurate, or to ensure that the correct document version has been attached to the record. This has been an incredibly effective method and helped us to build and foster excellent working relationships, and to better understand experiences with GALA and research repositories more generally. <\/p>\n\n\n\n However, at scale, moving communications outside of the software can become cumbersome and add delays to the processing of deposits. As such, we are instituting a minor change to our extant\u00a0processes, and\u00a0wanted to\u00a0clearly explain what we are doing and why, hence this blog post.\u00a0<\/p>\n\n\n\n In specific and limited circumstances, we are going to use some functionality in the repository software to return records\u2019 to a user\u2019s work area. We will accompany return of records with a detailed message to explain what needs amending on a given record. For example, if a Version of Record that is under the copyright of the publisher and thus cannot be shared via GALA has been attached to the record, we may explain that you will need to attach your author\u2019s accepted manuscript (AAM,) and where you may be able to obtain your AAM from<\/a> if you do not have a copy to hand, before you re-deposit your record. <\/p>\n\n\n\n Using this function of the software should better enable those depositing records to clarify or amend anything as appropriate in <\/em>sit<\/em>u<\/em>, expediting the process and resolving queries in a more effective way. <\/p>\n\n\n\n Of course, we are always here to support you and ensure that your experiences with open access repositories are positive, so we need to be clear that you can contact us by any means necessary to help resolve any outstanding issues. However, by returning the output to the user\u2019s work area, it will improve efficiency and enable depositors to better understand the requirements of depositing within GALA. <\/p>\n","protected":false},"excerpt":{"rendered":" As part of our ongoing review of processes around GALA, we have decided to try and make better use of some of the features of the software. We hope that a minor change to our existing review …<\/p>\n","protected":false},"author":24,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1],"tags":[25,29,42,49,53],"class_list":["post-544","post","type-post","status-publish","format-standard","hentry","category-uncategorised","tag-gala","tag-green","tag-open-access","tag-process-policy","tag-repositories"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/blogs.gre.ac.uk\/researchandenterprise\/wp-json\/wp\/v2\/posts\/544","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.gre.ac.uk\/researchandenterprise\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.gre.ac.uk\/researchandenterprise\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.gre.ac.uk\/researchandenterprise\/wp-json\/wp\/v2\/users\/24"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.gre.ac.uk\/researchandenterprise\/wp-json\/wp\/v2\/comments?post=544"}],"version-history":[{"count":1,"href":"https:\/\/blogs.gre.ac.uk\/researchandenterprise\/wp-json\/wp\/v2\/posts\/544\/revisions"}],"predecessor-version":[{"id":826,"href":"https:\/\/blogs.gre.ac.uk\/researchandenterprise\/wp-json\/wp\/v2\/posts\/544\/revisions\/826"}],"wp:attachment":[{"href":"https:\/\/blogs.gre.ac.uk\/researchandenterprise\/wp-json\/wp\/v2\/media?parent=544"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.gre.ac.uk\/researchandenterprise\/wp-json\/wp\/v2\/categories?post=544"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.gre.ac.uk\/researchandenterprise\/wp-json\/wp\/v2\/tags?post=544"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}