torrin47
commented
1 year ago Yes, and...
contactPoint is implemented in the DCAT-US schema by means of the vCard specification, which has an optional UID element that would be a good fit for ORCID and easy to implement. Documented here: https://github.com/USEPA/EPA_Environmental_Dataset_Gateway/issues/19 and here: https://github.com/project-open-data/project-open-data.github.io/issues/614
publisher would need more work to accommodate RORs, but agree fully with the value proposition.
Other important persistent identifiers, such as DOIs and PMCIDs supporting linked open data principles, are often dumped into the "references" array with no additional context. Suggest that any URI or other persistent identifier in DCAT-US be allowed to include an associated human-readable description of what the URI represents and potentially a reference to an issuing authority as described here: https://www.w3.org/TR/vocab-dcat-3/#identifiers-type Lots more discussion on this topic over here: https://github.com/project-open-data/project-open-data.github.io/issues/592 https://github.com/project-open-data/project-open-data.github.io/issues/69
fellahst
ShaferAC
mrratcliffe
leightonlc
Leighton Christiansen National Transportation Library, USDOT
Requirement(s)
Metadata fields that record information about Organizations and People should also record one or more persistent identifiers for that entity. publisher: should include subfields for "identifier" and "identifierType" where persistent identifiers such as SAM numbers, Crossref ids, and/or Research Organization Registry (ROR) ids can be recorded, with the type specified. contactPoint: Besides "email", contactPoint should include subfields for "identifier" and "identifierType" where persistent identifiers such as ORCIDs, ResearcherID, and/or arXiv Author Identifiers can be recorded, with the type specified.
Examples: "publisher": { "organizationIdentifier": { "https://ror.org/02xfw2e90", "identifierType": {"ROR", } } }
"contactPoint": { "personalIdentifier": {"https://orcid.org/0000-0002-0543-4268", "identifierType": {"ORCID", } } }
Problem Statement
The use of persistent identifiers to unambiguously identify researchers and research-related organizations is a standard practice in publishing and repositories. People may change their name several times over a lifetime, or variants of their name may be used by different publishers, causing confusion about a researcher's lifetime of work. Further, many people have the same names. Persistent identifiers, such as ORCID, help to globally disambiguate researchers. Organizations may also go through name changes, especially after internal reorganizations, or rebranding to better express mission, or to use more inclusive language. But their mission, and role vis a vie research, many not change. Further, sometimes researchers do not use the proper or preferred name or acronyms for a funding agency or publisher when citing support or publication history. Unique identifiers help to identify a specific organization through its lifecycle, and perhaps disambiguate it from an international or regional organization with the same or similar name. The use of persistent identifiers is specifically called out by the FAIR Principles https://www.go-fair.org/fair-principles/ as the first three steps of Findability. Further, the implementation of digital persistent identifiers is required by National Security Presidential Memorandum 33 (NSPM-33) and explained in the guidance document for NSPM-33 at https://www.whitehouse.gov/wp-content/uploads/2022/01/010422-NSPM-33-Implementation-Guidance.pdf Expanding the use of persistent identifiers will help to bring DCAT-US in closer alignment with standard practice and new federal policies.
Target Audience / Stakeholders
Intended Uses / Use Cases
In DCAT-US 3
"publisher": { "organizationIdentifier": { "https://ror.org/02xfw2e90", "identifierType": {"ROR", } } }
"contactPoint": { "personalIdentifier": {"https://orcid.org/0000-0002-0543-4268", "identifierType": {"ORCID", } } }
Existing Approaches - Optional
Left blank intentionally
Additional context, comments, or links - Optional
Left blank intentionally