Page MenuHomePhabricator

[Story] Highlight already-existing properties while adding a new statement on an item to avoid duplicate edits
Open, NormalPublic

Description

When adding a property to Wikidata items using the web interface, it is easy to unintentionally create a duplicate property entry - particularly on large items, where you may not notice that the property already existed.

This isn't a major problem - many properties are intended to have multiple values, after all! - but can be a little frustrating:

a) it can be confusing for the user, as after creating the new Pxxx line it "snaps up" to display alongside the existing Pxxx line, and so may seem like it's not been added when they look at the end of the page;
b) it means someone has to do a little work in future removing the duplicate.

A way round this might be to highlight in some way that a property Pxxx already exists. For example, when a user goes to add a new property to an item, and selects a property, the interface could check if it exists. If so, there's various ways to highlight that this is a possible duplicate:

  • the blue outline box could turn to orange;
  • a note could appear on the left underneath the property name: "An entry for P569 (Date of birth) already exists for this item".
  • the existing lines could "snap down" to be displayed alongside the new line for that item

Current workaround: Krbot removes some duplicates

Event Timeline

agray created this task.May 4 2016, 12:14 PM
Restricted Application added subscribers: Zppix, Aklapper. · View Herald TranscriptMay 4 2016, 12:14 PM

the existing lines could "snap down" to be displayed alongside the new line for that item

This is the best solution (or alternatively, scroll up to the existing box for that property).

Yes highlighting the case but still allowing it where it makes sense sounds good to me too. We'll do that but it'll take time. Thank you for the idea!

Lydia_Pintscher renamed this task from Suggestion: Identify already-existing properties on an item to avoid duplicate edits to [Story] Highlight already-existing properties while adding a new statement on an item to avoid duplicate edits.May 4 2016, 5:11 PM
Lydia_Pintscher triaged this task as Normal priority.
BrillLyle added a comment.EditedMay 19 2016, 1:06 PM

Is it possible to alphabetize the order of the elements? Using alphabetizing as an organizational principle would also prevent duplication.

Right now it's unclear -- at least to me -- what the order is for Authority Control elements. And I don't get why ISNI is up in a separate section.

Forgive my question if it's dumb. I'm an newish Wikidata end-user obsessed with Authority Control, especially the old school iteration. Am obviously not a programmer. :-)

Best,

– Erika
User:BrillLyle

Those are unrelated to this ticket but quickly:

  • ISNI is still waiting for conversion because someone objects to it
  • statement order will be worked on. Alphabetical only makes sense for identifiers and even there it is problematic because of different languages. We'll have to see how to handle it.

Thanks so much for the response, @Lydia_Pintscher

re: order of statements:
Ooh I hope the Alphabetical ordering can work. Wouldn't the Authority items all be static names depending upon their origin? Their names don't change even though they might appear on other language Wikis, correct?

Thanks again!

– Erika
User:BrillLyle

Those are unrelated to this ticket but quickly:

  • ISNI is still waiting for conversion because someone objects to it
  • statement order will be worked on. Alphabetical only makes sense for identifiers and even there it is problematic because of different languages. We'll have to see how to handle it.
abian awarded a token.Aug 21 2016, 9:29 AM
Esc3300 added a comment.EditedAug 30 2016, 1:52 PM

A way to spot it was that the statement didn't get added at the end of the list, but "disappeared" to earlier statements.

If the new sorting gadget is activated, one can't just check the last statement on the list.

Esc3300 updated the task description. (Show Details)Aug 30 2016, 1:54 PM

the existing lines could "snap down" to be displayed alongside the new line for that item

This is the best solution (or alternatively, scroll up to the existing box for that property).

T142082#2623859 seems to indicate that fixing this feature request may make the developers more comfortable with fixing T142082. It would be nice if we started from the simpler things, of course. :)