Freya Project

FREYA Knowledge Hub

Please note that the FREYA Knowlegde Hub has moved to become part of the PID Forum at pidforum.org.
This website is therefore not being updated anymore. Rather you can find the most recent content on the Knowlegde Hub of the PID Forum: https://www.pidforum.org/c/knowledge-hub/


Welcome to the FREYA Knowledge Hub, the Persistent Identifier (PID) Platform.

The Knowledge Hub is designed to help people understand what persistent identifiers are, why they exist, and how to use them for research. It began with FREYA's predecessor, the THOR project, and is continually being updated.

You'll find comprehensive guides and webinars to help you start working with persistent identifiers as quickly as possible, and there’s support if you get stuck. If you’re new to PIDs, start with our introduction then move on to the section most relevant to you.

Get Started    

PIDs for publications and data

There are a whole range of identifiers for digital objects, so it can be difficult to know which is best suited to your situation. A useful place to start is with this quick multi-choice online guide from NCDD (Netherlands Coalition for Digital Preservation). Or watch this webinar on Persistent Identifier Selection by Marcel Ras and Remco van Veenendaal.

Below are some of the most commonly seen PIDs for publications and data:

Handle
Example - hdl:2381/12775
Non-commercial identifier resolution system, established in 1995 and operated by the Corporation for National Research Initiatives (CNRI). Used as the foundation of other higher level systems such as DOI. Commercial Handle licences can be obtained by research bodies and institutional repositories to establish local Handle systems, such as the European Persistent Identifier Consortium (EPIC).

DOI - Digital Object Identifier
Example - doi:10.1186/2041-1480-3-9
Combines a metadata model with the Handle system as the resolution infrastructure (i.e. DOIs are built upon Handles). First introduced in 1998 with funding from the International DOI foundation (IDF). Became an official ISO standard in 2012 (ISO 26324). DOI Registration agencies are responsible for assigning identifiers. The DOI system is maintained and advanced by the IDF, itself controlled by its registration agency members. Using the Handle system, there is a central free worldwide resolving mechanism for DOI names which means that DOIs are self-sufficient and their resolution does not depend on a single agency. A standard metadata kernel is defined for every DOI name. Assigning DOI names typically involves a fee, dependent on the business model of the Registration Agency, but the resolution of DOIs is free.

The primary organisations for assigning DOIs for scholarly communication are Crossref and DataCite. For more information see the ANDS Guide to DOIs and the DOI Handbook.

URN - Uniform Resource Name
Example - urn:isbn:0451450523
Introduced in 1994, formalised in 1997 and is now an IETF standard. No central governance, no central resolving infrastructure. Used by major national libraries in Europe. ISBNs for books are part of the URN system. No licence costs involved for assigning URNs, but a URN registration agency needs to establish an assigning and a resolving infrastructure. The biggest initiative to harmonise URN registration in Europe is currently undertaken by the PersID project.

ARK - Archival Resource Key
Example - ark:/13030/tf5p30086k
Introduced in 1995. Not a formal standard but all ARKs follow the same structure and workflows. No central resolver - organisations can sign up to become Name Assigning Authority Numbers (NAANs) and run their own resolution infrastructure for ARKs. The system is run by the California Digital Library with dozens of NAANs worldwide through a combined ARK/DOI infrastructure EZID.

Resources

FREYA Project Report 3.1: Survey of Current PID Services Landscape (2018)
ODIN Project Report 4.2: Workflow for interoperability (2014)

Updated 2 years ago

PIDs for publications and data


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.