Closed heidivanparys closed 1 year ago
@oscar9 The same problem happens as well with the successor and predecessor. When an item is superseded the successor/predecessor doesn't appear. Probably the best is to add the 3 fields in the init script of the database, or to create on the fly successor/predecessor fields when there is a supersession, but this wouldn't solve the parent problem.
OR
in this page
should be given the option in the dropdown menu for the field type to choose: parent/successor or predecessor.
I followed the step-by-step guidance at https://github.com/ec-jrc/re3gistry/issues/42#issuecomment-829172097 to create a register that can contain hierarchical code lists.
However, what is described for step 2.6 / 3.2 does not work for me.
A workaround was to create a new field with type e.g. “text”, and then change its field type to “parent” (uuid = '7') directly in the database:
That new field could then be used in the item class: