You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
try to link your concept to another parent concept
Expected behaviour
The added concept should be linked to the second parent
Actual behaviour
The system gives an error: "PUT Request api/v1/tree/concept/1595/broader/1593?t= failed with status 400. This concept does not exist"
So I guess after deleting the only parent, the child is not linked to anything and got lost. Probably it is still saved in the back-end (cannot check this due to access limitations) and one could recreate the linking there. But for front-end users a concept should appear as Top-Level-Concept after removing every parent and not got lost.
In Spacialist instead of the concepts name, now only the URL of the concept is displayed
The text was updated successfully, but these errors were encountered:
Sorry for not answering for so long. When a concept is no longer linked to any parent, it gets deleted. In Spacialist you still see the URL, because in Spacialist concepts are linked by their URL and not their ID.
IMO there are several solutions for this problem:
Warn the user that removing the last parent will delete this concept (if it is not a top level concept as well)
Warn the user and let them decide what to do (same as right clicking on a concept and click on Delete concept)
Replace the x in the broader list with a ...-menu and let the user choose
Delete the concept (as it is now) and reset the view, so it is no longer possible to re-link that non-existing concept
I'd prefer option 1. or 2. (or 3. as it is similar to 2.). What is your prefered option from a user perspective?
Option 2 sounds good. Option 1 would be ok as well, but perhaps the user will quickly click the warning away, without fully understanding it. So, warning the user and wait for a response from the user sounds as a good solution for this.
Is it possible to give the user at this point the choice to make a concept to a top-level concept?
Steps to reproduce
Expected behaviour
The added concept should be linked to the second parent
Actual behaviour
The system gives an error: "PUT Request api/v1/tree/concept/1595/broader/1593?t= failed with status 400. This concept does not exist"
So I guess after deleting the only parent, the child is not linked to anything and got lost. Probably it is still saved in the back-end (cannot check this due to access limitations) and one could recreate the linking there. But for front-end users a concept should appear as Top-Level-Concept after removing every parent and not got lost.
In Spacialist instead of the concepts name, now only the URL of the concept is displayed
The text was updated successfully, but these errors were encountered: