fuddl
The relationship direction switcher (⬆/⬇) is not intuitive
Hi there,
I found the grey arrow in the UI not quite intuitive.
It would be great to amend the arrow with its meaning, either textual or graphical.
Cheers! Robert
Context
clicking the arrow currently flips the direction of the statement:
| Before clicking the arrow | After clicking the arrow |
|---|---|
 |
 |
Here are some UX/UI-Improvment tips - this is my brainstorming on this - so maybe it is helpful for you
- it needs to be clear that the information will be import to the object in Wikidata
- property bar has to be more conspicuous positioned (Are there property suggestions when entering something?)
- it is not recognizable that something can be added to object A or object B with the arrow Icon- maybe the Icon needs to exchange by an "Connection Icon"
- turning the arrow is not intuitive, maybe split the function e.g. 3 fields next to each other, the Q-numbers can be selected directly from the webpage by clicking on it -> right into a "fixed field" - maybe then the Q-numbers shows up as clickable button. For the propertíes you'll have a writing field that shows suggestions as a dropdown
Object 1 Q123 (fixed field) | Property field (input field) | Object 2 Q345 (fixed field)
Object 2 Q345 (fixed field) | Property field (input field) | Object 1 Q123 (fixed field)
- Setting up a help article or tutorial video on Youtube - How to use the extension - I'm sure that some people would use such a help
- it is not recognizable that something can be added to object A or object B with the arrow Icon- maybe the Icon needs to exchange by an "Connection Icon"
The interface might not be exclusive to connection type claims in the future. It might also support all the other data types in the future. Having a separate interface for different data types might not be intuitive for wikidata editors.
The switch direction feature however only makes sense for entity ids. I'd propose to additionally append a checkbox with a textual hint to the bottom of the form. I'll make a draft.
For the propertíes you'll have a writing field that shows suggestions as a dropdown
this dropdown would contain >1300 items for entity ids alone and this number is only going to grow. I'd rather stick to the autocomplete.
- Setting up a help article or tutorial video on Youtube - How to use the extension - I'm sure that some people would use such a help
That's a good point, but the interface should be in a more final/less drafty state before this video is done. 😬😅
For the time being, a readme file #4 might do the job more effectively?
@Nomi-1 @robertgiessmann: How about augmenting the entity claim adding tool with a simple texual clue that only appears when linking to an entity id? That would be easy.
| Example | Description |
|---|---|
 |
Unflipped |
 |
Flipped |
The arrow at first looked to me like a push to. I would read it in a way, that "arrow Wikidata logo" would make sense.
May I suggest a UI, where the order subject, predicate, object is always left to right or top to bottom. (for the add statement interface, as well as the backlink interface) In this case a switch button would result in the item for the viewed page would move down.
