Project

General

Profile

Actions

task #7346

closed

[CHECK] Use separate area vocabulary for common names

Added by Andreas Müller about 6 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Highest
Category:
cdmadapter
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
1:30 h
Severity:
normal
Tags:

Description

Currently we try to map common name areas to tdwg and country vocabularies.
Experience has shown that it is better to have an own vocabulary.
It future it is also planned that a mapping between (area) terms is possible via concept relationships so queries on areas of different vocabularies should still be possible.

We can use the emArea vocabulary which is mostly for occurrences but includes all areas required for common names, too.

Currently 147 of 149 areas are imported. The 2 not imported are the additional area 211 and 213 of Azores and Canary Is. They are not needed for common names.

The mapping emCommonNameRegionFk -> emArea can be handled via table emLanguageRegion. But

  • emCommonNameRegionFKs is a comma separated list, so it needs to be split first
  • emLanguageRegion.Region include region name and emCode, the mapping is to be done via the emCode part (for very few areas such a code does not exist, e.g. Wales which has 147 common names and Catalan which has no common names)

The includedIn mapping can be done via emRelArea, but still needs to be checked for completeness. Also there is one area that is included in 2 areas (666- North Caucasus, part of Russion Federation and Caucasia (Ab+Ar+Gg+Rf(CS))


Related issues

Related to EDIT - task #7341: [Check] CommonName import issuesResolvedAndreas Müller

Actions
Related to EDIT - feature request #7790: [DISCUSS] E+M: Language-Area MappingNewAndreas Müller

Actions
Related to EDIT - task #8272: Add includedIn relations to E+M areasNewAndreas Müller

Actions
Actions

Also available in: Atom PDF