bug #7857
closedUpdate name relationship type representations and symmetrie
100%
Description
since #7809 it is now possible to store name relationships in both directions.
Many of the direct representations are missing an "is xxx". This is necessary to better distinguish from "has xxx" relations.
Also we need to adapt symmetrie. 4 name relationships are defined as symmetrical (misspelling for, orth. var. for , emendation and nom. alt.). Generally none of the name relationships is really symmetrical. Even alternative names do have a kind of preferred name even if the alternative name is not illegitimate.
We should set all these "symmetric" flags to false.
Related issues
Updated by Andreas Müller over 5 years ago
- Related to feature request #7809: Improve namerelationship handling in editor added
Updated by Andreas Müller over 5 years ago
also change "is new combination blocked by" to "has blocking name"
Updated by Andreas Müller over 5 years ago
UPDATE DefinedTermBase
SET symmetrical=0
WHERE uuid IN ('049c6358-1094-4765-9fae-c9972a0e7780', '6e23ad45-3f2a-462b-ad87-d2389cd6e26c',
'c6f9afcb-8287-4a2b-a6f6-4da3a073d5de', 'eeaea868-c4c1-497f-b9fe-52c9fc4aca53')
also update representations
Updated by Andreas Müller over 5 years ago
Andreas Müller wrote:
are also title caches updated?
added implementation
Updated by Andreas Müller over 5 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 50
Updated by Andreas Müller over 5 years ago
- Related to feature request #8006: Improve labels for taxon relationships added
Updated by Andreas Müller about 5 years ago
- Status changed from Resolved to Closed
Updated by Andreas Müller over 2 years ago
- Related to bug #8007: Improve labels for concept relationships added