Editing Plan S (section)

=== Mandatory technical conditions for all publication venues ===

A1. Use of persistent identifiers (PIDs) for scholarly publications (with versioning, for example, in case of revisions), such as DOI (preferable), URN, or Handle.
* EPrints provides an ''Identification number'' (''id_number'') field to store DOIs as well as other PIDs such as PubMed ID, etc.  There are also separate fields for storing ISSNs and ISBNs.
* Each publication record in EPrints is assigned is own URI in the format: ''http://HOSTNAME/id/eprint/NUMBER'', (e.g. http://eprints.example.org/id/eprint/1234 ).
* There are plans to introduce a IDs, IDs, IDs Bazaar plugin similar to the [http://bazaar.eprints.org/449/ Dates, Dates, Dates] that will allow multiple PIDs to be stored with their types to make recording PIDs more extensible.

A2. Deposition of content with a long-term digital preservation or archiving programme (such as CLOCKSS, Portico, or equivalent).

A3. High-quality article level metadata in standard interoperable non-proprietary format, under a CC0 public domain dedication. 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).
* EPrints most comprehensive metadata export format is its EP3 XML for which an XML schema for any particular archive is available at /cgi/schema to support interoperability.  EPrints also provides metadata export in many other standard interoperable non-proprietary format such as:  BibTeX, EndNote, CSV, JSON, Dublin Core, RDF to name but a few.  EPrints is extensible to allow repository maintainers to add additional export plugins as necessary.
** For repositories connected to other data sources (e.g. CRIS systems, or paid-for services) the 'CC0' aspect may require a metadata profile that excludes some information such as abstracts, subjects or keywords.

[[Plan S - A4 - Embedding data into an article|A4]]. Machine-readable information on the Open Access status and the license embedded in the article, in standard non-proprietary format.
* EPrints generates a ''full_text_status'' value by analysing the content of a publication record to determine whether this value should be: ''none'', ''public'' or ''restricted''.  Each document added to a publication record can be assign a license from a list of available options.  Both metadata values are shown in the machine-readable EP3 XML export format and can be used.
** The page [[Plan S - A4 - Embedding data into an article]] contains details of some possible approaches to this requirement.