Wikidata:Property proposal/autosuggest value

autosuggest value edit

Originally proposed at Wikidata:Property proposal/Generic

Done: autosuggest value (P11889) (Talk and documentation)

Description	qualifier for P1963 that suggests which values should be autosuggested to the user that uses the property for items that are instances of the subject
Data type	Item
Example 1	human (Q5) properties for this type (P1963) sex or gender (P21) → female (Q6581072)
Example 2	horse (Q726) properties for this type (P1963) sex or gender (P21) → female organism (Q43445)
Example 3	species anatomical structure type (Q113131459) properties for this type (P1963) found in taxon (P703) → Homo sapiens (Q15978631)
Example 4	book (Q571) properties for this type (P1963) copyright status (P6216) → public domain (Q19652)

Motivation edit

According to a discussion in the project chat, currently the one-of-constraint is commonly used to create the suggested values for properties. Given that each property can have different suggested values depending on the class of the item it's used on, I suggest to store that information as a qualifier for properties for this type (P1963) ChristianKl ❪✉❫ 18:31, 16 September 2022 (UTC)[reply]

Discussion edit

Support for the idea in general - however our developers seem to have been generally reluctant to take account of the Wikidata class system when developing features (for example a truly useful feature would be to allow class filters on search...) so I think we might want to run this by some of the dev team to see what exactly would actually be likely to be supported in the UI for this, before settling on the data model and specifying a property like this. ArthurPSmith (talk) 18:20, 19 September 2022 (UTC)[reply]
@Manuel Merz (WMDE) Do you have an opinion? ChristianKl ❪✉❫ 09:46, 21 September 2022 (UTC)[reply]
Something like this is needed, but can it also work for qualifier props (eg "reason for deprecation") applicable to any prop? --Vladimir Alexiev (talk) 14:21, 23 September 2022 (UTC)[reply]
Can you describe how you would want it to behave with qualifier props? ChristianKl ❪✉❫ 20:08, 7 October 2022 (UTC)[reply]
Support either way, can be used for external programs if not integrated into the main site AntisocialRyan (Talk) 14:22, 24 September 2022 (UTC)[reply]
Comment really depends if the software is going to be updated to actually use it. Wouldn't mind if it gets created earlier, but the current system shouldn't be removed until the new system is up and running. Multichill (talk) 16:08, 8 October 2022 (UTC)[reply]
@Lydia Pintscher (WMDE): Can you give a perspective on whether or not such a feature could be used by Wikibase? If you are not the right person to ask, who is? ChristianKl ❪✉❫ 22:34, 8 October 2022 (UTC)[reply]
I'm the right person, yes :)

I'm not sure I understand exactly what we're trying to achieve. Could you clarify for the sex/gender example for example which statement would be on which Item or Property? Thanks! Lydia Pintscher (WMDE) (talk) 16:39, 10 October 2022 (UTC)[reply]
@Lydia_Pintscher_(WMDE): Not the proposer, but it would be on horse (Q726) as a qualifier to properties for this type (P1963). There would potentially be numerous qualifiers of this property. -wd-Ryan (Talk/Edits) 23:37, 26 October 2022 (UTC)[reply]
Thank you! And then the intention would be that I get "sex or gender" suggested as a new statement to add on an Item that is "instance of: horse" based on these qualifiers on the Item for horse? Lydia Pintscher (WMDE) (talk) 15:55, 28 October 2022 (UTC)[reply]

@Lydia Pintscher (WMDE) currently one-of constraint (Q21510859) gets used as a source for autosuggestion. We have added a one-of-constraint to sex or gender (P21) to have those autosuggestions. This is problematic because we don't really want to declare that anyone who has a gender identity that's not within our list has an invalid gender identity which is what the one-of-constraint implies.

There's currently a statement on human (Q5) with properties for this type (P1963). I propose to add a qualifier to that statement and have that statement as the source for autosuggest values. ChristianKl ❪✉❫ 20:31, 1 November 2022 (UTC)[reply]
Oppose We have enough to do already without having to manually maintain autosuggest values. It would also be confusing to users and of very limited benefit to have the property if it's not supported by Wikibase. I think it would be better to automatically suggest common values for a property, ideally taking in account when the instance of (P31)/subclass of (P279) values match, like how the property suggester works. - Nikki (talk) 12:47, 27 December 2022 (UTC)[reply]
@Nikki, I don't think it is technically possible to suggest good values for occupation (P106)/genre (P136)/language of work or name (P407)/sport (P641) - it is just too computationally expensive to calculate "select top N values" for millions of statements from one side or suggest something useful out of millions (in some cases) of P31/P279 items from other side... --Lockal (talk) 14:18, 5 January 2023 (UTC)[reply]
Support would be quite useful without introducing new constraints HeliosSunGod (talk) 07:06, 3 January 2023 (UTC)[reply]
Support. Previous discussion: Wikidata:Project_chat/Archive/2022/09#Missing_selection_options_for_occupation_(P106). However if accepted, it requires a new task in https://phabricator.wikimedia.org/project/profile/2796/. Right now autocompletion of occupation (P106)/genre (P136)/language of work or name (P407)/sport (P641)/other is based on deprecated constraints, and it looks like a hack, not like an intended solution. --Lockal (talk) 14:18, 5 January 2023 (UTC)[reply]

@ChristianKl, ArthurPSmith, Vladimir Alexiev, AntisocialRyan, Multichill, Lydia Pintscher (WMDE): @HeliosSunGod, Lockal: Done: autosuggest value (P11889). Feel free to correct the examples if they have been added in the wrong way. Regards Kirilloparma (talk) 04:09, 15 July 2023 (UTC)[reply]