Wikidata:Property proposal/sorting weight
sorting weight
[edit]Originally proposed at Wikidata:Property proposal/Generic
Description | when listing multiple properties, properties with a higher sorting weight are supposed to be shown before properties with lower sorting weight |
---|---|
Data type | Number (not available yet) |
Example 1 | instance of (P31) → 100000 |
Example 2 | subclass of (P279) → 9999 |
Example 3 | occupation (P106) → 1000 |
Motivation
[edit]We have currently multiple cases where properties have to be sorted. When displaying the normal properties and external-id properties on a page they have to be sorted.
When suggesting properties to the user according to properties for this type (P1963) there's a need for sorting. The proposed property can be used as a qualifer to help sort that list.
For qualifiers we might have in future a solution that uses sources the suggested qualifiers from qualifier for this property (P8379) where the sort order can also be specified with this property.
WikiProject Properties has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead. ChristianKl ❪✉❫ 10:40, 27 June 2020 (UTC)
Discussion
[edit]- Support seems reasonable though I guess it can be a bit controversial as to what the right value should be. Iwan.Aucamp (talk) 12:19, 27 June 2020 (UTC)
- Couldn't we just use MediaWiki:Wikibase-SortedProperties for this? Having two different sorting schemes feels like it's going to get complicated. Andrew Gray (talk) 14:11, 27 June 2020 (UTC)
- I don't think Wikibase-SortedProperties is a good solution for multiple reasons and that it would be best to deprecate it sooner or later.
- Having the data within properties makes it easier to discover how the sorting works for Wikidata users.
- We will have federated Wikibase properties in the future. Having a concept of sorting weight allows sorting of properties from different Wikibases in a consistent manner without having to define all the sorting in one Wikibase.
- Finally, I want a way that can be set more context dependent on properties for this type (P1963) and qualifier for this property (P8379). ChristianKl ❪✉❫ 18:08, 27 June 2020 (UTC)
- I think there's an argument to be made for centralised sorting being better - with values on a per-property basis, it's much harder to group similar properties together, ensure they are kept in a consistent order, and so on. It feels to me like it would be more difficult to get a broad overview this way around, though I take your point about federated properties. But to be honest I don't really have a strong opinion, whatever works is fine. :)
- I'm still not clear how this property would work, though - is the idea we create the property now and then develop a sorting mechanism which would use it? Andrew Gray (talk) 18:48, 30 June 2020 (UTC)
- Support I support this --Uni3993 (talk) 07:29, 8 March 2021 (UTC)
- There is already some sort of "weighted sorting" being done by the Wikibase (?) software when adding properties to items. Does that not suffice? —MisterSynergy (talk) 17:06, 27 June 2020 (UTC)
- The goal is to have a system where it's easier for users to change the sorting oder. ChristianKl ❪✉❫ 18:09, 27 June 2020 (UTC)
- The community managed approach does not work particularly well with MediaWiki:Wikibase-SortedProperties, as opposed to the built-in suggestion mechanism. As far as I understand, the software sort of anticipates the best order of suggested properties based on the data present in an item. This seems much more sophisticated than a static list, where users might even try to push their favorite properties to the front. —MisterSynergy (talk) 18:56, 27 June 2020 (UTC)
- It feels to me like there's some issue with it being intransparent of how the system actually works. Do you know whether it's documented somehow?
- I think it would be great if it would both be documented and also possible for humans to decide what the best order happens to be. ChristianKl ❪✉❫ 20:27, 27 June 2020 (UTC)
- It's called property suggester (Q86989962) (related: Extension:PropertySuggester (Q30101250), Extension:WikidataEntitySuggester (Q21679299), Help:Suggesters and selectors#Property suggester, …). You can use these items to search for more documentation on mediawiki.org or phabricator—I am not aware whether there is enough of it, however. —MisterSynergy (talk) 20:41, 27 June 2020 (UTC)
- The community managed approach does not work particularly well with MediaWiki:Wikibase-SortedProperties, as opposed to the built-in suggestion mechanism. As far as I understand, the software sort of anticipates the best order of suggested properties based on the data present in an item. This seems much more sophisticated than a static list, where users might even try to push their favorite properties to the front. —MisterSynergy (talk) 18:56, 27 June 2020 (UTC)
- The goal is to have a system where it's easier for users to change the sorting oder. ChristianKl ❪✉❫ 18:09, 27 June 2020 (UTC)
- Is this intended to apply to identifiers too? In general I'd like to see further information about how these priorities should be decided. --99of9 (talk) 02:16, 28 June 2020 (UTC)
- Yes, the idea would be that it can also be used to sort identifiers. ChristianKl ❪✉❫ 08:55, 30 June 2020 (UTC)
- The idea is to specify semantics about how sorting priorities can be expressed here. Later, when there are disagreements about how to decide the priority in a certain domain we can create policy to solve that. ChristianKl ❪✉❫ 17:11, 20 November 2020 (UTC)
- How are we going to determine the weights? BrokenSegue (talk) 16:43, 7 November 2021 (UTC)
- Same wonder here. And what about a need of weights differentiated according to certain topics ? EG paintings with sorting of properties different from buildings? Bouzinac 💬●✒️●💛 11:42, 9 December 2021 (UTC)
- I guess that will be a curation decision by each project. --- Jura 15:07, 10 December 2021 (UTC)
- Oppose unclear determination of value Nepalicoi (talk) 08:39, 8 March 2022 (UTC)
- Oppose per Nepalicoi - unclear how weight is determined, and, per Bouzinac, different use cases / different interests are not served by a singular weight per property. --Tagishsimon (talk) 03:43, 4 August 2022 (UTC)
- @ChristianKl, Iwan.Aucamp, Andrew Gray, MisterSynergy: @BrokenSegue, Bouzinac, Jura1, Nepalicoi, Tagishsimon: Not done It's been over 2 years with no clear plan and no strong support and many issues unresolved. Time to retire this. If any of you still think this is a good idea please consider the issues raised above and come back with a much clearer proposal. Support from the development team indicating they would actually implement this would be a good idea too (though I suppose a gadget could do it for those who want it). ArthurPSmith (talk) 18:35, 4 August 2022 (UTC)
- @Uni3993: missed a user in my ping. ArthurPSmith (talk) 18:36, 4 August 2022 (UTC)