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

populate occurrence fields based on MeasurementOrFact records #197

Open
pieterprovoost opened this issue Oct 1, 2021 · 2 comments
Open
Labels
data quality Issues associated with the quality/completeness of datasets and records OBIS EC Issues that need to be addressed by the OBIS EC and passed on to appropriate assignments QC task team

Comments

@pieterprovoost
Copy link
Member

pieterprovoost commented Oct 1, 2021

In several discussions (e.g. nvs-vocabs/OBISVocabs#15) the suggestion has come up that we could populate occurrence fields based on information in the MeasurementOrFact extension.

Possible target fields include:

  • samplingProtocol
  • sampleSizeValue
  • sampleSizeUnit
  • samplingEffort
  • habitat
  • individualCount
  • organismQuantity
  • organismQuantityType
  • sex
  • lifeStage
  • reproductiveCondition
  • occurrenceStatus

Populating these terms would require a mapping between the NVS and the Darwin Core terms.

I'm not aware of any existing QC flags for values amended based on extension records.

@pieterprovoost pieterprovoost added data quality Issues associated with the quality/completeness of datasets and records OBIS EC Issues that need to be addressed by the OBIS EC and passed on to appropriate assignments QC task team labels Oct 1, 2021
@ymgan
Copy link
Collaborator

ymgan commented Oct 25, 2021

@timrobertson100 I am wondering if GBIF populate occurrence fields based on information in MeasurementOrFact extension? If there is, do you mind to please link the documentation/related issues here? Thank you so much!!

@timrobertson100
Copy link

timrobertson100 commented Oct 25, 2021

Thanks @ymgan

At GBIF we don't pull anything in today. However, we do have some code to extract sex and lifestage from dwc:dynamicProperties.

We ported the extraction of some measurements from the VertNet implementation to Java - e.g. extracting length - but this raised many questions, and we haven't moved it into our production processes. You'll find other parsers we ported but don't yet use here.

Edited to add: we're interested to see where you may take this, and looking to learn from you. Our plans aren't really clear.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data quality Issues associated with the quality/completeness of datasets and records OBIS EC Issues that need to be addressed by the OBIS EC and passed on to appropriate assignments QC task team
Projects
None yet
Development

No branches or pull requests

3 participants