Wikidata:Suggester ranking input/Archive

 Done Ranking of male for P21

• Property: sex or gender (P21)
• What I type: "male"
• What I get: the desired item male (Q6581097) appears in 3rd position
• What I would expect: the desired item male (Q6581097) appears in first position
• Details: Interface set up in English. (but also same for German --Jcornelius (talk) 01:01, 24 December 2017 (UTC))
• Suggested by: ChristianKl

• This happens because male (Q6581097) has no sitelinks, and male organism (Q44148) has tons of them. Text is a match for both, and we consider items with more sitelinks more important. They both have lots of incoming links, though male organism (Q44148) has less (only 6082) but it is not enough to overcome the difference between "no sitelinks at all" and "lots of them". Need some idea here how to make the distinction. Smalyshev (WMF) (talk) 05:28, 9 January 2018 (UTC)

@Smalyshev (WMF): "we consider items with more sitelinks more important". Why, especially given the harm it does to search results, would we choose to do this? Why do we not give much more weight to the number of wikidata items that use e.g. male (Q6581097) as a statement value? --Tagishsimon (talk) 20:30, 2 April 2018 (UTC)

 Done Ranking of female for P21

• Property: sex or gender (P21)
• What I type: "female"
• What I get: the desired item female (Q6581072) appears in 2nd position
• What I would expect: the desired item female (Q6581072) appears in first position
• Details: Interface set up in English.
• Suggested by: ChristianKl

• Probably the same reason as male (Q6581097). Smalyshev (WMF) (talk) 05:28, 9 January 2018 (UTC)

 Done Ranking of femenino for P21

• Property: sex or gender (P21)
• What I type: "femenino"
• What I get: the desired item female (Q6581072) appears in 2nd position
• What I would expect: the desired item female (Q6581072) appears in first position, instead of feminine (Q1775415).
• Details: Interface set up in Spanish.
• Suggested by: strakhov

 Done Ranking of masculino for P21

• Property: sex or gender (P21)
• What I type: "masculino"
• What I get: the desired item male (Q6581097) appears in 2nd position
• What I would expect: the desired item male (Q6581097) appears in first position, instead of masculine (Q499327).
• Details: Interface set up in Spanish
• Suggested by: strakhov

 Done General behaviour: items that fit one-of property constraint should come first

• Property: Any property that uses value-type constraint (Q21510865) or one-of constraint (Q21510859). P21 above is a good example.
• What I type: e.g. "female"
• What I get: feminine (Q1775415), which violates P21's one-of constraint (Q21510859) is listed first.
• What I would expect: female (Q6581072), which fits the constraint, should come first.
• Details: Because sex or gender (P21) has one-of constraint (Q21510859), the items listed in the constraint should come first.
• Suggested by: Deryck Chan (talk) (I'm just summarizing the general behaviour we want from the suggester)

Which language to do you that you get feminine (Q1775415)? ChristianKl ❪✉❫ 14:11, 25 December 2017 (UTC)

 Done inventory number (P217) should suggest collection (P195)

• Property: inventory number (P217)
• What I type: Once I have added inventory number (P217) property, and I click "+ add qualifier", and start typing c-o-l-l... for adding the "collection"
• What I get: at "C" the first suggestions are canonical SMILES (P233) and made from material (P186). At "Co" the first suggestions are made from material (P186) and cast member (P161). At "Col" the first suggestion are Cologne phonetics (P3879) and collection (P195). Only at "Coll" does collection (P195) become the first suggestion.
• What I would expect: collection (P195) should be the immediate first suggested qualifier - especially since the use of inventory number (P217) without also a collection (P195) statement is considered a constraint violation.
• Suggested by: Wittylama (talk) 15:45, 27 December 2017 (UTC)
  • ...or, more generally, qualifiers that fit required qualifier constraint (Q21510856) and allowed qualifiers constraint (Q21510851) stipulations should come first in the qualifier suggester box! Deryck Chan (talk) 18:25, 20 January 2018 (UTC)

 Done Qualifier not suggested on creation

• Property:
• What I type: start creating some statement, including qualifiers
• What I get: no suggestions for qualifiers
• What I would expect: same suggestions for qualifiers when trying to add a qualifier to an existing statement
• Details:
• Suggested by:
  --- Jura 15:35, 25 March 2018 (UTC)