As a user I want the statements in an item to be consistently ordered across items. The order should move more important/useful/general infos to the top.
|· · ·|
|Open||None||T87316 [Story] Redesign statement section|
|Resolved||None||T61951 Sort statement: Up arrow and question mark nearly melted into each other|
|Invalid||None||T59918 [Story] show diffs for ordering changes|
|Open||None||T125493 [RfC] Order of data in Wikidata|
|Resolved||Lydia_Pintscher||T146637 Wikidata 2016 Q4 goals|
|Resolved||thiemowmde||T99243 [Story] consistent order of statements in an item|
|Invalid||Bene||T98375 [Task] ChangeOpClaim should handle indices per property id|
|Invalid||None||T74297 [RFC] Have API return and accept lists instead of maps to maintain order|
|Resolved||Lydia_Pintscher||T102792 [Task] Research ways to order properties on an item page|
|Resolved||Lydia_Pintscher||T129244 [Story] create gadget to try out global sort order|
|Resolved||Glorian_Yapinus||T147062 [Task] create initial order of all properties for gadget|
|Resolved||thiemowmde||T150788 [Task] Apply property ordering in EntityView|
|· · ·|
We need to do more thinking here before implementation starts. How do we order? Viable options I have so far:
- We have one big ordered list of all properties and this one list is applied to all items
- We let people decide the order on each individual item.
Ordering per class in Wikibase is out.
I think users will vote for option 1. It's tempting. "All we need to do to solve the problem of the world not being in order is to have this discussion one time, then it will be solved forever." Years later new users will get frustrated because they have good arguments to change the order but their arguments can not be heard because this will "magically" change the order on all existing items and will make some longtime users upset. This boils down to the same arguments why Wikibase supports pineapple as a gender and a gender on vegetables: the world is not in order.
I suggest to:
- let people decide the order on each individual item.
- have a preferred order and position when (and only when) adding a new property to an item. This is similar to what the property suggester does. You can stick with the suggestion if it's fine or you simply don't care, but you don't have to.
I agree with Thiemo that a fixed order defined in a central place (maybe even not on-wiki as a setting) is not a good idea. I like the idea of suggesting a position but I'm not sure on which data this suggestion should be based on? Having a fixed list defined for suggestions seems not as a good idea per the argument agains #1. As you mentioned property suggester, we might use the positioning on other items for such a suggestion but as there is no common order in place at the moment, we first have to order a bunch of items so that this would produce useful data.
What we might consider is a bot which runs once over all items and orders the statements but then lets the users decide if they want to change the order. This has to be dicussed with the community.
Another thing we should think about is ordering the statements by datatype. This makes sense for the identifier datatype (obviously) but also the other statements can be grouped by datatype.
A final aspect I have in mind is to recognize qualifiers for ordering. This applies for several statements for one property id, for example a list of presidents, where they should be ordered by start/end data. However, this should perhaps also be done by a bot rather than by Wikibase itself.