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 - projectTitle #531

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

New Term - projectTitle #531

aaltenburger2 opened this issue Dec 18, 2024 · 5 comments

Comments

@aaltenburger2
Copy link

aaltenburger2 commented Dec 18, 2024

taken from #527

Submitter: Andreas Altenburger
Efficacy Justification: I work at a university museum that publishes its collections on GBIF as datasets. We constantly receive requests from contributors to the museum collection, asking to be able to track "their" contributions at the record level on GBIF. This relates to private funders such as Ocean Census (https://oceancensus.org/) or the Mohn Foundation (https://mohnfoundation.no/), governmental funding from Artsdatabanken or the Research Council of Norway, and institutional internal funding. We need to be able to attribute the specimens to their respective projects and funders.

Demand Justification: Record-level attribution has been requested several times previously. See discussions
tdwg/dwc-qa#37
tdwg/dwc-qa#83
tdwg/dwc-qa#100
gbif/pipelines#836
gbif/ipt#1780
for more details.

Stability Justification (what concerns are there that this might affect existing implementations?): New terms for record-level attribution are unlikely to negatively impact existing implementations because these terms would be additional, optional fields that enhance the granularity of data attribution without altering existing data structures.

Implications for dwciri: namespace: The introduction of the proposed new term does not necessitate changes to existing dwciri term versions. The new terms would be added as property within the Darwin Core namespace and would not alter the definitions or functionalities of existing dwciri terms.

Proposed attributes of the new term:

  • Term name: projectTitle

  • Term label: Project Title

  • Organized in Class: Event

  • Definition of the term: A list (concatenated and separated) of titles or names for projects that contributed to a dwc:Event..

  • Usage comments (recommendations regarding content, etc., not normative): Use this term to provide the official name or title of a project as it is commonly known and cited. Avoid abbreviations unless they are widely understood. The recommended best practice is to separate the values in a list with space vertical bar space ( | ).

  • Examples (not normative): The Nansen Legacy; Scalidophora i Noreg; Arctic Deep

  • Refines: NA

  • Replaces: NA

  • ABCD 2.06 (XPATH of the equivalent term in ABCD or EFG; not normative): /DataSets/DataSet/Units/Unit/Gathering/Project/ProjectTitle

@tucotuco
Copy link
Member

The comments suggest that a list is suitable as a value for this term. If that is really the intention (it would be consistent with the projectID term as currently defined), then the definition should be changed to reflect that. It would also be good to have consistent wording between projectID and project name. The projectID definition is currently "A list (concatenated and separated) of identifiers for projects that contributed to a dwc:Event." Using that as a model, I would recommend that the definition of projectName be changed to, "A list (concatenated and separated) of names or titles for projects that contributed to a dwc:Event."

@CecSve
Copy link

CecSve commented Feb 26, 2025

Should the term not be projectTitle as mentioned in the original issue?

@aaltenburger2
Copy link
Author

You are right. I change it to projectTitle as agreed upon before.

@aaltenburger2 aaltenburger2 changed the title New Term - projectName New Term - projectTitle Feb 26, 2025
@tucotuco
Copy link
Member

I made the change to be consistent with the term request for fundingBodyName and in anticipation of a large body of upcoming proposed changes so that it would be consistent with those changes. If it is important to use the term name 'projectTitle' in place of 'projectName', my proposed new term name can be reverted.

@aaltenburger2
Copy link
Author

Definition updated as suggested above.

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

3 participants