ISO19115-3 mappings to OARec

[ByronCinNZ]

Candidate crosswalk attached. Needs discussion.
iso19115OARec-Crosswalk.xlsx
Note - This is a crosswalk for the latest version of ISO19115-3 based on ISO19115-1:2018. There will be some differences to 19139 metadata based on ISO19115:2004

[ghobona]

@ByronCinNZ Thanks for this! Very much appreciated.

[ByronCinNZ]

I did not complete the "links" mappings due to my lack of understanding. However I have a few mappings I think work.
For link to self //mdb:MD_Metadata/mdb:metadataLinkage
For link to alternate source (md standard may vary) - //mdb:MD_Metadata/mdb:alternativeMetadataReference
For link to parent - //mdb:MD_Metadata/mdb:parentMetadata

[ByronCinNZ]

What else would belong in "links:"? mdb:metadataStandard? mdb:metadataProfile?

[ByronCinNZ]

Candidate new mapping from ISO19115-3
Spatial Resolution //mdb:MD_Metadata
 /mdb:identificationInfo
 /mri:MD_DataIdentification /mri:spatialResolution /mri:MD_Resolution
(May be represented in a number of ways? Restricting it to numerical representation would aid search)
Candidate geoJSON mapping - properties.resolution

[pvretano]

@ByronCinNZ I can't seem to read the .xlsx file. I'm using libreoffice. Can you save it as an .xls file instead?

[ByronCinNZ]

@pvretano Try this
iso19115OARec-Crosswalk.xls

[pvgenuchten]

Great work Byron!

Some comments/questions:

• for type you refer to topiccategory, isn't this element more fit to capture hierarchylevel (e.g. dataset, service, sensor, document) (and topiccategory would go into theme (or keyword) i'd imagine)
• links section needs further clarification, ogcapi-common provides a number of types of links, we should capture (only some are related to this crosswalk):
  • links to related records
  • a link to the original location of the record (point of truth, canonical url)
  • a link to the collection where this record is a part of
  • link to alternative representations of this record (profile, language, format)

[pvgenuchten]

Notice that https://github.com/geopython/pygeoapi/blob/master/tests/load_tinydb_records.py contains a mapping of iso19139:2007 to ogc-api-records

[ByronCinNZ]

@pvgenuchten Thanks for the feedback Paul.
I will change type to metadataScope and replace my current mapping of theme with type
For links I have included references for a link to the original location of the record (point of truth, canonical url) and link to alternative representations of this record (profile, language, format) //mdb:MD_Metadata/mdb:metadataLinkage and //mdb:MD_Metadata/mdb:alternativeMetadataReference
I also include parentMetadata mapping in links. //mdb:MD_Metadata/mdb:parentMetadata
Not sure how to best map "collection where this record is a part of" or "links to related records". What goes into links and what goes into associations?

[ByronCinNZ]

Updated mappings are attached here
iso19115OARec-Crosswalk.xls

[pvgenuchten]

Suggestion could be to extend this a bit, add columns for iso19139 and DCAT, e.g.

OGC-API Records	iso19139:2007	iso19115-3:2012	DCAT 2
recordId	gmd:fileIdentifier	mcc:MD_Identifier	//dct:identifier
recordCreated	-	mdb:dateInfo[@dateType='creation']
recordUpdated	gmd:dateStamp	mdb:dateInfo[@dateType='LastUpdate']	dct:modified
type	gmd:hierarchyLevel	mdb:resourceScope	dct:type
title	gmd:title	cit:title	dct:title
description	gmd:abstract	cit:abstract	dct:description
keywords	gmd:keyword	mri:keyword	dcat:keyword
keywordsCodespace	gmd:thesaurusName	mri:thesaurusName	skos:inScheme
language	gmd:language	mdb:defaultLocale	dct:language
externalId	gmd:identifier	cit:identifier
created	gmd:date[@dateType='creation']	cit:date[@dateType='creation']	dct:created
updated	gmd:date[@dateType='modified']	cit:date[@dateType='lastUpdate']	dct:modified
publisher	gmd:pointOfContact[@ROLE='publisher']	mri:pointOfContact[@ROLE=“publisher”]	dct:publisher
themes	gmd:topicCategory	mri:topicCategory	dcat:theme
formats	gmd:format	mrd:MD_Format	dct:format
contactPoint	gmd:pointOfContact[@ROLE='pointOfContact']	mri:pointOfContact[@ROLE=“pointOfContact”]	dcat:contactPoint
license	gmd:MD_LegalConstraints/gmd:otherConstraints	mco:MD_LegalConstraints/gmd:otherConstraints	dct:license
rights	gmd:accessConstraints	mco:accessConstraints	dct:accessRights
extent	gmd:extent	mri:extent	dct:spatial / dct:temporal
associations	gmd:transferOptions	mri:asssociatedResource	dcat:accessURL

Sources: https://github.com/SEMICeu/iso-19139-to-dcat-ap/blob/master/documentation/Mappings.md

[cholmes]

Awesome work. One thing that would be really great to add is what fields are required. That'll help me a lot in figuring out what to make required in the 'dataset record' proposal, see #130

Also do any of these have default values? Like for language or keywordsCodespace?

[ByronCinNZ]

Working on that and will include indication of manditory ISO fields in my pull request

[ByronCinNZ]

Another candidate new mapping from ISO19115-3
Metadata Contact //mdb:MD_Metadata
 /mdb:contact

Candidate geoJSON mapping - recordContact
Metadata contact is mandatory in ISO19115-3

[pvretano]

@ByronCinNZ what is the description ISO1911503 //mdb:MD_Metadata
 /mdb:contact
? Is it a contact responsible for the record itself ... as opposed to the resource that the record describes?

+1 @cholmes opengeospatial/ogcapi-code-sprint-2021-07#23 (comment)

[ByronCinNZ]

@pvretano Yes that is a contact for the record not the resource (which is captured separately)

[pvretano]

07-APR-2023: Looks like a duplicate of #174. Work can continue in the more recent issue.