Property talk:P5008

From Wikidata
Jump to navigation Jump to search

Documentation

on focus list of Wikimedia project
property to indicate that an item is of particular interest for a Wikimedia project. This property does not add notability. Items should not be created with this property if they are not notable for Wikidata. See also P6104, P972, P2354.
RepresentsWikiProject focus list (Q51539995)
Data typeItem
Usage notesThis property does not add notability to items. Items should not be created with this property if not otherwise notable for Wikidata. Don't use it when querying another property returns a comparable list.
ExampleDerek Walcott (Q132701)Black Lunch Table (Q28781198)
Susanne S. Renner (Q98268)PlantsAndPeople (Q31805038)
Cornelius Gurlitt (Q15143412)
University of Washington Department of Scandinavian Studies (Q98429907)WikiProject PCC Wikidata Pilot/University of Washington (Q98970039)
See alsocatalog (P972), maintained by WikiProject (P6104), has list (P2354)
Lists
Proposal discussionProposal discussion
Current uses
Total1,120,037
Main statement1,120,015>99.9% of uses
Qualifier4<0.1% of uses
Reference18<0.1% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Value type “WikiProject (Q16695773): This property should use items as value that contain property “instance of (P31)”. On these, the value for instance of (P31) should be an item that uses subclass of (P279) with value WikiProject (Q16695773) (or a subclass thereof). (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P5008#Value type Q16695773, SPARQL
Scope is as main value (Q54828448): the property must be used by specified way only (Help)
List of violations of this constraint: Database reports/Constraint violations/P5008#Scope, hourly updated report, SPARQL
Allowed entity types are Wikibase item (Q29934200), Wikibase property (Q29934218): the property may only be used on a certain entity type (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P5008#Entity types

Discussion[edit]

"Don't use it when querying another property will give a comparable list."[edit]

Could this sentence be clarified? It's a bit vague. Thank you! --CKThomas

@CKThomas: This is a belated reply, but I understand it to mean that if, say, you're working on an article about a university, you don't generally need to add this property, because the university will have "instance of" -> "university", and that'll mean that it'll show up in the higher education project's focus list already, making this property redundant. Cheers, {{u|Sdkb}}talk 17:03, 30 March 2023 (UTC)[reply]

Remove "one-of constraint"[edit]

The one-of constraint (Q21510859) on this property does not scale. I suggest to remove it from this property, and rely on the already existing value-type constraint (Q21510865) only which may or may not be tweaked a bit (using WikiProject focus list (Q51539995) instead of WikiProject (Q21025364) as a value, which would require some changes in focus list items as well [1]). Thoughts? —MisterSynergy (talk) 12:20, 6 November 2019 (UTC)[reply]

Besides, I don't see an advantage of doing that.
The item seems somewhat ill-defined. It's a subclass of "Wikiproject".
If there are just one or two items with the value (e.g. on the notorious Basshunter) it's unlikely an actual focus list.
How do we determine that the focus list is no longer relevant? --- Jura 12:42, 6 November 2019 (UTC)[reply]
I don't understand most of that, your comment is too short:
So, can you please clarify? Thanks, MisterSynergy (talk) 12:59, 6 November 2019 (UTC)[reply]
It refered to your proposal to replace the one-of-constraint with a type constraint. Sorry about the stray word that remained after I re-organized the text .. ;)
I don't see how P6104 is relevant here.
Focus lists are meant to help people develop content .. if that isn't done, the statements are no longer needed. If there is just one or two items on such a focus lists, the property isn't correctly used. --- Jura 13:06, 6 November 2019 (UTC)[reply]
Well, the disadvantage of the "one-of constraint" is that we do not have a closed (and relatively short) list of candidates. Anyone can create new focus lists and add them here, and at some point the software will not be able to handle all the qualifiers. In other words: this constraint type does not scale. The "value type constraint" does not have this problem, but allows the same sort of oversight.
Items can be permanently on focus lists, as content development is not something necessarily something which is being finish within a confined timeframe. So, whether or not the statements are "no longer needed" is difficult to decide, and they do not really harm anyone. —MisterSynergy (talk) 13:11, 6 November 2019 (UTC)[reply]
I have removed this constraint, as usage of the property may be tracked via "list of values".--GZWDer (talk) 11:32, 11 March 2020 (UTC)[reply]
It doesn't seem to work. There are clear misuses of the property such as with Q66895890 that don't get identified that way. These otherwise get unnoticed. --- Jura 11:49, 11 March 2020 (UTC)[reply]
How is it a misuse? "focus list" may be a stub, if it is well maintained.--GZWDer (talk) 05:55, 12 March 2020 (UTC)[reply]

Removal of 'as main value' property scope constraint[edit]

I want to use P5008 as a qualifier of is a list of (P360) for wikipedia Women in Red redlist items - https://w.wiki/CTb - such as at Q65184008#P360, where the qualifiers gender=female, occupation=psychologist and crucially "on focus list of Wikimedia project"=Women in Red identify the set of items we expect to find in the list.

Is there a good reason to retain the 'as main value' property scope when this use case demonstrates a valid use of the property as a qualifier? --Tagishsimon (talk) 03:45, 23 November 2019 (UTC)[reply]

  • Such a P5008 qualifier does not really qualify the mainsnak value; thus, placing it in the qualifiers does not seem to be appropriate
  • P5008 includes the entire item to a WikiProject focus list, not just single statements
  • It is meant to provide simple access to the list, with "?item wdt:P5008 wd:Qxxx"; even SPARQL beginners can get this right in many cases. If we now start to allow qualifier use, one needs to use UNION and this would complicate things a lot for list users.
I don't think we should change this constraint. --MisterSynergy (talk) 09:57, 23 November 2019 (UTC)[reply]

In focus of project or in list or maintained...?[edit]

What's clear difference from maintained by WikiProject (P6104)? --Infovarius (talk) 12:04, 8 June 2022 (UTC)[reply]

related discussion: Wikidata_talk:WikiProjects#Consistency_in_tagging_WikiProjects_via_P5008_and/_or_P6104 - Valentina.Anitnelav (talk) 12:46, 7 July 2023 (UTC)[reply]