Project

General

Profile

Actions
Copy link

bug #7449

open

E+M: Import common names with no regionFk correctly

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

Status:
Resolved
Priority:
Highest
Assignee:
Andreas Müller
Category:
cdmadapter
Target version:
Euro+Med Migration
Start date:
Due date:
% Done:

0%

Estimated time:
Severity:
normal
Found in Version:
Tags:
euro+med

Description

Currently it looks they are not imported at all as there is an iteration over the set of regions and for each region a common name is created.

Note: also check if multiple regionFks are correctly imported.

Related issues

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

Actions
Actions
Copy link
 #1

Updated by Andreas Müller over 6 years ago

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

Updated by Andreas Müller almost 6 years ago

  • Target version changed from Euro+Med Portal Release to Euro+Med Migration
Actions
Copy link
 #3

Updated by Andreas Müller almost 6 years ago

  • Description updated (diff)
  • Status changed from New to Resolved

The empty ones are all common names for ILDIS taxa:

SELECT n.FullNameCache, n.NameCache, cn.*
FROM emCommonName cn INNER JOIN Name n ON n.nameId = cn.PTNameFk
WHERE cn.RegionFks IS NULL

I checked for AND PTNameFk = 21911 (Medicago minima (L.) L.) , which had the common names with empty refFk now (e.g. commonNameID = 125272).

====

There are only 19 with regionFk.size > 1

SELECT n.FullNameCache, n.NameCache, cn.*
FROM emCommonName cn INNER JOIN Name n ON n.nameId = cn.PTNameFk
WHERE cn.RegionFks like '%,%'  AND PTNameFk = 28017

I found both with commonNameID source 32965 in import

So this ticket seems to be fixed.

Actions
Copy link

Also available in: Atom PDF