New Term - projectTitle

[aaltenburger2]

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: Occurence

• Definition of the term: The title or name of the project under which the data was collected or the specimen was acquired.

• Usage comments (recommendations regarding content, etc., not normative): Use this term to provide the official or commonly recognized title or name of the project. This should be the title under which the project is 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