Feature #706
closedTerm Editing
Related issues
Updated by Petr Křemen almost 6 years ago
- Estimated time set to 8.00 h
Implement the term editing functionality:
Acceptance Criteria:
- each term can be edited on the term detail screen
- editing of identifier - text field, with the check for uniqueness across the current vocabulary
- editing of label - text field, with the check for uniqueness across the current vocabulary
- editing of comment - text area
- editing of subterms - a multi-select from the tree of terms of the current vocabulary
- editing of type/s - a multi-select from the tree of terms of the current vocabulary
- editing of source - text field
- the changes are persisted to the server.
- Tested
Updated by Martin Ledvinka almost 6 years ago
- Status changed from New to In Progress
Updated by Martin Ledvinka almost 6 years ago
Resolved with some limitations:
- IRI editing is currently disabled, as it needs to be decided whether it makes sense at all. Basically, it should be possible to edit the fragment part identifying the term only, since the rest of the IRI (the namespace) is derived from the enclosing vocabulary IRI and should not be changed. Also, in case the IRI is edited, it would have to be implemented by removing the old term and persisting a new one, in which case it is a question how the provenance info should look like. Should the persisted term have the original's created date and author?
- Term subterms will have to be handled more generally, to prevent users from creating term cycles etc. Also, as Task #725 specifies, the term hierarchy may be restructured.
Updated by Martin Ledvinka almost 6 years ago
- Status changed from In Progress to Resolved
Updated by Petr Křemen almost 6 years ago
- Status changed from Resolved to Closed
Updated by Martin Ledvinka almost 6 years ago
- Related to Task #743: Support term IRI change added