Links - not persistent
Links - local persistence
Human readable PIDs
Machine readable PIDs
Globally resolvable PIDs
Implement human readable
Implement machine readable
Implement globally resolvable PIDs
Cost of implementing identifiers
Use case mapping
Glossary - Terms used in this resource
To create collections comprised of more than one collection, this can take place at varying scales, e.g. Europeana, Google Arts and Culture etc.
Inclusion of a reference to an entity in a publication or other output. These can include a link to a PID which resolves to a landing page containing metadata about the object
To create links between different systems using external PIDs to reference information held in external systems. In relation to collections this would be demonstrated by using external PIDs as IDs for external items within an internal collection management system
To be able to search across one or more collections, e.g. in union catalogues or discovery tools
Refers to entities within the metadata in the institution e.g. name authority files. Could also refer to items in the collection but item is included for all definitions
The ability of a system to exchange and make use of information
Refers to collection items held by the institution
A number or string used to identify items within an organisation. They can include database identifiers, accession numbers, reference numbers and shelfmarks
Information which can be read by a computer, with no human intervention, ensuring no semantic meaning is lost. The information must be structured and expressed in a way which a computer can process, e.g. Cool URIs.
A long-lasting digital reference to a resource
For example usage statistics, lists of collection content filtered by facets etc.
Where the metadata associated with the PID can be accessed online directly through the PID, i.e. by using the PID hyperlink to access the information
We value your feedback on this resource. Any suggestions on the content or additional examples would be welcome.To submit feedback, you can raise an
issue via Github
(requires an account) or you can use the Feedback button in the bottom right of each screen.