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 almost 3 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 #1

Updated by Andreas Müller about 6 years ago

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

Updated by Andreas Müller about 6 years ago

  • Estimated time set to 6:00 h
Actions #3

Updated by Andreas Müller over 5 years ago

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

Updated by Andreas Müller over 5 years ago

Actions #5

Updated by Andreas Müller over 5 years ago

  • Description updated (diff)
Actions #6

Updated by Andreas Müller over 5 years ago

  • Description updated (diff)
Actions #7

Updated by Andreas Müller over 5 years ago

  • % Done changed from 0 to 40
Actions #8

Updated by Andreas Müller over 5 years ago

  • Status changed from New to In Progress
Actions #9

Updated by Andreas Müller over 5 years ago

  • % Done changed from 40 to 70
Actions #11

Updated by Andreas Müller over 5 years 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
Actions #12

Updated by Andreas Müller over 5 years 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
Actions #13

Updated by Andreas Müller over 5 years ago

  • Estimated time changed from 6:00 h to 1:30 h
Actions #14

Updated by Andreas Müller about 5 years ago

  • Related to task #8272: Add includedIn relations to E+M areas added
Actions #15

Updated by Andreas Müller about 5 years ago

  • Description updated (diff)
Actions #16

Updated by Andreas Müller about 5 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 70 to 90

This is generally solved. We only need to discuss how "Wales" should be handled as it is the only area which does not exist in E+M area vocabulary.

A follow up ticket exists for creation of includedIn relationships

Actions #17

Updated by Andreas Müller almost 3 years ago

  • Status changed from Resolved to Closed
  • % Done changed from 90 to 100
Actions

Also available in: Atom PDF