Persistent identifiers (WP3)

The main objective of WP3 is to enable and support a sustainable implementation of PIDs in an EOSC context by working together with PID service providers and infrastructures to meet user needs, align with EOSC PID Policy and to maximise the uptake of good PID practices.


This WP will support the creation of a coordination mechanism for PID Service Providers to get together to discuss relevant PID developments and to agree on good PID practices. The PID service providers will together produce a shared value proposition for PID service providers on PID usage in EOSC - the European Open Science Cloud. The EOSC PID coordination mechanism should facilitate  coordination between EOSC, PID service providers, and PID stakeholders globally. This way it responds to the needs of research and Open Science, in a way that ensures sustainability, continuity of services and innovation, and promotes the alignment of PID infrastructures in line with the EOSC PID Policy.

The work also entails collecting and documenting PID requirements for different types of data and workflows; sensitive data, dynamic workflows as well as evolving datasets and complex data citation.

In addition to these themes, all use cases will consider three cross-cutting themes;

  1. scientific reproducibility and machine actionability,
  2. granularity identifier syntax and relations, and
  3. data types/objects (e.g. instruments, devices, software and services).


The use case representatives will be provided with the opportunity to exchange experiences and views on successful PID solutions in three dedicated workshops aiming for consensus. The work with the communities is heavily user-centric and focuses on transferring best PID practices between scientific disciplines via the PID implementation programme. Furthermore, this WP will identify different EOSC actors and map their existing PID policies, analyse them and provide guides on defining PID policies in compliance with the EOSC PID Policy. This will be accomplished via three PID policy alignment workshops.

Lastly, WP3 offers practical implementation support for services and assists in performing self-assessments of PID compliance of services by utilising the PID assessment toolkit (to be developed by the other INFRA-EOSC project FAIRCORE4EOSC) to enforce the EOSC PID policy.

The expected impact is a more FAIR service ecosystem that offers better data quality and reusability producing societal and economic benefits in efficiency and fact based policy making.

Key tasks

  • Setting up a coordination mechanism for PID service providers to help them align their service implementation with the EOSC PID policy, and to create a shared long term vision for PID usage in EOSC.
  • On the basis of work conducted by selected use cases, the creation of a blueprint for PID practices in FAIR data management to be explored for adaptation by other communities and creation of User guidelines on EOSC PID implementation.
  • On the basis of analysis of EOSC actors and their PID policies, the creation of guidelines for communities to support the definition of EOSC compliant PID policy.
  • Carrying out a PID implementation programme to provide practical support for the selected applicants from the open calls (WP2), and to produce a guide to implement EOSC compliant PIDs.

Key expected outcomes

  • More coherent implementation of PIDs and more exact data citation as services support better data quality.
  • A broader and more targeted use of PIDs, avoiding creation of zombie identifiers, corrupting trust in PID services and risking galloping costs.
  • Enhanced scientific reproducibility.
  • A well designed use of PIDs for sensitive data (including kernel metadata and rights), enabling research with sensitive data without transferring data across borders or outside secure environments.

Related deliverables and milestones

Check them here


Partners involved

  • CSC - Leader -
  • SURF
  • DataCite
  • DTU-DeiC
  • Life-Watch
  • CNR


Watch the interview with Jessica Parland von essen - CSC Finland


What are the Persistent Identifiers and why to use them?

Video credits: FAIRsFAIR project

Get in touch with WP3 colleagues - write us