Make the linking of entities and concepts more efficient / comfortable / flexible.
Currently we simply use a ComboBox or Dropdown box, but this does not scale.
AutoComplete fields may be the next step, but the user might prefer actually seeing the concept tree maybe switch between KBs, etc.
@reckart wrote:
The main question is, how to make the concept choice efficient for the user. I have made a little mockup of what is currently spooking around in my head. We could probably reuse e.g the concept tree and the instance selection panel from the KB page for such a component.
@rcffc wrote:
About the mockup: I have a different idea.
When the user types nothing, the lower part contains all concept & instances in the KB. By typing, the user can narrow down the concepts by matching the name of their instances, with the goal to select the desired entity. After clicking the entity, the entity will be linked, which has the same effect as clicking one of the suggestion bubbles under the search field.
Make the linking of entities and concepts more efficient / comfortable / flexible.
Currently we simply use a ComboBox or Dropdown box, but this does not scale.
AutoComplete fields may be the next step, but the user might prefer actually seeing the concept tree maybe switch between KBs, etc.
@reckart wrote: The main question is, how to make the concept choice efficient for the user. I have made a little mockup of what is currently spooking around in my head. We could probably reuse e.g the concept tree and the instance selection panel from the KB page for such a component.
@rcffc wrote:
About the mockup: I have a different idea. When the user types nothing, the lower part contains all concept & instances in the KB. By typing, the user can narrow down the concepts by matching the name of their instances, with the goal to select the desired entity. After clicking the entity, the entity will be linked, which has the same effect as clicking one of the suggestion bubbles under the search field.