Property talk:P1184

Latest comment: 1 year ago by Jarnsax in topic identifier shared with

Documentation

Handle ID
Handle System identifier, which is a superset of the DOI
DescriptionHandle System (Q3126718) identifier, which is a superset of the DOI (P356)
RepresentsHandle System (Q3126718)
Data typeExternal identifier
Template parameterTemplate:Hdl (Q11717292) (commons:Template:Handle with 20,000+ uses, w:en:Template:Hdl with 1200 uses, and other languages with <20 uses); and Template:Cite hdl (Q7624305). 640 raw links on de.wp and 330 raw links on fr.wp
Domaincreative work (note: this should be moved to the property statements)
Allowed values[0-9a-z]+(\.[0-9a-z]+)*\/.{2,}
ExampleEleanor Elizabeth Bourne Papers (Q15664389)10462/eadarc/7154
Dialogue avec l'histoire : les collections de la Bibliothèque de l'Université Laval (Q63615887)20.500.11794/34239
Navigating and Responding to Raciolinguistic Ideologies: Refugee and Immigrant Students' Literacy Practices Across Contexts (Q104248274)1773/45982
SourceHandle System (note: this information should be moved to a property statement; use property source website for the property (P1896))
Formatter URLhttps://hdl.handle.net/$1
See alsoDOI (P356)
Lists
Proposal discussionProposal discussion
Current uses
Total135,041
Main statement124,91192.5% of uses
Qualifier18<0.1% of uses
Reference10,1127.5% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Format “[0-9a-z]+(\.[0-9a-z]+)*\/.{2,}: 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/P1184#Format, 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/P1184#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/P1184#Scope, SPARQL

Purpose edit

Handles are used for digital objects, especially by photographs by GLAMs and research papers held in academic digital repositories. The example provided is a Wikisource transcribed digital object provided by a GLAM. I can also provide an example of a notable research paper with a handle if required, but that will take a bit more searching. John Vandenberg (talk) 18:02, 28 January 2014 (UTC)Reply

Single value constraint? edit

Hi!

Because of the work that I'm doing with my sock puppet account (Iván Hernández Cazorla) I have doubts about the single value constraint in Handle ID (P1184). Why "single value constraint"? A publication may have more than one Handle System ID because it may be in more than one repository that uses Handle Systems. For example, El concepto de Epigrafía. Consideraciones sobre la necesidad de su ampliación, cincuenta años después (Q52155710) has two handle IDs: one for accedaCRIS (Q52155934) and another for the Biblioteca Digital Universidad de Alcalá. Two different handles for the same publication. There are probably more cases besides this.

What do you think about it? Should the "single value constraint" be removed of this property? At least I think it would be the correct, but maybe you know something that I don't know.

Regards, Ivanhercaz   (Talk) 16:14, 25 April 2018 (UTC)Reply

Another case that I just added: Las revistas científicas canarias de Humanidades: del papel a la edición electrónica (Q52230778). Ivanhercaz   (Talk) 16:03, 27 April 2018 (UTC)Reply
We also have the single value constrain violations list for this property, where there is 269 violations. Regards, Ivanhercaz   (Talk) 12:26, 28 April 2018 (UTC)Reply
I agree that this constraint is likely to be violated often. The Handle ID is a unique identifier for a particular digital copy of a work, but our items are about works, not particular copies. -− Pintoch (talk) 12:40, 28 April 2018 (UTC)Reply
Hi Pintoch! Of course, for what you said the distinct-values constraint (Q21502410) has sense, because is one Handle ID for a copy. So, in theory, Wikidata shouldn't have two items with the same identifier. But many times the works are in different repositories, these copies sometimes have different Handle ID: the same works, but in different locations and with different identifiers. I don't know if there is a rule to add one Handle ID and not other, I think there isn't and it could be complicated. In my mind the most reasonably is to add all Handle ID availables. For that I think the "single value constraint" isn't suitable for this property. Regards, Ivanhercaz   (Talk) 13:19, 28 April 2018 (UTC)Reply
Yes, I have therefore deleted the constraint. − Pintoch (talk) 13:22, 28 April 2018 (UTC)Reply
Thank you, Pintoch! Regards, Ivanhercaz   (Talk) 13:26, 28 April 2018 (UTC)Reply

identifier shared with edit

I've added this as an allowed qualifier here, and on Google Books ID (P675). Though these "should" have unique values, there are unfortunately (many) cases where different publications have been bound together, in different combinations, by different libraries. A fairly odd example is the CIA World Factbook (look at https://catalog.hathitrust.org/Record/000532922).... the University of California decided to bind them differently. Even though cases where "identifier shared with" still violate the distinct-value constraint, this qualifier lets us mark cases where the value being used on more than one item is actually appropriate. Jarnsax (talk) 05:39, 19 September 2022 (UTC)Reply

Return to "P1184" page.