-
Notifications
You must be signed in to change notification settings - Fork 60
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
Different metadata profile for Camtrap DP and DwC-A #2664
Comments
|
Yes, there recently was an update of GBIF's metadata profile: https://rs.gbif.org/schema/eml-gbif-profile/1.3/eml-gbif-profile.xsd This is implemented in the IPT v3+. Let me check if other crucial information might be needed. I am curious why you do not have to select a publishing organization for publishing Camtrap DP since it is required for other formats: Generally, the IPT have many more required fields for other formats which are not included for Camtrap DP (and maybe other DPs). |
Please be aware it is currently convoluted how the fields in the IPT relate to the EML profile and we need to document this better (gbif/tech-docs#100) - see this small example: gbif/doc-freshwater-data-publishing-guide#20 (comment) |
Ok - I will prepare a list for you as a recommendation. |
Here is an overview of the differences I noticed on the IPT while publishing a Dwc Occurrence vs Camtrap DP:
In detail:
Darwin Core Occurrence: after saving a mapping: redirect to Camtrap DP, after saving a mapping: redirect to
Camtrap DP: Publishing Organisation can be set at 2 locations:
It makes sense to only have this at Publication.
Darwin Core Occurrence: Camtrap DP:
Darwin Core Occurrence: Camtrap DP:
Darwin Core Occurrence: Camtrap DP: I prefer something else: Metadata > References
Darwin Core Occurrence: |
I noticed that there are some metadata information that is not possible to share when publishing a Camtrap DP vs a DwC-A - for example funding information, which is included in the new GBIF EML profile. Is this by design or could it be more similar to GBIF's metadata profile?
The text was updated successfully, but these errors were encountered: