Editing Plan S (section)

=== Mandatory criteria for repositories ===

C1. Use of PIDs for the deposited versions of the publications (with versioning, for example in case of revisions), such as DOI (preferable), URN, or Handle.
* Same as A1, see above.
* Clarification is provided in the [https://www.coalition-s.org/faq-theme/technical-requirements/ Plan S FAQs]: 
** Q: Does the Author’s Accepted Manuscript (AAM) of an article deposited into an institutional repository have to have a DOI assigned to it?
** A: For cOAlition S articles all AAMs in repositories must have a unique persistent identifier (PID) assigned to them. 


C2. High quality article level metadata 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 license 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).
* Mostly the same as A3, see above.
* With regard to deposited version the ''Content'' field for a document within a publication record can store version of the file such as: ''Draft Version'', ''Submitted Version'', ''Accepted Version'',  ''Published Version'', etc.  This field could be modified to use the values such as AAM, VoR, etc.  
** The [http://bazaar.eprints.org/1113/ REF Compliance Checker for EPrints] Bazaar plugin provides a mapping from EPrints standard content version for documents to the standardised Open Access versions like VoR and AAM.
* With regard to funder information, by default EPrints provides a field a ''Funders'' field that can indiviually store multiple different funders entered free-hand.
** The [http://bazaar.eprints.org/390/ RIOXX2] Bazaar plugin provides more detailed entry to submit the project ID (i.e. grant reference) and the funders name and ID (as a DOI or ISNI ID).

C3. Machine readable information on the Open Access status and the license embedded in the article, in standard non-proprietary format.
* Same as A4, see above.

C4. Continuous availability (uptime at least 99.7%, not taking into account scheduled downtime for maintenance or upgrades).
* EPrints cannot be responsible for the maintenance of the infrastructure on which it runs.  However, EPrints has been demonstrated as stable software over a number of years and should not fail and lead to unscheduled downtime in normal circumstances.

C5. Helpdesk: 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.
* By default EPrints requires an admin email address to be set its configuration and this address can be found on the About page of the repository linked off EPrints default main menu.
* EPrints cannot provide any guarantees that the email address has a functional mailbox, as that is the responsibility of the organisation managing the repository.