Documentation

[create Create a translatable help page (preferably in English) for this property to be included here]
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).
List of violations of this constraint: Database reports/Constraint violations/P7847#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/P7847#Unique value, SPARQL (every item), SPARQL (by value)
Format “^\d{10,13}$: 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/P7847#Format, SPARQL
Allowed entity types are Wikibase item (Q29934200), Wikibase MediaInfo (Q59712033): 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/P7847#Entity types
Label required in languages: nb: Entities using this property should have labels in one of the following languages: nb (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/P7847#Label in 'nb' language, search, SPARQL
Label required in languages: sv: Entities using this property should have labels in one of the following languages: sv (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/P7847#Label in 'sv' language, search, SPARQL
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/P7847#Scope, SPARQL

Structured data on commons and Digitaltmuseum: dont we need the mediaId in Wikidata/Wikicommons?

edit

@Ambrosiani, Jon Harald Søby (WMNO), Alicia_Fagerving_(WMSE), André_Costa_(WMSE): I feel we need another Property for pictures. If we look at the example

As structured data on commons handle pictures with metadata for one picture its important that one picture in Wikicommons reference the "original picture" at Digitalmuseum if we in the future should implement metadata roundtrips between Wikicommons and Digitalmuseum i.e. I guess we need the mediaID in Structured Data on Commons not just reference the containers dimu_code....

- Salgo60 (talk) 11:45, 23 February 2020 (UTC)Reply

Mostly (with messy data there are always exceptions) it's the DiMu object that is persistent, not the image IDs. New images will be added, the dimu image servers will be recompiled etc. But adding the media IDs is still better than nothing I suppose, and as you say it will probably help with future roundtripping efforts. Ambrosiani (talk) 17:00, 23 February 2020 (UTC)Reply
@Ambrosiani: As metadata will be connected to the picture and that we now support relative position in a picture we need a 1 <-> 1 connection between the original digital object and the object on Wikicommons/Wikibase. I did a test today see tweet with Welsh Welsh Portrait Collection (Q54859927) and they use for pictures Handle ID (P1184) = identifier e.g. 10107/4671365 same object but in Wikicommons File:Portrait_of_Charles_XII_(4671365).jpg json
@David_Haskiya_(WMSE): it would be nice if we could get GLAM Swedish people to use a more generic property like Handle ID (P1184) for digital objects. I guess this is maybe something Digisam (Q86324608) people should push and we should get DigitaltMuseum (Q11125708), Nationalmuseum (Q842858), Europeana (Q234110) and Alvin (Q59341385)... to support en:Handle_System instead of specific properties for every system.... How to move this forward? See also the test I did T243907#5914827 - Salgo60 (talk) 10:13, 25 February 2020 (UTC)Reply
I agree it would be valuable, but as is often the case it's more easily said than done. Digisam is doing what is within their very limited power, which is advocate for the use of Persistent Identifiers (PIDs). They have neither carrot (eg grant funds) nor stick (sanctions) and the same is true for the Swedish National Heritage Board. The reality is that Swedish museums will start to use persistent identifiers for media, and objects for that matter, when that comes as a built-in feature in the Collections Management System (or Digital Asset Management System) they have bought. Some system vendors already support PIDs. What the best way is to encourage more of them to do is I will admit I don't know, it's basically a demand and supply issue. Vendors will develop the feature if enough of their customers ask for it or they perceive supporting the feature will give them a competitive edge. --David Haskiya (WMSE) (talk) 14:27, 25 February 2020 (UTC)Reply

Added a section "Dataroundtrip of pictures and find a de facto standard for image Public Identifier" about this problem see blogpost - Salgo60 (talk) 06:55, 15 June 2020 (UTC)Reply

Return to "P7847" page.
  NODES
Done 1
eth 1
see 12
Story 2