IS-02 Schema matching and ontology matching (schema mapping; field mapping)
Establishes which fields or concepts in different sources mean the same thing and produces a mapping table of equivalent, partly equivalent and unmapped fields.
What it does
Establishes which fields or concepts in different sources mean the same thing. Artefact: a mapping table. Read which fields are equivalent, partly equivalent or unmapped.
When to use it
Use when you hold datasets from different sources that describe the same domain and need to know which columns correspond.
When it does not fit
Fits sources that describe the same domain. Misfit: similar names with different meanings.
Result format
The result is a mapping table with one row per field or concept, giving the matching field in each source and whether the match is equivalent, partly equivalent or unmapped. It lists the unmapped fields.
Requirements on the material
| Property | Requirement type | Requirement |
|---|---|---|
| Structure | Applies in some cases | requires=structured; requires=semi-structured |
| Content type | Always applies | requires=tabular |
| Unit of analysis | Always applies | requires=variable; requires=dataset |
| Level of detail available | Always applies | requires=aggregate tables |
| Number of sources | Always applies | requires=two or more |
| Appraises source credibility | Applies in some cases | no |
Not restricted on: Variable types, Time structure, How the sample was chosen, Whether sources can be joined, Amount of material, Known data problems, Producer interest, Source dependence, Origin, Document genre, Language, Personal information, Security classification, Licence.
| Minimum material | none |
|---|---|
| Additional sources needed | reference structure |
| Not for (rules) | none |
| Not for (text) | Fields have similar names but different meanings, or definitions are not documented. |
Choosing and ordering
| Kind of technique | Preparation technique, runs in step 5.2 |
|---|---|
| Phase tag | verify and prepare |
| Other phase tags | none |
| Kind of finding | gap; difference |
| Question answered | what |
| Strongest statement it supports | describe |
| Needs as input |
|
| Makes as output |
|
| Must exist first | None |
| Loop target | proceed with limit stated |
Library checks by stakes
Each stakes level includes the checks of the level below it. Checks that need a person apply at high stakes only, so the process leaves them out at lower stakes (decision 38). Repeatability: repeatable with fixed settings.
| Stakes | Check | Person involved | Counts as a different method |
|---|---|---|---|
| exploratory | spot check | optional | no |
| decision-informing | spot check | optional | no |
| decision-informing | repeat runs | none | no |
| decision-informing | human review sample | needed; left out below high stakes | no |
| high-stakes | spot check | optional | no |
| high-stakes | repeat runs | none | no |
| high-stakes | human review sample | needed | no |
| high-stakes | second technique with different assumptions | none | conditional |
| high-stakes | independent review | needed | no |
Failure modes and limits
| Model suitability | model plus code |
|---|---|
| Typical model failure | Maps fields by name similarity and ignores differences in units or definitions. |
| Error sources | input data; coder or rater judgement; data transformation |
| Certainty limits | Certainty drops when field definitions are undocumented and when mappings are only partly equivalent (indirectness). |
Related techniques
- pairs with IS-03 Common data model harmonisation (OMOP (Observational Medical Outcomes Partnership) common data model; data harmonisation): the mapping table is the basis for transforming sources into one model
- should follow PE-04 Data profiling and rule-based validation (data audit; data quality assessment; edit checks): profiling shows field types and values before mapping
Evidence and tag basis
Documented. The tutorial gives a definition only. An annual evaluation campaign for ontology matching exists, but its page did not state the output format. (Dong and Naumann, VLDB tutorial; Ontology matching evaluation campaign page)
Tag basis: input profile inference; selection inference; sequencing inference; robustness inference. All tag values are inference unless a source is named.