Property talk:P4249

Documentation

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

Vincoli in Rete ID
identifier of a building or site in the database of the MIBACT (Ministero per i Beni, le Attività Culturali e il Turismo) concerning regulatory constraints on cultural heritage in Italy

Applicable "stated in" value	Vincoli in Rete (Q107493990)
Data type	External identifier
Domain	cultural heritage items in Italy (note: this should be moved to the property statements)
Allowed values	[1-9]\d{0,7}
Example	Basilica di San Giovanni Battista (Q2887005) → 318021 Santi Pietro e Paolo Church (Q55326277) → 3055502
Source	http://vincoliinrete.beniculturali.it/
External links	Use in sister projects: [ar] • [de] • [en] • [es] • [fr] • [he] • [it] • [ja] • [ko] • [nl] • [pl] • [pt] • [ru] • [sv] • [vi] • [zh] • [commons] • [species] • [wd] • [en.wikt] • [fr.wikt].
Formatter URL	http://vincoliinrete.beniculturali.it/VincoliInRete/vir/bene/dettagliobene$1
Tracking: usage	Category:Pages using Wikidata property P4249 (Q56243014)
Related to country	Italy (Q38) (See 402 others)
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 Database reports/Constraint violations/P4249 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 538 Main statement 479 89% of uses Qualifier 2 0.4% of uses Reference 57 10.6% of uses
Search for values

[create Create a translatable help page (preferably in English) for this property to be included here]

Format “[1-9]\d{0,7}”: 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/P4249#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/P4249#Entity types

Scope is as main value (Q54828448), as reference (Q54828450): the property must be used by specified way only (Help)

List of violations of this constraint: Database reports/Constraint violations/P4249#Scope, hourly updated report, SPARQL

Single best value: this property generally contains a single value. If there are several, one would have preferred rank (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/P4249#single best value, SPARQL

Label required in languages: it: Entities using this property should have labels in one of the following languages: it (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/P4249#Label in 'it' language, search, SPARQL

Vincolo singolo

Ciao, scrivo in italiano perché presumo che solo chi capisce la lingua andrebbe in dettaglio a scorrere queste schede per assegnarle.

Mi sento di consigliare di non inserire "single-value constraint" per questa proprietà a breve; il numero di duplicati in archivio nel database ministeriale non mi pare basso. Non è da escludersi che siano ri-catalogazioni, o che si tratti di schede che in futuro saranno differenziate per indicare porzioni diverse di un determinato bene (una chiesa in un complesso ecclesiastico, il complesso delle mura in un borgo fortificato), quindi penso abbia senso comunque tenerne traccia e scoprorare nei prossimi anni se fosse il caso. O rimuoverne una delle due una volta eliminata e accorpata nel database. talvolta anche tre.

La mia soluzione al momento usare occorrenze multiple con un preferred rank sul più completo o attinente, vedasi Q3671488 o Q3950070. Commenti? Alexmar983 (talk) 16:59, 7 October 2022 (UTC)

Aggiunto single-best-value constraint (Q52060874). --Epìdosis 20:19, 7 October 2022 (UTC)