Open Geoscience Committee/persistent identifiers pid

Scope
This wiki page summarizes relevant facts and procedures regarding persistent identifers (PID) for the OSGeo communities.

Status
Draft (2022-01-09)

Overview

 * 1) What are persistent identifiers and why are they relevant
 * 2) PID for software
 * 3) PID for people
 * 4) PID for documentation
 * 5) PID for video
 * 6) PID for physical objects
 * 7) Infrastructure
 * 8) Howto: Registering a DOI for a OSGeo software Project

What are PID

 * Definition of PID according to Wikipedia

Digital Object Identifier (DOI)

 * Definition of DOI by Wikipedia

Open Researcher and Contributor ID (ORCID)

 * Definition of ORCID by Wikipedia

PID for documentation
tbd

PID for video
[|Wiki page on the TIB AV-Portal]

PID for physical objects
tbd

Infrastructure
* Software Repositories (GitHub) * Zenodo

Requirements
This should be done by a person who represents the software project (member of PSC or similar).

Options
ORCIDs for authors, developers and other project staff can be embedded in the DOI metadata, allowing for proper citation.

Option 1: Upload a snapshot

 * Pro: Takes less than 10 minutes to achieve
 * Pro: Can be extended and superseeded with better integration options. the DOI will stay always valid regardless and will point to the most up to date software version (and author credits)
 * Pro: No need to set webhooks in Zenodo or store description files in GitHub
 * Con: Metadata (author list) must be edited manually. (ORCID option ?)
 * Con: Every software release requires maintenance work by project staff, as an additional tarball must be uploaded and metadata must be updated.

=Howto= =Examples=
 * How to make your code citable (Berkeley Library)
 * rasdaman project

Option 2: Create a live link between the GitHub Repo and Zenodo
=Howto= tbd: Coming real soon =Examples=
 * Pro: Immediate automated updates of DOI payload and metadata for each software release on GitHub
 * Con: Takes a bit longer than option 1 (20 minutes ?)
 * MOSS (simple example from a static heritage project)
 * GRASS GIS (complex example from a highly dynamic project)
 * Bulleted list item