| Support of OAI-PMH Specification in version 2.0 | The OAI interface conforms to the protocol specification version 2.0. (siehe M.A.1-1) |
| Incremental Record Delivery | The OAI interface supports incremental harvesting correctly. |
| Valid e-mail address of administrator (Identify-Verb) | The response for the verb 'Identify' did not specify a valid email address for the repository administrator. |
| Name of the repository | The response for the verb 'Identify' should specify a name for the repository. |
| Description of the repository | The response for the verb 'Identify' should specify a description for the repository. |
| "open_access" set | A setSpec set exists that states ‘open_access’ and contains all metadata records of Open Access documents. (M.A.2-1) |
| set structure specifying ddc categories | A structure exists in accordance with Table 1, and all metadata records – like the documents – are assigned a setSpec according to the table used. (e.g. 'ddc:004') see M.A.2-2 |
| set structure specifying document type | A structure exists in accordance with Table 2, and all metadata records are assigned a setSpec according to the document and publication types. |
| deletion strategy | One of the values ‘persistent’ or ‘transient’ is selected as Deleting Strategy for the data provider. |
| set structure specifying the document status | A set structure exists in accordance with Table 3, and all metadata records are assigned a setSpec according to the documents’ statuses in the publication process. (see R.A.2-1) |
| batch size | The harvest batch size (i. e. the maximum number of data sets in reply to a ListRecords OAI request) is no less than 100 and no more than 500. (see R.A.2-2) |
| resumption token life span | The resumption token’s life span is at least 24 hours. (see R.A.2-3) |
| support of metadata format oai_dc | The metadata format oai_dc needs to be supported. |
| dc:title element | The Dublin Core formatted metadata sets (oai_dc) contain at least the element 'creator'. (see R.A.3-1) |
| dc:date element | The Dublin Core formatted metadata sets (oai_dc) contain at least the element 'date'. (see R.A.3-1) |
| dc:type element | The Dublin Core formatted metadata sets (oai_dc) contain at least the element 'type'. (see R.A.3-1) |
| dc:identifier element | The Dublin Core formatted metadata sets (oai_dc) contain at least the element 'identifier'. (see R.A.3-1) |
| at least one document type | Document or publication types according to the DINI Recommendations Common Vocabulary for Publication and Document Types (Gemeinsames Vokabular für Publikations- und Dokumenttypen) are assigned to all documents. (e.g. 'doc-type:masterThesis', see R.A.3-5) |
| at least one ddc category | Every record contains at least one DNB subject group in a subject element, and the document is listed in that group. (e.g. 'ddc:004'; see R.A.3-6) |
| dc:language format ISO 639-3 | The language element’s content is listed according to ISO 639-3. (see R.A.3-7) |
| dc:date format YYYY-MM-DD | The date element’s content is listed according to ISO 8601. The corresponding format is YYYY-MM-DD. (see R.A.3-8) |
| dc:contributor element | The contributor element is used and contains the name of one person or institution that was involved in the creation of the document described. (see R.A.3-2) |
| dc:source element | The source element follows the Guidelines for Encoding Bibliographic Citation Information in Dublin Core metadata. (see R.A.3-3) |
| dc:relation element
| The relation element is used to name objects that are related to the document described. (see R.A.3-4) |
| dc:subject element | The subject element is used for descriptions of a document’s content. (see R.A.3-5) |
| only one occurrence of dc:date | The date element is used only once in a metadata record. (see R.A.3-6) |
| dc:format with common mime types | The dc:format field should only contain standard MIME types. |
| Provenance-Element (empfohlen) | The element provenance is used in the about container for the individual metadata records that are delivered upon the ListRecords or the GetRecord requests. |