Data Mapping List of Terms (In Progress)

Title : Data Mapping List of Terms

Date version issued : 2024-06-17

Date created : 2024-06-17

This version : 0.3.0

Latest version : 0.3.0

Abstract : The Data Mapping Digital Object is created to contain the details necessary for mapping the data from the source system to the openDS data model. It has space for some general information but its most important content are the two Mapping objects: DefaultMapping and FieldMapping.
The DefaultMapping can be used to set default values for the fields in the openDS data model. When a value such as the ods:physicalSpecimenIDType is not present in the dataset as field, a default for the entire dataset can be set in the DefaultMapping. FieldMapping also impacts the full dataset. Within DiSSCo we try to set sensible defaults for the mapping to the openDS data model. However, for certain fields in a dataset these sensible default might need to be overruled. This is possible through the FieldMapping object, for each field in the openDS data model an explicit mapping can be set to a field in the source data. For example, by default we will try to map the ods:physicalSpecimenID to the dwc:occurrenceID field in the source data. However, sometimes it makes more sense to map the ods:physicalSpecimenID to the dwc:catalogNumber field in the source data. This can be done through the FieldMapping.
The data mapping is decoupled from the Source System so that for institutions with multiple Source Systems, only one Data Mapping object needs to be created. All Source Systems can then use the same Data Mapping object.

Main contributors : Sam Leeflang, Soulaine Theocharides, Tom Dijkema

Creator : Distributed Infrastructure for Scientific Collections (DiSSCo)

Bibliographic citation : Distributed Infrastructure for Scientific Collections. 2024. Data Mapping List of Terms.

1 Introduction

1.1 Status of the content of this document

The openDS data specification is in active development. This document is work in progres and might change until version 1.0.0 is released. Its main function at the moment is to inform the community about the current state of the data model and to gather feedback. We hope to include the feedback from the community and reach a first major version of the data model by the end of 2024.

1.2 RFC 2119 key words

The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in BCP 14 RFC 2119 and RFC 8174 when, and only when, they appear in all capitals, as shown here.

2 Borrowed Vocabulary

When terms are borrowed from other vocabularies, openDS uses the IRIs, common abbreviations, and namespace prefixes in use in those vocabularies. The IRIs are normative, but abbreviations and namespace prefixes have no impact except as an aid to reading the documentation.

Table 1. Vocabularies from which terms have been borrowed (non-normative)

3 Namespaces, Prefixes and Term Names

The namespace of terms borrowed from other vocabularies is that of the original. The namespace of de openDS terms is http://rs.dissco.eu/opends/terms/. In the table of terms, each term entry has a row with the term name. This term name is generally an “unqualified name” preceded by a widely accepted prefix designating an abbreviation for the namespace It is RECOMMENDED that implementers who need a namespace prefix for the openDS namespace use ods. In this web document, hovering over a term in the Index By Term Name list below will reveal a complete URL that can be used in other web documents to link to this document’s treatment of that term, even if it is from a borrowed vocabulary.