CINXE.COM

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en-gb">  <head>  <script async="async" src="https://www.googletagmanager.com/gtag/js?id=UA-3477654-9">// </script> <script> window.dataLayer = window.dataLayer || []; function gtag(){dataLayer.push(arguments);} gtag('js', new Date()); gtag('config', 'UA-3477654-9'); </script> <meta charset="utf-8" /> <meta http-equiv="X-UA-Compatible" content="IE=edge" /> <meta content="width=device-width,initial-scale=1.0" name="viewport" />  <meta content="on" http-equiv="cleartype" />    <link rel="stylesheet" href="/ux.jisc.2.0.0/css/ux.jisc-2.0.0.style.min.css" media="all" /> <link rel="stylesheet" href="/javascript/JavaScript-autoComplete-master/auto-complete.css" />  <script src="/ux.jisc.2.0.0/js/ux.jisc-2.0.0.script-head.min.js">// </script> <meta http-equiv="X-UA-Compatible" content="IE=edge" /> <link rel="icon" href="/favicon.ico" type="image/x-icon" /> <link rel="shortcut icon" href="/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/css/font-awesome.min.css" /> <link rel="stylesheet" href="/style/print.css" media="print" /> <link rel="stylesheet" href="/style/banner.css" media="screen" />  <link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png" />   <link rel="manifest" href="/site.webmanifest" />  <meta name="theme-color" content="#191919" />  <title> Support - Sherpa Services </title> <link rel="Top" href="https://v2.sherpa.ac.uk/" /> <link rel="Sword" href="https://v2.sherpa.ac.uk/sword-app/servicedocument" /> <link rel="SwordDeposit" href="https://v2.sherpa.ac.uk/id/contents" /> <link rel="Search" type="text/html" href="https://v2.sherpa.ac.uk/cgi/search" /> <link rel="Search" type="application/opensearchdescription+xml" href="https://v2.sherpa.ac.uk/cgi/opensearchdescription" title="Sherpa Services" /> <script type="text/javascript"> // <![CDATA[ var eprints_http_root = "https://v2.sherpa.ac.uk"; var eprints_http_cgiroot = "https://v2.sherpa.ac.uk/cgi"; var eprints_oai_archive_id = "v2.sherpa.ac.uk"; var eprints_logged_in = false; var eprints_logged_in_userid = 0; var eprints_logged_in_username = ""; var eprints_logged_in_usertype = ""; // ]]></script> <style type="text/css">.ep_logged_in { display: none }</style> <link rel="stylesheet" type="text/css" href="/style/auto-3.4.4.css?1718105074" /> <script type="text/javascript" src="/javascript/auto-3.4.4.js?0"> //padder </script>  <meta name="Generator" content="EPrints 3.4.4" /> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> <meta http-equiv="Content-Language" content="en" /> </head> <body> <header class="masthead" role="banner" data-mobilemenu=""> <div class="masthead__top"> <div class="inner"> <a id="skiplinks" class="visuallyhidden focusable in-page" href="#main" tabindex="1"> <span>Skip to main content</span> </a> <a class="masthead__logo" href="https://www.jisc.ac.uk"> <img alt="Jisc logo" src="/ux.jisc.2.0.0/logo.png" /> </a> </div> </div> <div class="masthead__main masthead__main--with-content masthead__main--opendoar"> <div class="inner"> <div id="new-opendoar-banner" class="new-opendoar-banner"> <div> <p class="banner-title">OpenDOAR will be moving!</p> <p>Our new site is launching soon. We'll redirect you, so you won't have to do anything.</p> </div> <img src="/img/OPENDOAR_image.png" alt="Illustration of two people using the OpenDOAR service" /> </div> <p class="masthead__title masthead__title--short"> <a href="/opendoar/">OpenDOAR</a> </p> <div class="nav-wrapper"> <nav class="masthead__nav header__nav--primary" role="navigation" data-dropdown=""> <ul> <li class="nav__item" id="nav_about_tab"> <a href="https://v2.sherpa.ac.uk/opendoar/about.html">About</a> </li> <li class="nav__item" id="nav_search_tab"> <a href="https://v2.sherpa.ac.uk/opendoar/search.html">Directory</a> </li> <li class="nav__item" id="nav_policytool_tab"> <a href="https://v2.sherpa.ac.uk/opendoar/policytool/">Support</a> </li> </ul> </nav> <nav class="masthead__nav masthead__nav--secondary" id="nav_admin_tab"> <ul> <li class="nav__item" id="nav_contact_tab"> <a href="https://v2.sherpa.ac.uk/opendoar/contact.html">Contact</a> </li>  </ul> </nav> </div> </div> </div> </header> <main id="main" role="main" class="main"> <div class="inner l-pull-left featured"> <div class="l-centre-offset" style="min-height: 300px"> <div class="row"> <h1 class="h1_like_h2"> Support </h1> <div class="static-page"> <p>Repositories are a key facilitator for discovering pre-print research outputs. The technical requirements put forward in Plan S serve to ensure repositories work towards excellent standards to represent the research they hold in the best way possible.</p> <section class="is-collapsible show_hide__container is-collapsible--button show_hide--is-collapsed" data-collapsible=""> <h3 class="show_hide__trigger"> What are the six Plan S repository requirements? </h3> <div class="show_hide__target"> <p>The six Plan S repository requirements are:</p> <ul class="policy-list-sections"> <ul class="policy-list-items"> <li>The repository must be registered in OpenDOAR or in the process of being registered. </li> <li>Use <strong>of persistent identifiers (PIDs)</strong> for the deposited versions of the publications (with versioning, for example in case of revisions), such as DOI (preferable), URN, or Handle. </li> <li><strong>High quality article level metadata</strong> in standard interoperable non-proprietary format, under a CC0 public domain dedication. This must include information on the DOI (or other PIDs) both of the original publication and the deposited version, on the version deposited (AAM/VoR), and on the Open Access status and the licence of the deposited version. Metadata must include complete and reliable information on funding provided by cOAlition S funders (including as a minimum the name of the funder and the grant number/identifier). </li> <li><strong>Machine readable information</strong> on the <strong>open access status</strong> and the <strong>license</strong> embedded in the article, in standard non-proprietary format. </li> <li><strong>Continuous availability</strong> (uptime at least 99.7%, not taking into account scheduled downtime for maintenance or upgrades). </li> <li><strong>Helpdesk:</strong> as a minimum an email address (functional mailbox) has to be provided; a response time of no more than one business day must be ensured. </li> </ul></ul> <p><i>Source: Source: cOAlition S "Part III: Technical Guidance and Requirements": </i> <a href="https://www.coalition-s.org/technical-guidance_and_requirements/">https://www.coalition-s.org/technical-guidance_and_requirements/</a></p> </div> </section> <h2>Assessing your repository against the requirements </h2> <section class="is-collapsible show_hide__container is-collapsible--button show_hide--is-collapsed" data-collapsible=""> <h3 class="show_hide__trigger"> Is your repository registered, or in the process of being registered, in OpenDOAR?</h3> <div class="show_hide__target"> <p>OpenDOAR is the global Directory of Open Access Repositories where repositories can register for free, provided they meet the eligibility criteria. All the details and guidance can be found on the OpenDOAR website.</p> </div> </section> <section class="is-collapsible show_hide__container is-collapsible--button show_hide--is-collapsed" data-collapsible=""> <h3 class="show_hide__trigger"> Are persistent identifiers (PIDs) used for deposited versions of the items (with versioning, for example in case of revisions)? </h3> <div class="show_hide__target"> <p>A persistent identifier, or 'PID', is a unique, long-lasting reference to a digital object. PIDs are an effective way of finding and connecting information from different sources. A PID for the deposited version of a publication refers to the PID associated with the item in the repository. These PIDs can be generated by repository software platforms in the form of 'Digital Object Identifiers' (DOIs), URLs or Handles. The PIDs in use should comply with the requirements of that selected PID scheme. </p> </div> </section> <section class="is-collapsible show_hide__container is-collapsible--button show_hide--is-collapsed" data-collapsible=""> <h3 class="show_hide__trigger"> Does the repository provide high quality article level metadata?</h3> <div class="show_hide__target"> <p>Article level metadata (ALM) refers to the metadata of deposited items in the repository. High quality ALM is necessary to enhance discovery, reproducibility and system interoperability. A number of different metadata standards are in use across repositories, e.g. RIOXX and DataCite. Plan S does not specify a standard that the repository must use, in favour of institutional and community approaches. ALM is likely to include descriptive metadata, such as the title and abstract, a subject or keywords, language, information about versions, attribution to authors and organisations, any licence or embargo restrictions, and any relations to other works or research outputs, e.g. citations. </p> </div> </section> <section class="is-collapsible show_hide__container is-collapsible--button show_hide--is-collapsed" data-collapsible=""> <h3 class="show_hide__trigger"> Is the metadata available in a standard interoperable non-proprietary format?</h3> <div class="show_hide__target"> <p>Metadata is structured information that helps you to manage and communicate research outputs, but the structures in your repository may not match the structures used by others. That can make it harder to communicate your data, making it less findable, accessible, interoperable and reusable (FAIR). To solve this problem communities have developed standards for metadata, but these standards are only effective for interoperability if they are open and people are permitted to use them and map between them. Examples of open standards for metadata are: RIOXX, Dublin Core, MARCXML, DataCite, JSON-LD (Schema.org). </p> </div> </section> <section class="is-collapsible show_hide__container is-collapsible--button show_hide--is-collapsed" data-collapsible=""> <h3 class="show_hide__trigger"> Is the metadata available under a CC0 public domain dedication? </h3> <div class="show_hide__target"> <p><a href="https://creativecommons.org/share-your-work/public-domain/cc0/">CC0 is a 'no rights reserved', public domain licence</a> created by Creative Commons. CC0 enables researchers, educators, artists and other creators and owners of copyright- or database-protected content to waive those interests in their works and thereby place them as completely as possible in the public domain, so that others may freely build upon, enhance and reuse the works for any purposes without restriction under copyright or database law. This is in contrast to Creative Commons' other licences that allow copyright holders to choose from a range of permissions while retaining their copyright, CC0 provides the choice to opt out of copyright and database protection, and the exclusive rights automatically granted to creators. </p> </div> </section> <section class="is-collapsible show_hide__container is-collapsible--button show_hide--is-collapsed" data-collapsible=""> <h3 class="show_hide__trigger"> Does the metadata include complete and reliable information on funding provided by cOAlition S funders? </h3> <div class="show_hide__target"> <p>The inclusion of funding metadata enables transparency into research funding and its outcomes. It is good practice for authors to acknowledge support for, and contributions to, their research in their published articles. This support may be financial, such as a grant or salary award; or practical, such as the use or loan of specialist facilities and equipment. They do this by listing the funding agency and the grant number somewhere in their article - usually the first or last page - or in the acknowledgments or footnotes section. This should also be included in the metadata so that anyone can make connections, for example, to identify which funders invest in certain fields of research. Funding data is also used by funders to track the publications that result from their grants. </p> </div> </section> <section class="is-collapsible show_hide__container is-collapsible--button show_hide--is-collapsed" data-collapsible=""> <h3 class="show_hide__trigger"> Is machine readable information on the licence and open access status embedded in the article available in standard non-proprietary format? </h3> <div class="show_hide__target"> <p>Machine-readable information refers to data that is in a suitable format that can be processed by a computer. In the context at hand, this information would enable a computer to automatically determine the licence attributed to an article as well as the open access status. </p> </div> </section> <section class="is-collapsible show_hide__container is-collapsible--button show_hide--is-collapsed" data-collapsible=""> <h3 class="show_hide__trigger"> Does the repository have continuous availability? </h3> <div class="show_hide__target"> <p>Repositories should minimise unscheduled downtime as much as possible. They should aim towards at least 99.7% uptime which equates to an approximate maximum of 27 hours unscheduled service outage per year. This does not include scheduled downtime for maintenance and upgrades.</p> </div> </section> <section class="is-collapsible show_hide__container is-collapsible--button show_hide--is-collapsed" data-collapsible=""> <h3 class="show_hide__trigger"> Does your repository have a helpdesk? </h3> <div class="show_hide__target"> <p>Repositories must provide a channel for depositors and other users to submit queries. cOAlition S does not specify what format of contact is adopted as the repository should identify the most suitable channel for their workflows and resource. A helpdesk could constitute an email address, a telephone number, an online contact form, a ticket management system, and so on. The initial response to a query, should be sent no more than one business day from receipt. This response may comprise an automated holding note that gives an indication of when the enquirer can expect to receive a more fulsome response. </p> </div> </section> <br /> <h3>What happens if my repository does not meet the Plan S criteria? </h3> <p>The above guidance is intended to help you work towards meeting the requirements over time. If you are unable to meet a requirement, cOAlition S encourages you to find a suitable solution that is possible within the remit of the resource available to you. </p> <h3>Can we use the guidance to assess our CRIS? </h3> <p>Yes. If you use the CRIS as a repository and it provides open access to full-text items, then it is an eligible candidate for assessment. </p> <h2>Policy Support</h2> <p>Repositories play a key role in the publication lifecycle. They provide a stable platform for research outputs and are often referenced on funders' open access policies. Having a clear understanding of how repository content should be treated promotes effective usage enabling repository staff, authors, data harvesters, and the wider academic community to get the most out of repositories.</p> <h3>What should be covered?</h3> <p>Clear policy information encourages a standardised level of service, it sets users' expectations, and helps increase impact and visibility of research. We have identified five core policy areas that satisfy best practice for open access compliance:</p> <ul> <li><strong>Metadata Policy</strong> stating the access rights and permissions for information describing items in the repository, and the minimum metadata requirements.</li> <li><strong>Data Policy</strong> stating the access rights and (re-)use permissions for full-text and other full data items.</li> <li><strong>Content Policy</strong> stating the types and versions of documents and datasets held.</li> <li><strong>Submission Policy</strong> concerning eligible depositors, quality control and copyright statements.</li> <li><strong>Preservation Policy</strong> concerning the long-term retention, migration, and withdrawal protocols.</li> </ul> <h3>Repository policy statements</h3> <p>To help you, we have developed two general policy statements based on industry standards to encourage good practice across the community. The policy statements are available in different formats for inclusion on your repository website or documentation.</p> <section class="is-collapsible show_hide__container is-collapsible--button show_hide--is-collapsed" data-collapsible=""> <h3 class="show_hide__trigger"> Open access repository policy (minimum recommended) </h3> <div class="show_hide__target"> <p>This is the recommended option for minimum open access compliance. It encourages open access yet holds restrictions, such as allowing re-use of metadata for not-for-profit purposes, but prohibits commercial re-use.</p> <ul class="policy-list-sections"> <li><strong>Metadata Policy</strong> (for information describing items in the repository) <ul class="policy-list-items"> <li>Anyone may access the metadata free of charge.</li> <li>The metadata may be re-used in any medium without prior permission for not-for-profit purposes provided the OAI Identifier or a link to the original metadata record are given.</li> <li>The metadata must not be re-used in any medium for commercial purposes without formal permission.</li> </ul> </li> <li><strong>Data Policy</strong> (for full-text and other full data items) <ul class="policy-list-items"> <li>Anyone may access full items free of charge.</li> <li>Single copies of full items can be reproduced, and displayed or performed in any format or medium for personal research or study, educational, or not-for-profit purposes without prior permission or charge.</li> <li>Full items must not be sold commercially in any format or medium without formal permission of the copyright holders.</li> </ul> </li> <li><strong>Content Policy</strong> (for document types and datasets) <ul class="policy-list-items"> <li>This is an institutional or departmental repository OR Multi-institution subject-based repository [list subjects]:</li> <li>The repository holds all types of items OR The repository only permits the following item types [list]</li> <li>All items are individually tagged with their peer-review status and publication status.</li> </ul> </li> <li><strong>Submission Policy</strong> (concerning depositors, quality and copyright) <ul class="policy-list-items"> <li>Items may only be deposited by accredited members of the organisation, or their delegated agents.</li> <li>Authors may only submit their own work for archiving.</li> <li>The administrator only vets items for the exclusion of spam</li> <li>The validity and authenticity of the content of submissions is the sole responsibility of the depositor.</li> <li>Items may not be deposited until any publishers' or funders' embargo period has expired.</li> <li>Any copyright violations are entirely the responsibility of the authors/depositors.</li> <li>If the repository receives proof of copyright violation, the relevant item will be removed immediately.</li> </ul> </li> <li><strong>Preservation Policy</strong> <ul class="policy-list-items"> <li>Items will be retained indefinitely.</li> <li>The repository will try to ensure continued readability and accessibility.</li> <li>The repository regularly backs up its files according to current best practice.</li> <li>Items may not normally be removed from the repository.</li> <li>Acceptable reasons for withdrawal include: <ul> <li>Proven copyright violation or plagiarism</li> <li>Legal requirements and proven violations</li> <li>National Security</li> <li>Falsified research</li> </ul></li> <li>Withdrawn items are not deleted per se, but are removed from public view.</li> <li>Withdrawn items' identifiers/URLs are retained indefinitely.</li> <li>URLs will continue to point to 'tombstone' citations, to avoid broken links and to retain item histories.</li> <li>Changes to deposited items are not permitted.</li> <li>If necessary, an updated version may be deposited.</li> <li>In the event of the repository being closed down, the database will be transferred to another appropriate archive.</li> </ul> </li> </ul> <ul class="policy-downloads"> <li><a href="minimum-policy.html">View policy HTML</a></li> <li><a href="minimum-policy.txt">View policy plain text</a></li> </ul> </div> </section> <section class="is-collapsible show_hide__container is-collapsible--button show_hide--is-collapsed" data-collapsible=""> <h3 class="show_hide__trigger"> Open access repository policy (optimum recommended) </h3> <div class="show_hide__target"> <p>This is the recommended option for optimum open access compliance. It encourages unrestricted open access, such as allowing free commercial re-use which offers the listed material extra exposure.</p> <ul class="policy-list-sections"> <li><strong>Metadata Policy</strong> (for information describing items in the repository) <ul class="policy-list-items"> <li>Anyone may access the metadata free of charge.</li> <li>The metadata may be re-used in any medium without prior permission for not-for-profit purposes and re-sold commercially provided the OAI Identifier or a link to the original metadata record are given.</li> </ul></li> <li><strong>Data Policy</strong> for full-text and other full data items <ul class="policy-list-items"> <li>Anyone may access full items free of charge.</li> <li>Copies of full items generally can be:</li> <li>reproduced, displayed or performed, and given to third parties in any format or medium</li> <li>for personal research or study, educational, or not-for-profit purposes without prior permission or charge.</li> <li>provided:<ul> <li>the authors, title and full bibliographic details are given</li> <li>a hyperlink and/or URL are given for the original metadata page</li> <li>the content is not changed in any way</li> </ul></li> <li>Full items must not be sold commercially in any format or medium without formal permission of the copyright holders.</li> </ul></li> <li><strong>Content Policy</strong> (for document types and datasets) <ul class="policy-list-items"> <li>This is an institutional or departmental repository OR Multi-institution subject-based repository [list subjects]:</li> <li>The repository holds all types of items OR The repository only permits the following item types [list]</li> <li>Items are individually tagged with their version type and date; their peer-review status; and their publication status.</li> </ul></li> <li><strong>Submission Policy</strong> concerning depositors, quality & copyright <ul class="policy-list-items"> <li>Items may only be deposited by accredited members of the organisation, or their delegated agents.</li> <li>Authors may only submit their own work for archiving.</li> <li>The administrator only vets items for the eligibility of authors/depositors, relevance to the scope of the repository, valid layout & format, and the exclusion of spam</li> <li>The validity and authenticity of the content of submissions is the sole responsibility of the depositor.</li> <li>Items can be deposited at any time, but will not be made publicly visible until any publishers' or funders' embargo period has expired.</li> <li>Any copyright violations are entirely the responsibility of the authors/depositors.</li> <li>If the repository receives proof of copyright violation, the relevant item will be removed immediately.</li> </ul></li> <li><strong>Preservation Policy</strong> <ul class="policy-list-items"> <li>Items will be retained indefinitely.</li> <li>The repository will try to ensure continued readability and accessibility.</li> <li>Items will be migrated to new file formats where necessary.</li> <li>Where possible, software emulations will be provided to access un-migrated formats.</li> <li>The repository regularly backs up its files according to current best practice.</li> <li>The original bit stream is retained for all items, in addition to any upgraded formats.</li> <li>Items may not normally be removed from the repository.</li> <li>Acceptable reasons for withdrawal include:<ul> <li>Proven copyright violation or plagiarism</li> <li>Legal requirements and proven violations</li> <li>National Security</li> <li>Falsified research</li> </ul></li> <li>Withdrawn items are not deleted per se, but are removed from public view.</li> <li>Withdrawn items' identifiers/URLs are retained indefinitely.</li> <li>URLs will continue to point to 'tombstone' citations, to avoid broken links and to retain item histories.</li> <li>Changes to deposited items are not permitted.</li> <li>Errata and corrigenda lists may be included with the original record if required.</li> <li>If necessary, an updated version may be deposited.</li> <li>In the event of the repository being closed down, the database will be transferred to another appropriate archive.</li> </ul></li> </ul> <ul class="policy-downloads"> <li><a href="optimum-policy.html">View policy HTML</a></li> <li><a href="optimum-policy.txt">View policy plain text</a></li> </ul> </div> </section> </div> </div> </div> </div> </main> <footer role="contentinfo">  <div class="inner l-pull-left light l-gutter--top"> <div class="l-centre-offset row"> <div class="col span-4"> <div class="linklist l-gutter--right"> <div class="linklist__title">Useful links</div> <ul> <li class="linklist__item"><a href="https://www.jisc.ac.uk/guides?f%5B0%5D=field_project_topics%3A455&topic=9">Open access guides by Jisc</a></li> </ul> </div> </div> <div class="col span-4"> <div class="linklist l-gutter--right"> <div class="linklist__title">Contact</div> <a href="mailto:help@jisc.ac.uk">help@jisc.ac.uk</a> </div> </div> <div class="col span-4"> <div class="linklist l-gutter--right"> <div class="linklist__title">Accessibility</div> <a href="/opendoar/accessibility.html">Accessibility Statement</a> </div> </div> </div> </div>  <div class="inner l-pull-left medium bottom-section"> <div class="l-centre-offset row"> <div class="col span-12"> <div class="l-gutter--right"> <div class="divisional-info"> <div class="divisional-info__side"> <a href="https://jisc.ac.uk"> <img alt="Jisc logo" src="/ux.jisc.2.0.0/jisc-logo.png" width="158" height="93" /> </a> </div> <div class="divisional-info__body"> <div class="linklist__title">Open research</div> <p>Removing barriers, embedding open practices and developing open infrastructure.</p> <p><a href="https://www.jisc.ac.uk/open-research">Find out more at jisc.ac.uk/open-research</a></p> </div> </div> </div> </div> </div> </div>  <div class="inner l-pull-left heavy"> <div class="l-centre-offset row cc-wrap"> <div class="cc media-object"> <div class="media-object__media"> <a rel="license" href="http://creativecommons.org/licenses/by-nc-nd/4.0/"> <img src="/img/by-nc-nd.png" alt="License" /> </a> </div> <div class="media-object__body">  <span class="print-only">漏2017 Jisc.</span> This work is licensed under the <a class="cc__link" rel="license" href="http://creativecommons.org/licenses/by-nc-nd/4.0/">CC BY-NC-ND 4.0</a><br /> <span class="cc"><a class="cc__link" id="about-our-content" href="https://www.jisc.ac.uk/website/copyright?loc=cc">About using our content</a></span> </div> </div> </div> </div> </footer> <script src="/ux.jisc.2.0.0/js/ux.jisc-2.0.0.script-foot.min.js">// </script> <script src="/javascript/JavaScript-autoComplete-master/auto-complete.min.js">// </script> <script>jQuery.noConflict()</script> <script src="/javascript/select_tab.js">// </script> <script src="/javascript/search_field_autocomplete.js">// </script> </body> </html>