Property talk:P9073
Documentation
value suitable for "stated in" (P248) when property is used in references to refer to the primary publication/website/database associated with the property
List of violations of this constraint: Database reports/Constraint violations/P9073#Scope, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P9073#allowed qualifiers, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P9073#single best value, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P9073#Value type Q35127, Q386724, Q3331189, Q2352616, Q8513, Q1789476, Q1277575, Q121182, Q7094076, Q1334294, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P9073#Item P2302, search, SPARQL
![](http://178.128.105.246/cars-http-upload.wikimedia.org/wikipedia/commons/thumb/a/a6/Pictogram_voting_comment.svg/40px-Pictogram_voting_comment.svg.png)
External-ID-properties used as reference without P9073. TODO: add P9073 statement to property entity, create item when non-existing (Help)
Violations query:
SELECT ?item ?ms ?msinstance # ?itemLabel ?msLabel ?msinstanceLabel WHERE { hint:Query hint:optimizer "None". ?item p:P2302 / pq:P5314 wd:Q54828450 . ?item wikibase:propertyType wikibase:ExternalId . FILTER NOT EXISTS { ?item p:P9073 ?v9073 } OPTIONAL { ?item wdt:P1629 ?ms . ?ms wdt:P31 ?msinstance } # SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en" } }
List of this constraint violations: Database reports/Complex constraint violations/P9073#Properties lacking this
![](http://178.128.105.246/cars-http-upload.wikimedia.org/wikipedia/commons/thumb/a/a6/Pictogram_voting_comment.svg/40px-Pictogram_voting_comment.svg.png)
TODO: check how to fix values that amalgamate concepts (Help)
Violations query:
SELECT DISTINCT ?item ?value ?instance # ?itemLabel ?valueLabel ?instanceLabel WHERE { hint:Query hint:optimizer "None". ?item wdt:P9073 ?value . ?value (wdt:P31/(wdt:P279*)) wd:Q33506 . ?value wdt:P31 ?instance . ?instance (wdt:P31*/(wdt:P279*)) wd:Q33506 . # SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en" } }
List of this constraint violations: Database reports/Complex constraint violations/P9073#Value shouldn't be a museum
![](http://178.128.105.246/cars-http-upload.wikimedia.org/wikipedia/commons/thumb/a/a6/Pictogram_voting_comment.svg/40px-Pictogram_voting_comment.svg.png)
TODO: check how to fix values that amalgamate concepts (Help)
Violations query:
select distinct ?item ?value ?instance # ?itemLabel ?valueLabel ?instanceLabel where { hint:Query hint:optimizer "None". ?item wdt:P9073 ?value. ?value wdt:P31/wdt:P279* wd:Q7075; wdt:P31 ?instance. FILTER NOT EXISTS { ?instance wdt:P279* wd:Q212805 } ?instance wdt:P279* wd:Q7075. # SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en" } }
List of this constraint violations: Database reports/Complex constraint violations/P9073#Value shouldn't be a (non-online) library
![](http://178.128.105.246/cars-http-upload.wikimedia.org/wikipedia/commons/thumb/a/a6/Pictogram_voting_comment.svg/40px-Pictogram_voting_comment.svg.png)
TODO: check how to fix values that amalgamate concepts (Help)
Violations query:
SELECT ?item ?value ?org WHERE { ?item wdt:P9073 ?value . ?value wdt:P31 ?org . FILTER EXISTS { ?org wdt:P279* wd:Q43229 } }
List of this constraint violations: Database reports/Complex constraint violations/P9073#Value shouldn't be an organization
P244 as sample
[edit]- The property isn't really suitable as a sample as currently there is no P9073 statement at Property:P244#P9073.
- Also, I did remove the multiple statements as they would violate the single value constraint.
- There is a short discussion at Property_talk:P2333 about what do to when there is no primary database. For ISBN and ISSN currently "no value" is being used. @UWashPrincipalCataloger: --- Jura 09:14, 27 January 2021 (UTC)
Which value to use
[edit]- Any idea what value to use with ESRB game ID (P8303), Australian Classification ID (P8326), BBFC reference (P8794), FVLB work ID (P8680) and Common Sense Media ID (P7091)? @Jura1:--Trade (talk) 10:53, 29 January 2021 (UTC)
- Wikidata's general explanation is at Help:Sources#Databases. Four of the properties are already used in references. You could check these and see how they are used/create an item for the database/website they refer to. The last one isn't used in references, so P9073 might not be useful there.
- Looking at the subject items of the four, British Board of Film Classification (Q861670) and Entertainment Software Rating Board (Q191458) are currently just organizations per the items' P31 statements, Australian Classification (Q26708073) a classification system, Film & Video Labelling Body (Q98280432) an organization and a database. Items that are about the organizations aren't suitable as P9073 values. I think it would be good to have some consistency for these properties (and possibly other similar ones). Should there also be separate items about the classification itself and the database the property links to? @Máté: knows them better than I do. --- Jura 08:21, 30 January 2021 (UTC)
- It'd be probably best to create new items for their online databases, yes. – Máté (talk) 08:31, 30 January 2021 (UTC)
Could either of you make a QS that replaces all P248 > Q157754 with P248 > Q105272106? P248 > Q191458 with P248 > Q105295303. @Máté, Jura1:--Trade (talk) 15:14, 3 February 2021 (UTC)
- Not sure if QS is ideal for this, try Wikidata:Bot requests. --- Jura 09:16, 4 February 2021 (UTC)
What are the applicable value of P5933? X (Q918) or Tweet (Q56119332)? @Jura1: --Trade (talk) 12:21, 8 February 2021 (UTC)
- Not sure. What do you think? X post ID (P5933) is used frequently in references. --- Jura 12:33, 8 February 2021 (UTC)
- I'll go with Tweet (Q56119332). X (Q918) would imply that the tweet was made by the Twitter staff. --Trade (talk) 12:46, 8 February 2021 (UTC)
- Maybe there should be an intermediate level (the publication venue isn't the company). Also, I noticed you started adding items like "facebook username" as values. Do we have sample references where this is actually used in P248? Is there anything in Help:Sources to support it? --- Jura 12:40, 9 February 2021 (UTC)
- Wouldn't using "facebook" as a value imply that the statement was published by or endorsed by the company itself? Shouldn't we differentiate between referencing user generated content and referencing the site itself? --Trade (talk) 09:18, 17 February 2021 (UTC)
- There is no need for P9073 to be filled if the property isn't used (or to be used) widely in references with the same stated in (P248) value. --- Jura 07:20, 2 March 2021 (UTC)
- @Jura1:--Trade (talk) 12:49, 17 February 2021 (UTC)
- Wouldn't using "facebook" as a value imply that the statement was published by or endorsed by the company itself? Shouldn't we differentiate between referencing user generated content and referencing the site itself? --Trade (talk) 09:18, 17 February 2021 (UTC)
- Maybe there should be an intermediate level (the publication venue isn't the company). Also, I noticed you started adding items like "facebook username" as values. Do we have sample references where this is actually used in P248? Is there anything in Help:Sources to support it? --- Jura 12:40, 9 February 2021 (UTC)
What about Amazon Standard Identification Number (P5749)? @Jura1: --Trade (talk) 17:54, 28 February 2021 (UTC)
- Same as ISBN? --- Jura 07:20, 2 March 2021 (UTC)
Confusion/Inconsistency around this property
[edit]I notice that there is a query to say the value of this should not be an organisation, yet that has been added to the constraint as a valid value. I presume this is wrong.
Additionally, I'm a little confused about the example for Library of Congress authority ID (P244), I presume "some/unknown value" should be used when there are multiple possible primary sources associated with the property? This is not currently reflected on P244 itself and I'm also a little unclear on why we should not list all the possible primary sources as a way of showing what they are since it's not so much a case of "unknown value", but "one of these values". --SilentSpike (talk) 13:50, 5 October 2021 (UTC)
- Interested to hear from those involved in creation in clarifying these points @Jura1, ArthurPSmith: --SilentSpike (talk) 13:52, 5 October 2021 (UTC)
- Allowing multiple values if there could be several sounds like a good solution to me; however I don't know if there's some automation where this is currently used that might break with multiple values? Maybe it could work with one preferred value? ArthurPSmith (talk) 17:50, 5 October 2021 (UTC)
- Hello @SilentSpike, ArthurPSmith, Jura1:
I agree to removing the edit from UWashPrincipalCataloger. If the item cannot receive something like online database (Q7094076), it cannot be set as a value to P9073 and another Item must be created. We must not change what is logical. I thought this property was created to prevent this. We must remove organization (Q43229), because an organization "is not", but "has" a db of identifiers.
- For the example of P244, everything is connected, there is only one valid formatter URL (P1630). In Library of Congress authority ID (P244), even if P1630 receives multiple values, only one value receives a preferred rank. From this URL, all values of P9073 are covered, but only one value of P9073 is linked to P1630. This is why single-best-value constraint (Q52060874) is used in P9073. I replaced with the first value (with the preferred rank, which actually seems more logical than "unknown value"). Regards. —Eihel (talk) 23:54, 5 October 2021 (UTC)
- @ArthurPSmith, Eihel: Thanks for replies, glad to know we're on the same page. I've removed that constraint edit because I agree with the original intention of this property which is to map the use of ID properties in references to P248 values. As an open ended thought experiment to any future reader: is there a scenario where this property can ever take "unknown value"? --SilentSpike (talk) 22:51, 8 October 2021 (UTC)
- Values are currently checked through complex constraints. I don't see how multiple values could work or be useful. Supposedly only one would be in formatters as well. Maybe added "novalue" as prefer once more than one occurs? There was some discussion about it at Property_talk:P2333. --- Jura 10:52, 10 October 2021 (UTC)
Validation issue
[edit]Properties that include this property are now getting a constraint validation error when the property class of non-item property value (P10726) is used instead of Wikidata item of this property (P1629). I changed the constraint but it was reverted. What's the solution? Here's an example: electrocd artist ID (P11676). AdamSeattle (talk) 19:25, 18 March 2023 (UTC)
- All Properties
- Properties with wikibase-item-datatype
- Properties used on 1000+ items
- Properties with scope constraints
- Properties with entity type constraints
- Properties with qualifiers constraints
- Properties with single best value constraints
- Properties with constraints on type
- Properties with constraints on items using them
- Properties with complex constraints