Project

General

Profile

bug #7857

Update name relationship type representations and symmetrie

Added by Andreas Müller 3 months ago. Updated about 3 hours ago.

Status:
Resolved
Priority:
Highest
Category:
cdm
Target version:
Start date:
10/23/2018
Due date:
% Done:

50%

Severity:
normal
Found in Version:

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

Related to Edit - feature request #7809: Improve namerelationship handling in editor Feedback 10/08/2018

History

#1 Updated by Andreas Müller 3 months ago

#2 Updated by Andreas Müller 3 months ago

also change "is new combination blocked by" to "has blocking name"

#3 Updated by Andreas Müller 3 months 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

#4 Updated by Andreas Müller about 3 hours ago

are also title caches updated?

#5 Updated by Andreas Müller about 3 hours ago

Andreas Müller wrote:

are also title caches updated?

added implementation

#6 Updated by Andreas Müller about 3 hours ago

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

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 40 MB)