Story: As a user, I want to add a value to a statement
What happens: If I add a value to a statement with a property which values are restricted to items (let's say I want to add to the item Harry Potter that he is Property:MemberOf the Item:Gryffindor) , creation of the value fails silently if that item does not yet exists: The save link remains gray, there is no notification of the kind of error.
Even if I notice the problem, my workflow is interrupted; I can't carry on creating these relations (like I could similarly on Wikipedia, where such would result in red links) but must cancel or create the other, to-be-linked-to item first.
What should happen:
- There should be a notification e.g. if the user clicks "save" which informs the user that the input could not be matched to an item and that this item could be created.
- Possibly, it would make sense to allow saving anyway and allow to match the input with an item later. So if I edit Harry Potter’s "educated at" value and I want to add "Hogwarts" but the item Hogwarts does not exists yet, I still can save, but the value is grayed out (or similar) and if I edit, I can match it again to the (hopefully) now created item.
Usability Guidelines: User Control and Freedom, Help users recognize, diagnose, and recover from errors