Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Term - projectID #532

Open
aaltenburger2 opened this issue Dec 18, 2024 · 8 comments
Open

New Term - projectID #532

aaltenburger2 opened this issue Dec 18, 2024 · 8 comments

Comments

@aaltenburger2
Copy link

aaltenburger2 commented Dec 18, 2024

taken from #527

Proposed attributes of the new term:

  • Term name (in lowerCamelCase for properties, UpperCamelCase for classes): projectID
  • Term label (English, not normative): Project ID
  • Organized in Class (e.g., Occurrence, Event, Location, Taxon): Event
  • Definition of the term (normative): A list (concatenated and separated) of identifiers for projects that contributed to a dwc:Event.
  • Usage comments (recommendations regarding content, etc., not normative): A projectID can be may be shared in multiple
    distinct datasets. The nature of the association can be described in the metadata project description element. This term should be used to provide a globally unique identifier (GUID) for a project, if available. This could be a DOI, URI, or any other persistent identifier that ensures a project can be uniquely distinguished from others. The recommended best practice is to separate the values in a list with space vertical bar space ( | ).
  • Examples (not normative): RCN276730; RCN276730 | Artsproject_7-24; OC202405; https://arvenetternansen.com/; https://doi.org/10.3030/101180559;
  • Refines (identifier of the broader term this term refines; normative): none
  • Replaces (identifier of the existing term that would be deprecated and replaced by this term; normative): none
  • ABCD 2.06 (XPATH of the equivalent term in ABCD or EFG; not normative): /DataSets/DataSet/Units/Unit/Gathering/Project/
@dshorthouse
Copy link

Examples would be best separated by ( | ) instead of semi-colons.

@aaltenburger2
Copy link
Author

aaltenburger2 commented Jan 16, 2025

Thank you for the feedback. I would separate the projectIDs with a "|" when there are several for one occurrence. The examples are meant to show different projectIDs for different occurrences; hence, the semicolons. I have updated the text with an example showing two projectIDs to make this clearer.

@mnhn-paul
Copy link

maybe some actual DOIs or URIs in the examples would be useful for the documentation.

@aaltenburger2
Copy link
Author

The research council of Norway does not provide DOIs or URIs for research projects. Do you have an example from another national research council who does that? One example could be https://arvenetternansen.com/ which I assume is a stable identifier.

@qgroom
Copy link
Member

qgroom commented Feb 27, 2025

The EU provide DOIs for research projects through their CORDIS platform. Though it is never really clear to me whether this DOI identifies the project or the description of the project.
Here is an example
https://doi.org/10.3030/101180559

@sharifX
Copy link

sharifX commented Feb 28, 2025

There is also RAiD (https://raid.org/what-is-raid) : 'Research Activity Identifier' which will be a DOI based identifier. The metadata schema supports nested activities as well (using a property called relatedObject https://metadata.raid.org/en/latest/core/relatedObjects.html). RAiD can be included as one of the examples.

@aaltenburger2
Copy link
Author

Examples have been updated as proposed. @sharifX Do you have a RAiD that is currently being used for a research project and could serve as an example?

@sharifX
Copy link

sharifX commented Feb 28, 2025

The RAiD implementation is still in beta mode. But here's one example: https://doi.org/10.26259/3b15eca7.
Within Europe the FAIRCORE4EOSC project is also working on an implementation: https://faircore4eosc.eu/eosc-core-components/research-activity-identifier-service-raid

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants