Type “work (Q386724)”: item must contain property “instance of (P31)” with classes “work (Q386724)” or their subclasses (defined using subclass of (P279)). (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/P5331#Type Q386724, SPARQL

Single value: this property generally contains a single value. (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: American Architectural Books: A List of Books, Portfolios and Pamphlets Published in America before 1895 on Architecture and Related Subjects (Q107256050), Laws and Rules in Indo-European (Q113710071), Urdu Punjabi Lughat (Q65398900)
List of violations of this constraint: Database reports/Constraint violations/P5331#Single value, SPARQL

Distinct values: this property likely contains a value that is different from all other items. (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/P5331#Unique value, SPARQL (every item), SPARQL (by value)

Format “[1-9]\d*”: value must be formatted using this pattern (PCRE syntax). (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/P5331#Format, SPARQL

Conflicts with “OCLC control number (P243)”: this property must not be used with the listed properties and values. (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Akusherstvo i ginekologii︠a︡ (Q27708908), Dicionário de Gentílicos e Topónimos (Q115175984)
List of violations of this constraint: Database reports/Constraint violations/P5331#Conflicts with P243, search, SPARQL

Allowed entity types are Wikibase item (Q29934200): 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/P5331#Entity types

Scope is as main value (Q54828448), as reference (Q54828450): the property must be used by specified way only (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/P5331#Scope, SPARQL

This property is being used by: uk:Шаблон:Журнал, uk:Шаблон:Твір, uk:Шаблон:Альманах Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

@Jheald:

Unfortunately, the "default url" for this property (http://classify.oclc.org/classify2/ClassifyDemo?owi=) , the one linked when clicking on the links created on items, does not work...

could it be changed to the (second url), the one that works, and can be found http://experiment.worldcat.org/entity/work/data/ - so that it would be possible to easily check the ID ?

example : on Le Code Noir : idées reçues sur un texte symbolique (Q21997202) - clicking on the ID leads to nowhere http://classify.oclc.org/classify2/ClassifyDemo?owi=1209330965 with an error message, while http://worldcat.org/entity/work/id/1209330965 opens without problem...

Thanks for your help on this... many items which mix work and edition need to be checked... the checking of IDs would be facilitated :) --Hsarrazin (talk) 06:30, 8 May 2019 (UTC)[reply]

@Hsarrazin: I have made the URL that you suggest the preferred one -- but note that the change will not propagate through to existing values until they are edited. The 'ClassifyDemo' URL appears to have been added by User:Netoholic, so I hope they will confirm if this is okay by them as well. Also pinging User:Tpt. Jheald (talk) 08:00, 8 May 2019 (UTC)[reply]

it does not work (for now)... so, for me, a working url is always better than a dead one ;) - Thank you Jheald --Hsarrazin (talk) 08:07, 8 May 2019 (UTC)[reply]

Looks like an outage of some sort. ClassifyDemo was operational just a day ago. I promoted the "experiment.worldcat.org" link to preferred, since the "worldcat.org" one just redirects to it anyway. -- Netoholic (talk) 08:14, 8 May 2019 (UTC)[reply]

if i understand correctly, oclc is creating work ids on an automatically way using key-matching based on title and author values, mainly if the bibliographic records don't know any link to an original work title, which should be used for matching processes at first. i have no idea about the current number of cases but i think there are many duplicate and non-necessary work-ids outside in oclc' worldcat. look at this example: Little Puppy Cleans His Room (Q92373730). I think it is totally correct that we have stored both work ids there, but it would be fine to add a qualifier object named as (P1932) to add the different titles from the worldcat.

• Little Puppy Cleans His Room (Q92373730)OCLC work ID (P5331)"5611687006"object named as (P1932)"Little puppy cleans his room"
• Little Puppy Cleans His Room (Q92373730)OCLC work ID (P5331)"3769463044"object named as (P1932)"Cyndy Szekeres' little puppy cleans his room"

Therefore i propose: OCLC work ID (P5331)property constraint (P2302)single-value constraint (Q19474404)separator (P4155)object named as (P1932)

@Discostu: --Mfchris84 (talk) 07:23, 29 April 2020 (UTC)[reply]

I noticed there was a constraint issue on Q4982058. However I am puzzled by the reason that an OCLC Work ID cannot be in the same space with OCLC record control number. Both IDs serve different purposes. Screenshot here. jshieh (talk) 11:13, 1 October 2020 (UTC)[reply]

• Hi jshieh, I understand that you reached out to Jeff with OCLC about this. So today just now both I and Jeff Mixter (OCLC developer) had a conference call about this. This particular constraint of not using both properties of OCLC control number (P243) and OCLC work ID (P5331) is valid actually. However your particular use case would instead be served by using one of the following: based on (P144), derivative work (P4969), modified version of (P5059). Both Jeff and I did acknowledge and agree that the other constraint issue you mentioned to him of the Type constraint on OCLC work ID (P5331) for instances of written work (Q47461344) needs to be changed to instances of work (Q386724) since a "work" in OCLC's terms does sort of mean "any object in a collection", like a stuffed toy, or even a moon rock. We both agreed that 99% of the cases will suffice as instances of work (Q386724) which is 99% accurate most of the time, instead of constraining to the highest conceptual level of entity (Q35120) which would be 100% the most accurate. However, in practicality, it would not make sense to constrain to "an object in a collection" even if we do have that Q ID already somewhere in Wikidata, since MANY things, and ANY thing can be put in a collection (an infinite list of entity (Q35120) things). So, I will ping some folks on the mailing list to get some attention to this topic talk and see if we cannot get this Type constraint replaced with at least work (Q386724) to help everyone. --Thadguidry (talk) 18:13, 7 October 2020 (UTC)[reply]
  • Many thanks, Thadguidry!! Resolving my curiosity of the rationale behind the constraints for properties that record control number (an Instance/manifestation issue) and work id (a Work which may or may not be conceptual) describing a publication, creative work, or a literary work entity. I came from an angle that as librarians when we query the data, by way of a single Work identifier, it will be relatively simple for us to output associated and available published/unpublished representation of a work. The presence of other properties as you mentioned, e.g. derivatives, based on, etc. are part of the core elements we use, if available, when describing a manifestation or an expression of a work. The definition of Work has been widely discussed as long as I could remember (maybe since 2012?) in various forums (metadata listservs, LD4P, BIBFRAME, OCLC and Share VDE groups). Now LC came up a term, Hub for <super work>, others opted Opus, some aggregative work, aggregation, etc. I suspect there will be policies and best practices once the library community comes to a majority consensus or not. Librarians may not all agree on modeling a work. For instance Hamlet has been expressed in different languages and formats. But I suspect majority of users will not dispute associating a single Work identifier for Hamlet with William Shakespeare if there is one in Wikidata. But then, should Wikidata be the environment for such data model? Not sure. Again, thank you so very much for continuing the conversation on additional data modeling concerning cardinality and property constraints!! jshieh (talk) 12:24, 8 October 2020 (UTC)[reply]

• •  Done - Mbch331 (talk) 18:31, 7 October 2020 (UTC)[reply]
    • Thank you. --Thadguidry (talk) 19:01, 7 October 2020 (UTC)[reply]

by reading the english descriptions i could not get it right on the 1st go: https://www.wikidata.org/w/index.php?title=Q124077560&diff=2043137089&oldid=2043136983 . something better is needed to distinguish this from OCLC control number (P243). RZuo (talk) 07:38, 2 January 2024 (UTC)[reply]

I changed the description to hopefully make it clearer. By the way OCLC Classify is being discontinued on 31 January 2024, and this property will then become defunct. AdamSeattle (talk) 19:46, 2 January 2024 (UTC)[reply]

Now when I click on a OCLC work id like this, the page says "Classify was discontinued on 31 January 2024". Emijrp (talk) 09:50, 10 March 2024 (UTC)[reply]

@Emijrp: I am assuming you are referring to Notes of an East Coast Naturalist (Q96755125). For that case you can still see this. But you are right in that this is a real issue for the future of the OCLC work ID (P5331) property. —Uzume (talk) 09:03, 30 March 2024 (UTC)[reply]

@Uzume Just curious, Is this property being updated, or will it be discontinued? It is impacting many literary work (Q7725634) items. Wallacegromit1 (talk) 19:57, 3 April 2024 (UTC)[reply]

@Wallacegromit1: Due to the issuer of the identifiers discontinuing their service, I presume this property is doomed and will likely be deleted at some point. If you know of some useful potential replacement, I am sure people would like to hear about it (I know I would). —Uzume (talk) 20:02, 3 April 2024 (UTC)[reply]

@Uzume Thanks for the swift reply. At the moment I am using the WorldCat Entities ID (P10832), if the 'Entity Type = Work', not 'Text'. But it is not really an alternative. Example: Indexing biographies and other stories of human lives (Q125306931)

It is odd that OCLC itself has not migrated their ID's into another format, it maybe because they are trying to combine their ID's in one place.

If you learn of anything further regarding this property, please let me know as well. Wallacegromit1 (talk) 20:18, 3 April 2024 (UTC)[reply]

@Wallacegromit1: Yes, it seems like WorldCat Entities ID (P10832) still needs development, e.g., E39PCGMxXWdjGVf6gXbygc8FXd Indexing biographies and other stories of human lives Work actually links to E39PCjDpGyFWtYwJJ3mkY74FGb Hazel K. Bell Person but you have to download the JSON to see that and it does not appear on their website HTML render. As for the reverse, the work is mentioned on the Person page but it does not link to the other entity and the JSON does not appear to link to the Work entity (so the page seems to be rendered via some sort of record "join"). And further, E39PCYBTPWMrW8JtkWqhJyBbgq 1992 Text and E39PCGqh6cRFpw334rHRyfXFmm 1998 Text both with the same title of the Work do not appear to link to it or vice versa (although they have descriptions mentioning Hazel K. Bell and the latter even mentions Bell as a "related person"). In summary, although it seems like it might be better designed than OCLC work ID (P5331) (by employing semistructured JSON like Wikibase/Wikidata), WorldCat Entities ID (P10832) seems much less mature than the former. —Uzume (talk) 21:20, 3 April 2024 (UTC)[reply]

@Uzume Thanks for the explanation, have removed the ID in the item. Wallacegromit1 (talk) 21:31, 3 April 2024 (UTC)[reply]

@Wallacegromit1: I reverted that as it is still a relevant work identifier. Maybe someday it will also be more useful for finding and linking to its creators and editions, etc. (in a fashion similar to how OCLC work ID (P5331) used to link to WorldCat catalog records for editions of the work, etc.) —Uzume (talk) 21:50, 3 April 2024 (UTC)[reply]