Project

General

Profile

task #7346

[CHECK] Use separate area vocabulary for common names

Added by Andreas Müller 10 months ago. Updated 4 months ago.

Status:
In Progress
Priority:
Highest
Category:
cdmadapter
Target version:
Start date:
04/06/2018
Due date:
% Done:

70%

Estimated time:
1.50 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 to.

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 issues In Progress 04/03/2018
Related to Edit - feature request #7790: E+M: Language-Area Mapping New 09/24/2018

Associated revisions

Revision 8ef74e91 (diff)
Added by Andreas Müller 4 months ago

ref #7346 use E+M area vocabulary for common names

Revision 959bcc8d (diff)
Added by Andreas Müller 4 months ago

ref #3986 , ref #7346 remove some areas from area import

Revision 449cd4da (diff)
Added by Andreas Müller 3 months ago

ref #7346 create areas only if vocabulary does not yet exist

History

#1 Updated by Andreas Müller 10 months ago

  • Related to task #7341: [Check] CommonName import issues added

#2 Updated by Andreas Müller 9 months ago

  • Estimated time set to 6.00 h

#3 Updated by Andreas Müller 4 months ago

  • Target version changed from Euro+Med Portal Release to Euro+Med Migration

#4 Updated by Andreas Müller 4 months ago

#5 Updated by Andreas Müller 4 months ago

  • Description updated (diff)

#6 Updated by Andreas Müller 4 months ago

  • Description updated (diff)

#7 Updated by Andreas Müller 4 months ago

  • % Done changed from 0 to 40

#8 Updated by Andreas Müller 4 months ago

  • Status changed from New to In Progress

#9 Updated by Andreas Müller 4 months ago

  • % Done changed from 40 to 70

#11 Updated by Andreas Müller 4 months ago

  • Subject changed from [E+M] Use separate area vocabulary for common names to REV: Use separate area vocabulary for common names
  • Priority changed from Highest to Priority12

#12 Updated by Andreas Müller 4 months ago

  • Subject changed from REV: Use separate area vocabulary for common names to [CHECK] Use separate area vocabulary for common names
  • Priority changed from Priority12 to Highest

#13 Updated by Andreas Müller 4 months ago

  • Estimated time changed from 6.00 h to 1.50 h

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 40 MB)