Summary
The PDS DOI Service documentation does not describe:
- How PDS4 XML label fields map to DataCite metadata fields (XPath → DataCite field)
- Which fields are auto-generated by the service vs. which require manual curation
- What default values are applied (publisher, rights, DataCurator contributor, language, etc.)
- Curation guidelines for fields the service cannot populate from the PDS4 label (subjects/UAT keywords,
relatedIdentifiers, dates[Available], ORCIDs when using legacy author_list)
Impact
Discipline node operators have no single reference to understand what metadata will be populated automatically when they submit a PDS4 label, what they are responsible for curating, and what the expected values/formats are. This leads to inconsistent DOI metadata quality across nodes.
Proposed Solution
Add a dedicated documentation page covering:
- A table mapping each DataCite field to its source PDS4 XPath
- A table of auto-generated / hardcoded fields and their values
- Curation guidelines for fields requiring manual input
- Product type mapping table (
product_class → resourceTypeGeneral / resourceType)
- Author mapping details (structured
List_Author vs. legacy author_list)
- Keywords/subjects generation logic
Additional Context
The existing DOI Metadata Guidelines page describes what good metadata looks like, but does not explain how the service translates PDS4 labels into that metadata. These two resources should complement each other.
Summary
The PDS DOI Service documentation does not describe:
relatedIdentifiers,dates[Available], ORCIDs when using legacyauthor_list)Impact
Discipline node operators have no single reference to understand what metadata will be populated automatically when they submit a PDS4 label, what they are responsible for curating, and what the expected values/formats are. This leads to inconsistent DOI metadata quality across nodes.
Proposed Solution
Add a dedicated documentation page covering:
product_class→resourceTypeGeneral/resourceType)List_Authorvs. legacyauthor_list)Additional Context
The existing DOI Metadata Guidelines page describes what good metadata looks like, but does not explain how the service translates PDS4 labels into that metadata. These two resources should complement each other.