Property talk:P648

From Wikidata
Jump to navigation Jump to search


Open Library ID
identifier for a work ("W"), edition ("M") or author ("A") for book data of the Internet Archive
DescriptionIdentifier assigned by Open Library (Q1201876) for works, editions and authors.
RepresentsOpen Library (Q1201876)
Associated itemOpen Library (Q1201876)
Data typeExternal identifier
According to this template: Mainly published materials, book (Q571) and version, edition, or translation (Q3331189), but also authors
According to statements in the property:
human (Q5), creative work (Q17537576), work (Q386724), organization (Q43229) and pseudonym (Q61002)
When possible, data should only be stored as statements
Allowed valuesOL[1-9]\d{0,7}[AMW]
ExampleTwenty Years After (Q1639633)OL36858W (RDF)
Anton Chekhov (Q5685)OL3156833A (RDF)
Libraries in the Medieval and Renaissance Periods (Q45341759)OL6917238M (RDF)
According to this template: Open Library (Q1201876)
According to statements in the property:
When possible, data should only be stored as statements
Formatter URL$1
Robot and gadget jobs$1
Tracking: usageCategory:Pages using Wikidata property P648 (Q51440038)
Related to countryFlag of the United States.svg United States of America (Q30) (See 303 others)
Proposal discussionProperty proposal/Archive/8#P648
Current uses182,112
Search for values
[create] Create a translatable help page (preferably in English) for this property to be included here
Format “OL[1-9]\d{0,7}[AMW]”: value must be formatted using this pattern (PCRE syntax). (Help)
List of this constraint violations: Database reports/Constraint violations/P648#Format, hourly updated report, SPARQL, SPARQL (new)
Distinct values: this property likely contains a value that is different from all other items. (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P648#Unique value, SPARQL (every item), SPARQL (by value), SPARQL (new)
Single value: this property generally contains a single value. (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P648#Single value, SPARQL, SPARQL (new)
Type “human (Q5), creative work (Q17537576), work (Q386724), organization (Q43229), pseudonym (Q61002): element must contain property “instance of (P31)” with classes “human (Q5), creative work (Q17537576), work (Q386724), organization (Q43229), pseudonym (Q61002)” or their subclasses (defined using subclass of (P279)). (Help)
Exceptions are possible as rare values may exist. Known exceptions: Prime Minister of the United Kingdom (Q14211), JT LeRoy (Q1676714)
List of this constraint violations: Database reports/Constraint violations/P648#Type Q5, Q17537576, Q386724, Q43229, Q61002, SPARQL, SPARQL (new)

Danger, Will Robinson![edit]

Author Identifiers OL\dA are often non-unique. Several such OL records may exist for a single author, even with the exact same spelling of the name. In other cases, one OL record may reflect many authors with similar names. OL has been dragging its feet for years on implementing consistent authority controls. I've tried to get their attention on this problem to no avail. We'll need to be able to deal with this. Work Identifiers OL\dW are often non-unique, with the same or varying title, linked to various author records. Cleaning up the mess at could take weeks. Edition Identifiers OL\dM are even more of a mess. They conflate different editions under one record, and have multiple records for one edition. All this said, however, OL remains one of the most useful ways to locate a freely-readable copy of many sources. As such, OL identifiers are given for editions or works cited, per w:en:SAYWHEREYOUGOTIT. We'll need to accommodate the multiple OL identifiers attributed to one work, edition, or author. We'll also need to distinguish the multiple works, editions, or authors conflated by one OL identifier. It's nontrivial. It may be impossible to code. Ideas? LeadSongDog (talk) 17:30, 16 June 2016 (UTC)

  • @LeadSongDog: Thanks for the info! For specificity, can you give examples of such duplications for A, W, M? (I haven't yet seen a M ID, I'd like to see one).
Authors with many OL ID, OL ID mapping to several authors (first one is a mistake on WD)
IMHO WD only needs to worry about the multiplicity if OL goes ahead and removes duplicate IDs without keeping a redirect to the surviving (merged-to) ID: do you have evidence of this happening? Otherwise WD could help OL by finding such duplicates (as constraint violations) but WD can't clean up OL's database. If you yourself say OL IDs are useful, we should keep them. --Vladimir Alexiev (talk) 10:07, 7 June 2017 (UTC)
@Vladimir Alexiev: Well, an obvious case is OL2624944A. The appropriate quick intervention (which I did in this case) is to suffix " (undifferentiated)" to the author name. The harder job is to mine each of the linked works and its editions in order to find sourcing for more completely spelled names (often via an edition's ISBN or OCLCno), then edit the OL\d*W record to reflect that finding. In most cases there will already be an OL\d*A record to link in. Sometimes there are duplicates even at the better (more specific) spelling. [1] and [2] are the same person, while [3] is quite another. VIAF and ISNI can help to clarify these cases. The latter died before the former was born. LeadSongDog (talk) 17:06, 7 June 2017 (UTC)

Split this property[edit]

This property is currently used for the OpenLibrary identifiers for works, editions and people. But, sadly Open Library is using different URI patterns for each of these type ($1,$1...). It would be nice to split this property in 3 to avoid this problem and to be able to have better constraints. I would suggest to keep this property for the author identifiers (around 119117 usages) and create two new properties, one for works (around 956 usages) and one for editions (around 34324 usages). What do you think about it? Tpt (talk) 14:15, 13 June 2018 (UTC)

  • I think a feature was requested to address the uri question. It seems to be in the works somewhere. If the existing property is re-purposed as suggested, users might get incoherent results.
    --- Jura 14:19, 13 June 2018 (UTC)