Property talk:P8960

Latest comment: 17 days ago by Thierry Caro in topic IDs have changed

Documentation

Kunsthistorisches Museum Wien ID
identifier for an artwork on the website of the Kunsthistorisches Museum, in Vienna, Austria
[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/P8960#Single value, SPARQL
Distinct values: this property likely contains a value that is different from all other items. (Help)
List of violations of this constraint: Database reports/Constraint violations/P8960#Unique value, hourly updated report, SPARQL (every item), SPARQL (by value)
Type “work of art (Q838948): item must contain property “instance of (P31)” with classes “work of art (Q838948)” 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/P8960#Type Q838948, SPARQL
Item “location (P276): Items with this property should also have “location (P276)”. (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/P8960#Item P276, search, SPARQL
Item “creator (P170): Items with this property should also have “creator (P170)”. (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/P8960#Item P170, search, SPARQL
Item “inception (P571): Items with this property should also have “inception (P571)”. (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/P8960#Item P571, SPARQL
Item “inventory number (P217): Items with this property should also have “inventory number (P217)”. (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/P8960#Item P217, search, 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/P8960#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/P8960#Scope, 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/P8960#Item P195, search, SPARQL
Format “[0-9a-f]{10}: 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/P8960#Format, SPARQL
Item “made from material (P186): Items with this property should also have “made from material (P186)”. (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/P8960#Item P186, search, SPARQL
Item “genre (P136): Items with this property should also have “genre (P136)”. (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/P8960#Item P136, search, SPARQL
Item “depicts (P180): Items with this property should also have “depicts (P180)”. (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/P8960#Item P180, search, SPARQL
Item “height (P2048): Items with this property should also have “height (P2048)”. (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/P8960#Item P2048, SPARQL
Item “width (P2049): Items with this property should also have “width (P2049)”. (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/P8960#Item P2049, SPARQL
Item “copyright status (P6216): Items with this property should also have “copyright status (P6216)”. (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/P8960#Item P6216, search, SPARQL
Label required in languages: de: Entities using this property should have labels in one of the following languages: de (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/P8960#Label in 'de' language, search, SPARQL

IDs have changed

edit

Hi Thierry Caro, I noticed that the Kunsthistorisches Museum Wien website is now using numeric identifiers instead of the 10 character hexadecimal IDs but they still redirect you to the right page, see e.g. https://www.khm.at/de/object/32bb90e897/, https://www.khm.at/objektdb/detail/72/ and https://www.khm.at/de/object/72/. I wonder whether we should make the change here too? Does it make sense to keep the hexadecimals when you can't even find them on the webpages? Samoasambia 14:21, 5 December 2024 (UTC)Reply

@Samoasambia: We can change them, I guess. Ideally, it would all happen in one go, so that there will be no disruption in the property use. If you can do that, feel free. I can't. Thierry Caro (talk) 18:51, 5 December 2024 (UTC)Reply
Return to "P8960" page.