Property talk:P3424

From Wikidata
Jump to navigation Jump to search

Documentation

Polish cultural heritage register number
reference in a Polish cultural heritage register
Representsobject on the Polish cultural heritage register (Q21438156), immovable monument (Q29940414)
Associated itemNarodowy Instytut Dziedzictwa (Q1963390), Narodowy Instytut Dziedzictwa (Q1963390)
Data typeString
Template parametereg. "zabytek" in pl:Szablon:Budynek infobox
Domaincultural heritage monuments in Poland (note: this should be moved to the property statements)
Allowed values[A-Za-zŁł0-9/.-]{1,25}.{1,25}
ExampleChurch of St. Barbara in Bielsko-Biała (Q11746560) → R/488/56
no label (Q122177246) → 10
no label (Q122234491) → 1
Source When possible, data should only be stored as statements
Robot and gadget jobsno
Tracking: usageCategory:Pages using Wikidata property P3424 (Q29034666)
Related to country Poland (Q36) (See 67 others)
See alsopoint in time (P585)
Lists
Proposal discussionProposal discussion
Current uses
Total92,142
Main statement92,134>99.9% of uses
Qualifier6<0.1% of uses
Reference2<0.1% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Format “[A-Za-zŁł0-9/.-]{1,25}: 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/P3424#Format, SPARQL
Item “country (P17): Poland (Q36): Items with this property should also have “country (P17): Poland (Q36)”. (Help)
List of violations of this constraint: Database reports/Constraint violations/P3424#Item P17, hourly updated report, search, SPARQL
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/P3424#Item P131, search, SPARQL
Item “coordinate location (P625): Items with this property should also have “coordinate location (P625)”. (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/P3424#Item P625, SPARQL
Format “.{1,25}: value must be formatted using this pattern (PCRE syntax). (Help)
List of violations of this constraint: Database reports/Constraint violations/P3424#Format, hourly updated report, 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/P3424#Entity types
Label required in languages: pl: Entities using this property should have labels in one of the following languages: pl (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/P3424#Label in 'pl' language, search, SPARQL
This property is being used by:

Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Format/datatype[edit]

As practically no item respected the format constraint, I tried to fix it, but I couldn't determine much of a pattern and added string length only. A better format definition might help.

Further, the unique value constraint has some 8600 violations for 65000 uses (approx.). This suggests that the data is either in bad shape or this is not an external identifier as it's generally seen at Wikidata. In the later case, datatype string would be more appropriate. --- Jura 13:24, 4 January 2018 (UTC)[reply]

A short survey let me see there is not seem to have logical in the 8600 violations, also I see there is a lot of violation of simple use. I found a part of the register [1] in the monument database site, and the id seem to have many id that don't follow the format constraint. So my best theory will be that the id come form multiple registers who are now mixed up. Past this property as a datatype string will probably be a good solution. --Fralambert (talk) 16:00, 4 January 2018 (UTC)[reply]
 Support of migrating to string datatype. The non uniqueness of the property was already mentioned in the property proposal. --Pasleim (talk) 13:50, 8 January 2018 (UTC)[reply]

Datatype was changed to string. --- Jura 11:45, 6 July 2021 (UTC)[reply]

Description update[edit]

Following the previous discussion, maybe "reference in a Polish heritage register" describes it better. I updated the English description accordingly [2].
--- Jura 01:44, 9 January 2018 (UTC)[reply]