Difference between revisions of "Open Geoscience Committee/persistent identifiers pid"

From OSGeo
Jump to navigation Jump to search
(more links added)
Line 67: Line 67:
 
tbd: Coming real soon
 
tbd: Coming real soon
 
=Examples=
 
=Examples=
* [https://doi.org/10.5281/zenodo.5825144 MOSS (simple 20example)]
+
* [https://doi.org/10.5281/zenodo.5825144 MOSS (simple example from a static heritage project)]
* [https://doi.org/10.5281/zenodo.5810537 GRASS GIS (complex example)]
+
* [https://doi.org/10.5281/zenodo.5810537 GRASS GIS (complex example from a highly dynamic project)]
 
* Bulleted list item
 
* Bulleted list item

Revision as of 06:51, 9 January 2022

Persistent Identifiers (PID): Introduction and HowTo

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

PID for software

Digital Object Identifier (DOI)

PID for people

Open Researcher and Contributor ID (ORCID)

PID for documentation

tbd

PID for video

[page on the TIB AV-Portal]

PID for physical objects

tbd

Infrastructure

 * Software Repositories (GitHub)
 * Zenodo


Howto: Registering a DOI for a OSGeo software Project

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 with better integration options
  • 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

Option 2: Create a live link between the GitHub Repo and Zenodo

  • 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 ?)

Howto

tbd: Coming real soon

Examples