Closed RieksJ closed 7 months ago
The check for duplicates, which determines if an entry overwrites another entry within a provisional MRG, currently happens according to the termid
property of an entry. I believe this issue stems from that, because the rename action doesn't alter the termid
. I suppose this could be remedied by re-triggering the termid
creation after a rename of the term
or termType
.
yes, please!
@Ca5e : This is (still) not fixed.
The SAF says this:
The log I just generated says this:
I didn't expect to see (line 61) that a term got overwritten. And if the rename
instruction worked, then indeed the mrg-entry 'action' got overwritten.
When using the MRGT on the tev2-specifications repo the result is this:
When generating
mrg.tev2.documentation.yaml
, the first instruction selects the termaction
from theessif-lab
scope. Then, the subsequentrename
instruction tells it to rename the term, modifying fieldsid
andterm
to becomeact
, and modifying theformphrases
field to becomeact{ss}
.However, when I check the resulting mrg-file, I cannot find an entry for the renamed thing.
Note that the following termselection instruction again imports
action
from essif-lab. This should not overwrite the (renamed)act
entry, but seems to do so.