tdwg / mids

11 stars 7 forks source link

Mapping template for MIDS level 1 #49

Closed hardistyar closed 2 months ago

hardistyar commented 3 years ago

Design and agree mapping template for mapping institutional collection management and other data management schema terms/fields to MIDS level 1 information elements.

hardistyar commented 3 years ago

Elspeth (RGBE) has provided one: https://docs.google.com/spreadsheets/d/1pvEdHjbZdfCs26a_Q71UzZCtpJtzVIcMtxv8FtJA-Fs/edit?usp=sharing

emhaston commented 2 years ago

Mapping of MIDS-1 elements

cp-weiland commented 2 years ago

Some matching terms I found, organization has an exact match in ABCD (I think), we might fit MIDS level in openDS (which has a narrower def), dcterms modified/license are in DWC - maybe that fits also for MIDS?

MIDS term Mapping Label Mapping URI used in DWC?
Modified Date Modified http://purl.org/dc/terms/modified yes, same
PhysicalSpecimenId Maps broadly to: dwc:catalogNumber, dwc:occurrenceID, dwc:materialSampleID, ABCD:physicalObjectID   yes, DWC/ABCD
Organisation Organisational Unit Name (LC) Organization (ABCD) https://github.com/tdwg/cd/issues/198 http://rs.tdwg.org/abcd/terms/Organization  no, but in ABCD
SpecimenType dwc:materialSampleType   proposed?  
ObjectType Broadly maps to: dwc:preparations, ABCD:kindOfUnit    
Name dcterms:title   http://purl.org/dc/terms/title  no, also not in ABCD
Licence License http://purl.org/dc/terms/license yes, same
MIDSLevel MIDS Level https://modelling.dissco.tech/wiki/Item:Q18 ,no, skos:broadMatch to ods:MIDSLevel

matdillen commented 2 years ago

I've been working on a JSON schema to automate calculations of MIDS levels. The schema maps MIDS elements to specific properties in a dataset. The scope was currently on (GBIF-annotated) DwC archives, but I hope to extend it to other standards as well.

There was support for XML as well, to enable mappings to EML metadata (specifically dataset publication date for the Modified MIDS element), but that needs further fleshing out in the JSON and is only partially supported in the current (unfinished) version of the Rshiny app that makes use of the schema.

https://github.com/AgentschapPlantentuinMeise/MIDSCalculator/blob/main/data/schemas/DwC-GBIF_schema.json

wouteraddink commented 2 years ago

Hi Mathias, this is interesting but maybe not the right approach since DwC is not fully compatible (yet) with MIDS. So you get mappings that are not entirely correct, for instance specimen type is not basis of record (in openDS we now have a proposed list of 10 types + 7 not currently in scope of DiSSCo), name is not always scientific or vernacular name (e.g. can be a chemical formula for a mineral), MIDS institution(P)ID does not equal dwc:institutionID (which does not need to be resolvable). So I think either you need to map to openDS and GBIF needs to support that (in the future) as one of the supported schemas or DwC needs changes to support MIDS elements.

Kind regards, Wouter

On Tue, 12 Jul 2022 at 11:32, Mathias Dillen @.***> wrote:

I've been working on a JSON schema to automate calculations of MIDS levels. The schema maps MIDS elements to specific properties in a dataset. The scope was currently on (GBIF-annotated) DwC archives, but I hope to extend it to other standards as well.

There was support for XML as well, to enable mappings to EML metadata (specifically dataset publication date for the Modified MIDS element), but that needs further fleshing out in the JSON and is only partially supported in the current (unfinished) version of the Rshiny app that makes use of the schema.

https://github.com/AgentschapPlantentuinMeise/MIDSCalculator/blob/main/data/schemas/fourthschema.json

— Reply to this email directly, view it on GitHub https://github.com/tdwg/mids/issues/49#issuecomment-1181539628, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADAUXUQZLZFBZDX4445RA3VTU3UPANCNFSM5BEEIYWQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>

-- Coördinator Research-data and E-infrastructure

International Biodiversity Infrastructures Natural Biodiversity Center, P.O. Box 9517, 2300 RA Leiden, The Netherlands

Coordination team member, Distributed System of Scientific Collections ( DiSSCo http://dissco.eu/) Node Manager for DiSSCo, Global Biodiversity Information Facility (GBIF http://www.gbif.org/) Regional representative for Europe, Biodiversity Information Standards Organisation (TDWG http://tdwg.org/) Chair Biodiversity Data Integration IG, Research Data Alliance (RDA http://www.rd-alliance.org/) Catalogue of Life Ambassador (CoL http://www.catalogueoflife.org/)

ORCID: 0000-0002-3090-1761 | Linkedin: linkedin.com/in/wouteraddink/ http://linkedin.com/in/wouteraddink/

Twitter: @wouter99999 | Tel: +31 (0) 71 751 9364

@.*** - www.naturalis.nl - www.catalogueoflife.org - www.dissco.eu

matdillen commented 2 years ago

Both openDS and ongoing developments in TDWG task groups for Darwin Core are currently still moving targets with no effective implementations yet and hence no GBIF support. We used Darwin Core as it is used as of now, because it is already widely implemented and available, hence it can be utilized for immediate MIDS calculations.

The mappings are not perfect, as Darwin Core is not either and MIDS itself is still being developed, but dwc:basisOfRecord is the best approximation we have now for specimenType. Mineral names are currently not in scope of this schema. We would probably need a different one to accommodate such specimens. Mappings to ABCD may be useful in this regard, but we'd have to develop them and I lack experience with that standard to make that happen efficiently.

emhaston commented 2 months ago

This has been superceded by other mapping issue versions