Property talk:P2186
Documentation
unique ID for the monuments included in Wiki Loves Monuments national lists
| Represents | Wiki Loves Monuments (Q1353202) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Data type | External identifier | ||||||||||||
| Template parameter | external reference template (to be created) and/or Wikipedia infoboxes (depending on the nature of the WLM item) | ||||||||||||
| Domain | monuments included in Wiki Loves Monument's national lists (note: this should be moved to the property statements) | ||||||||||||
| Allowed values | According to this template:
depends on the WLM identifiers
According to statements in the property:
When possible, data should only be stored as statements.{3,16}[a-zA-Z0-9ÁÓÍ/-]{3,16} | ||||||||||||
| Example | Rocca di Meldola (Q3939476) → 040019806 San Lorenzo de Tarapacá, La Casona (Q42897888) → CL-289 | ||||||||||||
| Source | Wikimedia chapters lists for WLM (note: this information should be moved to a property statement; use property source website for the property (P1896)) | ||||||||||||
| Robot and gadget jobs | to be determined, probably Mix 'n' Match will be used | ||||||||||||
| Lists |
| ||||||||||||
| Proposal discussion | Proposal discussion | ||||||||||||
| Current uses |
| ||||||||||||
| Search for values |
List of violations of this constraint: Database reports/Constraint violations/P2186#Item P17
List of violations of this constraint: Database reports/Constraint violations/P2186#Item P131, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P2186#single best value, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P2186#Unique value, SPARQL (every item), SPARQL (by value)
List of violations of this constraint: Database reports/Constraint violations/P2186#Item P1435, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P2186#Item P18, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P2186#Item P625, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P2186#Item P373, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P2186#Format, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P2186#Entity types
|
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
Land restriction[edit]
I would suggest we remove the country (P17) = Italy (Q38) restriction so that this property can be used for any entry in the monuments database (or at least any which doesn't have another official id).
If the restriction is not lifted the label and descriptions should be updated to make clear it is only for use with the Italian monuments. /André Costa (WMSE) (talk) 13:02, 1 June 2016 (UTC)
- You could just add countries where you think it's needed. I don't think there is much use in duplicating values of more specific properties into this.
--- Jura 13:11, 2 June 2016 (UTC)- @André Costa (WMSE): I agree, it's already used in a bunch of other countries. I changed it to P17 only, without specific country. Yarl 💭 12:20, 9 June 2017 (UTC)
- I don't think this should be used for random countries. Please provide an explanation for countries you think should be added. This was create for Italy as no official identifier is/was available.
--- Jura 10:50, 21 August 2017 (UTC)- @Jura1: There are multiple countries which participated in WLM over the years who ended up making their own identifiers because an official one wasn't available. I agree that this shouldn't be used for any dataset where the identifier was official (for those we should propose a new property). Note that adding more countries to the mix creates an uniqueness problem. See the section on Prefixes below. /André Costa (WMSE) (talk) 12:10, 21 August 2017 (UTC)
- I increased the list of allowed countries based on what has been uploaded and listed at Wikidata:WikiProject_WLM/Status. Netherlands (Q55) is added to allow for various sub-national datasets (such as Aruba (Q21203)). /André Costa (WMSE) (talk) 14:54, 10 November 2017 (UTC)
- @Jura1: There are multiple countries which participated in WLM over the years who ended up making their own identifiers because an official one wasn't available. I agree that this shouldn't be used for any dataset where the identifier was official (for those we should propose a new property). Note that adding more countries to the mix creates an uniqueness problem. See the section on Prefixes below. /André Costa (WMSE) (talk) 12:10, 21 August 2017 (UTC)
- I don't think this should be used for random countries. Please provide an explanation for countries you think should be added. This was create for Italy as no official identifier is/was available.
- @André Costa (WMSE): I agree, it's already used in a bunch of other countries. I changed it to P17 only, without specific country. Yarl 💭 12:20, 9 June 2017 (UTC)
Prefixes?[edit]
@Alicia Fagerving (WMSE), Jura1, Yarl, Sannita, Nvitucci:
With the wikidata migration of WLM data I'm discovering more countries with "inofficial" ids. For WLM it has not been any issue that two countries use the same id number but that assumption breaks down for this property.
One solution is to say that these id's are only unique when combined with a country. The other is to require them to have a prefix (e.g. IT-#, CL-# or NL-GEM-#). The downside of the latter solution is that the prefix would have to be stripped when comparing with old identifiers (used in e.g. Commons templates). The benefit though is that we could add a constraint for the allowed prefixes giving us a better control of where the identifier is (ab)used. /André Costa (WMSE) (talk) 10:39, 21 August 2017 (UTC)
- A third solution would be to require a qualifier (maybe of (P642)) with the dataset as the target item. /André Costa (WMSE) (talk) 12:10, 21 August 2017 (UTC)
- I imported both Irish and Polish dataset with prefixes, fyi.
- Anyway, I think it shouldn't be a huge deal in a long perspective. One of the the things we need to do in the near perspective is to migrate Commons' heritage templates to use data from Wikidata based on Wikidata item number as a param. This way we can lower the dependency on this property. Yarl Yarl 14:45, 21 August 2017 (UTC)
- I put together this query which shows for which countries this property is currently used and how often. /André Costa (WMSE) (talk) 15:20, 21 August 2017 (UTC)
- Then my recommendation is to import any new ones with prefixes and then do a batch convert of the old ones once WLM is over for this year so as to ensure there is no disruption.
- @Yarl:. Doesn't Poland have Polish cultural heritage register number (P3424) which should be used instead of this property? /André Costa (WMSE) (talk) 11:30, 25 August 2017 (UTC)
- Yes, we have Polish cultural heritage register number (P3424) for proper registry numbers. Wiki Loves Monuments ID (P2186) in Poland are created based on internal index from national heritage board, and for now it's pretty useful. We will decide what to do with WLM identifiers for Poland in the future. Yarl 💭 18:46, 25 August 2017 (UTC)
- I put together this query which shows for which countries this property is currently used and how often. /André Costa (WMSE) (talk) 15:20, 21 August 2017 (UTC)
Constraints involving deprecated properties[edit]
Hi, I removed the constraint that the address should be provided as well, since the property used in the constraint was deprecated. Braveheart (talk) 07:51, 22 January 2019 (UTC)
Verification[edit]
Why is there no formatter URL (P1630) or source website for the property (P1896) for this identifier? Is there really no way for Wikidata editors to verify values? Bovlb (talk) 17:31, 24 November 2021 (UTC)
Unsourced messy data[edit]
I noticed at Wikidata:WikiProject WLM/Status that more sources are using this property. This creates a huge pile of unsourced messy data. I do understand the need to be able to link to the custom (homebrew or made up) id's for Wiki Loves Monuments that are in the lists on Wikipedia and used in the monuments database. First of all, if we get official id's, we should just create a property for it (like Rijksmonument ID (P359)). If it's a custom homebrew identifier we have two options:
- Use this property with a prefix (so instead of 1234, xx-1234 where xx is for example a country code)
- Make a new property per set of monuments
I prefer the second option because it's much closer to real properties and the first option disrupts a lot of workflows. Case at hand is Ukraine with 91574 monuments according to the monuments database. Multichill (talk) 20:11, 7 March 2022 (UTC)