Property talk:P8521

Documentation

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

Sculptures and cities database ID for sculptures
identifier for sculptures in the Sculptures and cities database

Applicable "stated in" value	Sochy a města (Q97941212)
Data type	External identifier
Domain	plastic artwork (Q350268), memorial (Q5003624) or monument (Q4989906)
Allowed values	[1-9]\d*
Example	Prolézačka se skluzavkou Ryba (Q64815333) → 18533 Váňův kámen (Q64177698) → 19744
Formatter URL	https://sochyamesta.cz/zaznam/$1
Related to country	Czech Republic (Q213) (See 155 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/P8521 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 3,131 Main statement 994 out of 5,287 (19% complete) 31.7% of uses Qualifier 2 <0.1% of uses Reference 2,135 68.2% of uses
Search for values

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

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

Format “[1-9]\d*”: 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/P8521#Format, SPARQL

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/P8521#Single value, SPARQL

Type “plastic artwork (Q350268), memorial (Q5003624), monument (Q4989906)”: item must contain property “instance of (P31), subclass of (P279)” with classes “plastic artwork (Q350268), memorial (Q5003624), monument (Q4989906)” or their subclasses (defined using subclass of (P279)). (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/P8521#Type Q350268, Q5003624, Q4989906, 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/P8521#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/P8521#Scope, SPARQL

Used as main value

@Vojtěch Dostál:, I see you did something like that. Why not symply add the identifier without any reference? The reference is useful for statement but in the case of external identifier I do not see the benfit because the link of the identifier points directly to the web page. As far as I know, this is how it is done for all external identifiers. But maybe I miss something. Pamputt (talk) 18:40, 17 August 2020 (UTC)

@Pamputt: I know it's not essential in case of identifier statements, but it can still be useful. I often acquire identifiers using different methods and from different sources. In this case, it's pretty straightforward, but sometimes I obtain identifiers from a completely different database. This can happen because databases link to each other. Vojtěch Dostál (talk) 18:46, 17 August 2020 (UTC)

OK no problem. In that case, just remove the use of Sculptures and cities database ID for sculptures (P8521) in the reference because it is clearly redundant (and it violates the contraint about the property scope (before you add "as reference"). Pamputt (talk) 18:48, 17 August 2020 (UTC)

@Pamputt: Why is it redundant? I just tried to explain that it servers a useful purpose.Vojtěch Dostál (talk) 16:12, 23 August 2020 (UTC)

@Vojtěch Dostál: it is redundant because you want to add a reference to the statement Sculptures and cities database ID for sculptures (P8521) = XXX using as a reference Sculptures and cities database ID for sculptures (P8521) = XXX. Using only stated in (P248), reference URL (P854) and subject named as (P1810) appears to be sufficient. Pamputt (talk) 16:22, 23 August 2020 (UTC)

In my opinion, using the identifier property is better than reference URL (P854) and supplements it. This is because the URL can change (become defunct) but the identifier will still clearly identify the database entry.Vojtěch Dostál (talk) 16:26, 23 August 2020 (UTC)

@Vojtěch Dostál: Indeed, but using the database identifier as a reference for the database identifier is a bit circular... Pamputt (talk) 21:50, 23 August 2020 (UTC)