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 - fundingAttribution #533

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

New Term - fundingAttribution #533

aaltenburger2 opened this issue Dec 18, 2024 · 6 comments

Comments

@aaltenburger2
Copy link

aaltenburger2 commented Dec 18, 2024

taken from #527

  • Submitter: Andreas Altenburger
  • Efficacy Justification (why is this term necessary?): 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 (name at least two organizations that independently need this term): Record-level attribution has been requested several times previously. See discussions
    Project Information - Darwin Core Hour Input Form 2/14/2017 11:46:27 dwc-qa#37
    tracking funding source for projects at occurrence record level dwc-qa#83
    serving datasetID for some, not all records dwc-qa#100
    ProjectIDs on individual records, rather than a dataset as a whole gbif/pipelines#836
    Option to add several projects in the Project data metadata page 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. Current users and systems can continue to operate without adopting these new terms immediately, allowing for a gradual integration. Moreover, these terms are designed to be backward-compatible, ensuring that they do not disrupt existing workflows or data integrity. The addition of these terms would primarily provide a means for more detailed tracking and reporting, which is a growing requirement from funders and contributors. This enhancement would improve the transparency and traceability of data contributions without imposing changes on those who do not require this level of detail.
  • Implications for dwciri: namespace (does this change affect a dwciri term version)?: The introduction of the proposed new term does not necessitate changes to existing dwciri term versions. The new term would be added as property within the Darwin Core namespace but would not alter the definitions or functionalities of existing dwciri terms.

Proposed attributes of the new term:

  • Term name (in lowerCamelCase for properties, UpperCamelCase for classes): fundingAttribution
  • Term label (English, not normative): Funding Attribution
  • Organized in Class (e.g., Occurrence, Event, Location, Taxon): Event
  • Definition of the term (normative): A list (concatenated and separated) of names of the funding organizations or agencies that provided funding for the project.
  • Usage comments (recommendations regarding content, etc., not normative): Specify the full official name of the funding body. This should include the complete name without abbreviations, unless the abbreviation is an official and commonly recognized form (e.g., NSF for the National Science Foundation). The recommended best practice is to separate the values in a list with space vertical bar space ( | ).
  • Examples (not normative): Norges forskningsråd; Artsdatabanken; Ocean Census | Nippon Foundation
  • Refines (identifier of the broader term this term refines; normative): NA
  • Replaces (identifier of the existing term that would be deprecated and replaced by this term; normative): NA
  • ABCD 2.06 (XPATH of the equivalent term in ABCD or EFG; not normative): /DataSets/DataSet/Metadata/Owners/Owner/Organisation/Name this is not a perfect fit as the funding body is not necessarily the owner
@tucotuco
Copy link
Member

Since a list is suitable as a value for this term, the definition should use a pattern consistent with similar terms already in Darwin Core. For example, recordedBy is defined as "A list (concatenated and separated) of names of people, groups, or organizations responsible for recording the original dwc:Occurrence." Using that as a model, I would recommend that the definition of fundingBody be changed to, "A list (concatenated and separated) of names of the funding organizations or agencies that provided funding for the project."

@aaltenburger2
Copy link
Author

Definition updated as suggested.

@tucotuco
Copy link
Member

I just rediscovered that Audiovisual Core has the term 'ac:fundingAttribution'. Should we reuse that?

@baskaufs
Copy link

I think that if the meaning is the same (which it appears to be), then just borrow the term. I think it would be appropriate for DwC to add its own usage notes, since the AC notes don't have any guidance on usage except to say that it should be text (vs. IRI)

@aaltenburger2
Copy link
Author

aaltenburger2 commented Feb 27, 2025

So we replace FunndingBodyName with fundingAttribution? Fine by me. Updated accordingly.

@aaltenburger2 aaltenburger2 changed the title New Term - fundingBodyName New Term - fundingAttribution Feb 27, 2025
@tucotuco
Copy link
Member

Specifically, we would create an entry in the list of Darwin Core terms for Event, and that entry would be the Audiovisual Core term ac:fundingAttribution with additional usage comments. We have other term adoptions as precedents, including a variety of Record-level terms from two Dublin Core namespaces.

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