during the last week I’ve implemented the importer/exporter tool according to our recommendations for the KIT Data Manager platform. In the meantime, David figured out that the SWORD people are also referring to our recommendations with the difference that they skip the requirement of datacite.xml. After a short discussion in their profile working document  it seems that the main reason is the necessity of a DOI. Obviously, using machine-recognizable codes as stated under ‘Guidance for handling missing mandatory property values’ in  applies to all mandatory properties but the identifier as the schema defined a fixed regular expression with the value 10\..+/.+ for this element. Thus, datacite documents using placeholders for the identifier won’t validate against the schema.
The question is now how we proceed. I see two options:
We ignore the fact that datacite documents without DOI can’t be validated and add a comment to our recommendations saying it is allowed (but of course not advised) to add ‘invalid’ datacite documents, but in that case, there should be an alternateIdentifier of type INTERNAL that can be used by the consumer of the bag.
We switch to another standard for providing our minimal metadata set, e.g. DataCrate.
What is your opinion on that? Do you see a third option?
Karlsruhe Institute of Technology (KIT)
Steinbuch Centre for Computing (SCC)
Dipl. Ing. Thomas Jejkal
76344 Eggenstein-Leopoldshafen, Germany
Phone: +49 721 608-24042
Registered office: Kaiserstraße 12, 76133 Karlsruhe, Germany
KIT – The Research University in the Helmholtz Association