Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Person identifiers in respositories exported in metadata to third parties #14
As an institutional repository manager, I want to expose metadata about the resources in my repository to downstream services, in a way which optimises the processing of the metadata by those services.
With respect to person identifiers in Dublin Core I want to be able to:
This use case is derived from discussions in the UK ORCID consortium recorded at:
Comments on implementation options and examples:
Limitations: The identification scheme is not known with this format.
Regarding (a) and (b) the ideal is to allow:
For requirement (c) provenance information could include whether the ID was verified locally (ie with the involvement of the user doing an authenticating process), whether it was harvested from an external system.
The requirement for provenance information is so that downstream systems can then make processing decisions based on whether they consider the provenance entity to be trustworthy (e.g. they could discard the ORCID ID or incorporate them into their own records).
Example for including ORCID ID in RDF export as implemented in eprints Advance ORCID plugin, 2018
I think it would be really great if the workshop could unpack the requirement a little further. Also think about, is there anything about PIDs that makes it more critical to know their provenance than other metadata? Repository managers and harvesting systems are needing to decide now 'do I store and trust this PID that I've received, and do I share it on?' However if that's what they've been doing with other metadata, what is different about PIDs?