Project

General

Profile

Actions

bug #9322

closed

Remove invalid designation taxon relationship

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

Status:
Closed
Priority:
Priority14
Category:
cdmlib
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Severity:
normal
Found in Version:

Description

Invalid designations are simply names which are not valid and therefore are called "designations" only not "names".

For some reason in the Berlin Model there was a taxon relationship called "is invalid designation for" which was imported to CDM as well.

This relationship should not be used. Instead a synonym relationship should be used and the "designation" name should get a nomenclatural status indicating that it is "invalid".

Therefore everything related to "invalid designation" relationship should be deleted in TaxEditor, Dataportal and cdmlib/model.


Related issues

Related to EDIT - task #8055: Correct formatting for invalid designationsRejectedAndreas Müller

Actions
Related to EDIT - feature request #7761: Invalid designations should be displayed like misapplied names in name editorClosedKatja Luther

Actions
Related to EDIT - feature request #6394: Allow additional taxon relationships in TaxEditor to be handled similar to misapplicationsNewKatja Luther

Actions
Actions #1

Updated by Andreas Müller about 2 years ago

  • Related to task #8055: Correct formatting for invalid designations added
Actions #3

Updated by Andreas Müller about 2 years ago

  • Related to feature request #7761: Invalid designations should be displayed like misapplied names in name editor added
Actions #4

Updated by Andreas Müller about 2 years ago

  • Related to feature request #6394: Allow additional taxon relationships in TaxEditor to be handled similar to misapplications added
Actions #5

Updated by Andreas Müller about 2 years ago

Find possible cases:

SELECT tr.id, tb1.titleCache fromx , tb2.titleCache tox, tr.*
FROM TaxonRelationship tr 
INNER JOIN DefinedTermBase trType ON trType.id = tr.type_id 
LEFT JOIN TaxonBase tb2 ON tb2.id = tr.relatedto_id
LEFT JOIN TaxonBase tb1 ON tb1.id = tr.relatedfrom_id
WHERE trType.uuid = '605b1d01-f2b1-4544-b2e0-6f08def3d6ed'

;

SELECT tr.id, tb1.titleCache fromx , tb2.titleCache tox, tr.*
FROM TaxonRelationship_AUD tr 
INNER JOIN DefinedTermBase trType ON trType.id = tr.type_id 
LEFT JOIN TaxonBase tb2 ON tb2.id = tr.relatedto_id
LEFT JOIN TaxonBase tb1 ON tb1.id = tr.relatedfrom_id
WHERE trType.uuid = '605b1d01-f2b1-4544-b2e0-6f08def3d6ed';

SELECT *
FROM TaxonRelationship_AUD tr 
WHERE tr.id IN (
SELECT tr.id
FROM TaxonRelationship_AUD tr 
INNER JOIN DefinedTermBase trType ON trType.id = tr.type_id 
LEFT JOIN TaxonBase tb2 ON tb2.id = tr.relatedto_id
LEFT JOIN TaxonBase tb1 ON tb1.id = tr.relatedfrom_id
WHERE trType.uuid = '605b1d01-f2b1-4544-b2e0-6f08def3d6ed'
)

Actions #6

Updated by Andreas Müller about 2 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 50

This is generally fixed. Only in integration_reference there is still 1 record left (mail sent to AK).

After release run query again on all production to be on the save side.

Actions #7

Updated by Andreas Müller about 2 years ago

  • Priority changed from New to Priority14
Actions #8

Updated by Andreas Müller about 2 years ago

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

Also available in: Atom PDF