Property talk:P7711

Documentation

• Start a query
• Current uses
• Statistics by class
• String length
• List of qualifiers
• Count

Joconde author ID
identifier for a person in the Service des Musées de France Joconde authority file

Applicable "stated in" value	Joconde (Q809825)
Data type	External identifier
Allowed values	T513-[1-9]\d{1,5}|[0-9a-f]{8}(-[0-9a-f]{4}){3}-[0-9a-f]{12}
Example	Jean-Baptiste Camille Corot (Q148475) → T513-7005 (RDF) Louise Moillon (Q446984) → T513-21686 (RDF) Camille Claudel (Q120582) → T513-6441 (RDF) Claude-Léon Mascaux (Q5128670) → 171394dc-5472-4322-9017-b8ca091e18b0 (RDF)
Source	http://data.culture.fr/thesaurus/page/ark:/67717/T513
Formatter URL	http://data.culture.fr/thesaurus/page/ark:/67717/$1/ https://data.culture.fr/thesaurus/data/ark:/67717/$1
Related to country	France (Q142) (See 638 others)
See also	Joconde work ID (P347), Thésaurus de la désignation des objets mobiliers ID (P4979), Thésaurus de la désignation des œuvres architecturales et des espaces aménagés ID (P4980)
Lists	Items with the most statements of this property Count of items by number of statements (chart) Items with the most statements Items with the fewest statements Count of items by number of sitelinks (chart) Items with the most sitelinks Items with the most sitelinks, but no link to one Wikipedia (sample: Welsh Wikipedia, cywiki) Items with the fewest sitelinks Most linked wikis Items with the most identifier properties Items with no other external identifier Items with no other statements Most recently created items Items with novalue claims Items with unknown value claims Usage history (total) Usage history (main statement) Chart by item creation date Mix'n'match (Report) Database reports/Constraint violations/P7711 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 6,786 Main statement 6,782 out of 38,000 (18% complete) >99.9% of uses Qualifier 4 <0.1% of uses
Search for values

[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/P7711#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/P7711#Unique value, SPARQL (every item), SPARQL (by value)

Format “T513-[1-9]\d{0,4}|[0-9a-f]{8}(-[0-9a-f]{4}){3}-[0-9a-f]{12}”: 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/P7711#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/P7711#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/P7711#Scope, SPARQL

Format

@Christelle Molinié, VIGNERON, Nomen ad hoc: Looking at the entries listed by the SPARQL endpoint, it seems this so-called "identifier" and its current formatter URL were only used to generate URIs for the initial batch of entries in August 2018 (from then-existing values of the AUTR field in Joconde I guess). However, items created after that date (and supposedly future ones) use an UUID instead which does not fit with this scheme at all. Should we revise the proposed format to cope with them before more items are added? The same comment of course applies to other thesauri published on the site, though some are probably less dynamic. Is there a contact on GINCO that could provide some insight? --Nono314 (talk) 12:49, 16 January 2020 (UTC)

• Hi @Nono314:, thank you for raising this issue and looking for an explanation. I 've had a phone call this morning with one of the administrator of Joconde vocabularies. She asked the GINCO platform manager who confirmed that there are some ID made up of the system number of the former database and others, the latest, made up with opaque identifiers (GUID). I have just seen that @Vladimir Alexiev: has received a reply here Property talk:P7844 about the same subject on an other list (there are 10 Joconde properties potentially concerned). We will probably have to manage with two formats. Is it possible to allow two types of values ? --Christelle Molinié (talk) 13:16, 21 January 2020 (UTC)
• We can keep expanding the regexes of these thesauri but if new entries will be generated using GUIDs instead of "natural keys", the only feasible course is to merge all 10 culture.fr thesauri on WD into one (note: culture.fr have a total of 20 thesauri), since it makes little sense to have the same formatterUrl for several external-ids. The disadvantage is that we can't check for item type, and (as mentioned at Property talk:P7844) some matches will be non-unique (because the same item could me mapped to several culture.fr thesauri). @Nono314, Christelle Molinié, VIGNERON, Nomen ad hoc, Crowjane7: what do you think? --Vladimir Alexiev (talk)
• It's a pity that Ginco doesn't have a "URL policy" feature to generate sequential IDs ("natural keys"). Resorting to GUIDs is impolite to humans (we have our rights too! ;-). --Vladimir Alexiev (talk) 13:30, 21 January 2020 (UTC)

• Maybe you need this: Wikidata:Project_chat#UUID_search. --- Jura 13:24, 3 February 2020 (UTC)

Property deletion

Property was kept, please see Wikidata:Properties for deletion/Joconde — Martin (MSGJ · talk) 21:37, 15 February 2022 (UTC)