NUB: Some classification keys do not exist in the database

18149
Reporter: mblissett
Assignee: mdoering
Type: Bug
Summary: NUB: Some classification keys do not exist in the database
Priority: Blocker
Resolution: Fixed
Status: Closed
Created: 2016-01-12 16:01:17.269
Updated: 2016-02-11 11:39:46.139
Resolved: 2016-02-11 11:39:46.053
        
Description: {{SELECT n.id, n.phylum_fk, p.id FROM name_usage n LEFT JOIN name_usage p ON n.phylum_fk = p.id WHERE n.phylum_fk IS NOT NULL AND p.id IS NULL AND n.dataset_key = 'd7dddbf4-2cf0-4f39-9b2a-bb099caae36c' AND n.deleted IS NULL LIMIT 10000;}}

4048 names are returned — they have a phylum_fk, but these ids don't exist in the table.

3118 for family_fk, 1970 for class_fk, 24171 for genus_fk, and 23351 for parent_fk.

Most of these are accepted names.
]]>
    

Author: mdoering@gbif.org
Comment: This only shows up in the nub, not any other checklist. Likely a nub build based issue
Created: 2016-01-13 17:55:18.782
Updated: 2016-01-13 17:55:18.782

Author: mdoering@gbif.org
Comment: Fixed. Query returns zero records now
Created: 2016-02-11 11:39:46.136
Updated: 2016-02-11 11:39:46.136