EuDML interoperability Clause Samples

EuDML interoperability. ‌ When acquiring metadata from different partners, it was observed that any reasonably structured format is rather easily converted to JATS format. The big drawback with many OAI-PMH servers is that they only serve the mandatory OAI-DC format in such a way that many different metadata elements are stored in the same, repeated Dublin Core element. As a consequence, only heuristics based on order of appearance, or pattern matching on an element’s value allows disambiguating the metadata thus contributed. For instance, <identifier> can be used to transport an ISSN, a textual bibliographic reference, a URL, etc. Qualified versions of Dublin Core that are modelled on the metadata schema with finest grain available to the content provider allow faithful interchange of metadata. Qualification can be imbedded into the value of simple Dublin Core elements as in the DML-DC recommendation or similar qualification using URN-like prefixes, or it can use qualified elements and a documented application profile such as SWAP or MLAP. As of writing this report, the best scenario for returning EuDML metadata to providers is to use the EuDML schema over OAI-PMH communication channels. For interoperability and visibility beyond EuDML partners or associated partners, a simple transformation has been developed to represent a subset of EuDML metadata in OAI-DC (compliant with DML-DC) so that general harvesters can manage our metadata. This is available in the OAI-PMH server ▇▇▇▇://▇▇▇▇-▇▇▇▇.▇▇▇-▇▇▇▇▇▇▇▇.▇▇/repox/ OAIHandler. 6 Best practice recommendation for mapping EuDML abstract metadata to the EuDML schema‌ A best practices working group for representing EuDML metadata in JATS notation was formed in Prague: ▇▇▇▇-▇▇▇▇ ▇▇▇▇▇ (chair), ▇▇▇▇▇▇▇ ▇▇▇▇▇▇, ▇▇▇▇▇▇ ▇▇▇▇▇▇▇▇, and ▇▇▇▇▇▇ ▇▇▇▇▇▇▇▇▇▇. A set of recommendations has been derived, and is being tested on large amounts of EuDML items. Complete examples of EuDML XML files obeying these recommend- ations are included as Annex B to this document. The recommendation itself is a work-in-progress, which is available to the project’s partners3 as a live HTML page. When mature enough, it will be placed in an area of the ▇▇▇.▇▇▇▇▇.▇▇ website dedicated to developers’ resources. Up-to-date documentation will be available there for download as well: the specification, the DTDs and possible associated tools. The current content of these recommendations is included as Annex A to this document.