Page MenuHomePhabricator

Add another "Add statement" button on top to ensure consistent position
Open, LowPublic

Tokens
"Burninate" token, awarded by Roy17."Like" token, awarded by Moebeus."Like" token, awarded by Effeietsanders."Pirate Logo" token, awarded by Esc3300."Like" token, awarded by WiseWoman.
Assigned To
None
Authored By
Nemo_bis, Aug 4 2016

Description

I've already reported elsewhere but I don't find the report and it's been too long anyway: we currently have a simple but severe problem in the Wikidata UI, namely that it's extremely hard for users to add a new statement on a very long page. The main reason is that it's nearly impossible to see the "add statement" button unless you know very well where it is, and even if you know it's hard to find (you have to carefully scroll towards the bottom of the page, but not too much or you'll end up among sitelinks). I regularly observe this problem cause big trouble to every user I introduce to Wikidata.

At least one "add statement" button should be placed in a perfectly predictable position which doesn't require scrolling and/or is predictably reachable by following some TOC link or other method which doesn't require trial-and-error scrolling, nor manual typing of anchors, nor ctrl-f.

The easiest and most obvious solution is to add a second "add statement" button, identical to the bottom one, next to the <h2 id="claims" header or slightly above it.


See also: T137774: Inconsistent use of "+ add …" in Wikidata Item view UI, T54136: [Epic] Redesign Item UI for Wikidata repo

Event Timeline

Nemo_bis created this task.Aug 4 2016, 12:08 PM
Restricted Application added a project: Wikidata. · View Herald TranscriptAug 4 2016, 12:08 PM
Restricted Application added a subscriber: Aklapper. · View Herald Transcript
thiemowmde triaged this task as Normal priority.Sep 5 2016, 4:02 PM

How do you make sure then you are not adding a statement that is already there?

Lydia_Pintscher lowered the priority of this task from Normal to Low.Sep 9 2016, 6:19 PM

Yes, I also think one should add a statement to the regarding section.
It seems to me more that the TOC or some other in page navigation is missing and that solving this would also satisfy the need described here.

How do you make sure then you are not adding a statement that is already there?

I don't understand the question. How does a button at the bottom not have the same problem?

Esc3300 added a subscriber: Esc3300.Nov 1 2016, 5:02 PM

I don't get the point of scrolling either. Pages are getting annoyingly long and frequently I add statements that I know aren't there because query.wikidata.org found the items.

In general, I think we urgently need more compact views: depending on the purpose, frequently entire groups of statements are irrelevant for the task at hand and could easily be collapsed or replaced a simple count. Imagine if every item had tons of ELO ratings ;)

Can we add this to T150179 ?

Restricted Application added a subscriber: TerraCodes. · View Herald TranscriptJan 2 2017, 11:54 AM

Let's not add easy tags to tasks that don't have consensus. It'd just lead to newbies being burned by rejecting their code.

Esc3300 added a comment.EditedJan 2 2017, 1:25 PM

Users seem to need it and my lay view is that it shouldn't be too complicated too do. I might be mistaken about the later.

It's not really clear why adding twice the same statement is much of an issue (other than for the user).

Let's not add easy tags to tasks that don't have consensus.

This task has consensus. Not a single person raised objections.

I have raised objections several times when this came up on-wiki.

We could have a keyboard shortcut that power users could use to trigger the add button.

Then there is the question which shortcut!
Alt + A ?

Nikki added a subscriber: Nikki.Jan 3 2017, 4:29 PM

There's T146205 for a keyboard shortcut, btw. The "KeyShortcuts" gadget (which I use) uses just "a", so alt-a would be fairly consistent with that and would probably be usable in situations where the KeyShortcuts gadget isn't (e.g. when text fields or links are focused).

Nemo_bis added a comment.EditedJan 3 2017, 4:41 PM

I'm not interested in a shortcut, please file a separate task for this supposed need of power users. This task is about how to make it easier for users to add new statements, especially inexperienced users who may not be versed in exactly calibrating their scrolling to find the randomly-positioned button.

I have raised objections several times when this came up on-wiki.

Where? I could not find any such discussion and we still don't know what objections you have.

Esc3300 added a comment.EditedJan 3 2017, 5:29 PM

I have raised objections several times when this came up on-wiki.

Where? I could not find any such discussion and we still don't know what objections you have.

I don't recall that either. Why isn't it being linked from this thread?

@Lydia_Pintscher for the sake of clear communication and to avoid mixing roles, you might simply want to decline this request. Otherwise someone does write the code and it ends up getting rejected, "easy" tag or not.

I have not declined it yet because there clearly is an issue we need to solve. I just object to the proposed solution.
My objection is that just adding another button clutters the user interface more (while we've been trying to clean it up) and if it is at the top it will encourage newcomers to not look at existing statements before adding one.

Esc3300 added a comment.EditedJan 4 2017, 11:25 AM

Maybe you could just include a text about that in the warning that already appears to first time users.

Obviously anything can be see as cluttering the interface, but the priority is to have statements added ..

If an additional button adds clutter, I propose to remove the button at the bottom.

I agree that the current "add" buttons at the bottom are hard to find on large pages, and I have seen this put off newbies.
Replacing them with one predictably located bottom on the top sounds like progress to me.

Checking for existing statements with essentially the same information can be quite daunting already for human users (example: https://www.wikidata.org/wiki/Q13561329#P682 ) and should perhaps rather be done automatically before saving - we already have similar mechanisms in place to check whether two items share the same label and description in the given language.

Note that the relevant “+ add” button is quite hard to find — you are looking for the one right at the end of the list of existing statements

https://medium.com/mysociety-for-coders/help-us-find-the-offices-of-heads-of-governments-across-the-world-4558124bcd24

Restricted Application added a subscriber: PokestarFan. · View Herald TranscriptAug 9 2017, 7:42 PM

Maybe it's time to rise the priority of this.

Moebeus added a subscriber: Moebeus.
KaMan added a subscriber: KaMan.Jan 19 2019, 9:21 AM
KaMan added a comment.Jan 19 2019, 9:26 AM

Such feature should consider page layout for lexemes. There is many "add statement" buttons for lexeme, every sense and every form. Single button at the top could be misleading which "add statement" it duplicates.

Roy17 awarded a token.Mon, Aug 12, 7:33 PM