bug #9322
Remove invalid designation taxon relationship
100%
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
Associated revisions
remove create/change to invalid designation handler
ref #9322 remove invalid designation relationship from cdmlib
ref #9322 adapt TaxEditor to removed invalid designation relationship
ref #9322 adapt vaadin to removed invalid designation relationship
ref #9322 adapt TaxEditor to removed invalid designation relationship (cont.)
ref #9322 adapt TaxEditor to removed invalid designation relationship (cont. 2)
ref #9322 adapt TaxEditor to removed invalid designation relationship (cont. 3)
ref #9322 adapt BerlinModelOccurrenceSourceImport to removed Invalid Designation
ref #9322 removing taxon relationship invalid designation from portal code
ref #9322 handle also AUD table in SingleTermRemover and connect the schema updater
ref #9322 changing test case for invalid designation to misapplied name
ref #9322 fix the bug for deleting inverse representations in TermRemover
History
#1 Updated by Andreas Müller 11 months ago
- Related to task #8055: Correct formatting for invalid designations added
#3 Updated by Andreas Müller 11 months ago
- Related to feature request #7761: Invalid designations should be displayed like misapplied names in name editor added
#4 Updated by Andreas Müller 11 months ago
- Related to feature request #6394: Allow additional taxon relationships in TaxEditor to be handled similar to misapplications added
#5 Updated by Andreas Müller 11 months 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'
)
#6 Updated by Andreas Müller 11 months 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.
#7 Updated by Andreas Müller 11 months ago
- Priority changed from New to Priority14
#8 Updated by Andreas Müller 11 months ago
- Status changed from Resolved to Closed
- % Done changed from 50 to 100
