Property talk:P9546

From Wikidata
Jump to navigation Jump to search

Documentation

Indiana State Historical Marker Program ID
identifier for an historical marker of the Indiana State Historical Marker Program
RepresentsIndiana State Historical Marker Program (Q106571962)
Applicable "stated in" valueIndiana Historical Markers (Q111442916)
Data typeExternal identifier
Domaincommemorative plaque (Q721747)
Allowed values[a-z0-9\-\/]+
ExampleBailly Homestead (Q111442474)find-historical-markers-by-county/indiana-historical-markers-by-county/bailly-homestead
Fort Ouiatenon (Q111442456)fort-ouiatenon
Maj Gen Ambrose E Burnside 1824-1881 (Q111442451)maj-gen-ambrose-e-burnside-1824-1881
Sourcehttp://www.in.gov/history/state-historical-markers/find-a-marker/
https://www.in.gov/history/state-historical-markers/
Formatter URLhttps://www.in.gov/history/state-historical-markers/find-a-marker/$1/
Related to country United States of America (Q30) (See 769 others) (Indiana (Q1415))
See alsoFlorida Historical Marker List ID (P6567), Historical Marker Database ID (P7883), NC Highway Historical Marker Program ID (P9492), Nevada SHPO marker ID (P9515)
Lists
Proposal discussionProposal discussion
Current uses
Total9
Main statement3 out of 702 (0% complete)33.3% of uses
Qualifier666.7% of uses
Search for values
[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/P9546#Single value, SPARQL
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/P9546#Unique value, SPARQL (every item), SPARQL (by value)
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/P9546#Entity types
Format “[a-z0-9/-]+: 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/P9546#Format, SPARQL
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/P9546#Scope, SPARQL
Type “commemorative plaque (Q721747): item must contain property “instance of (P31), subclass of (P279)” with classes “commemorative plaque (Q721747)” or their subclasses (defined using subclass of (P279)). (Help)
List of violations of this constraint: Database reports/Constraint violations/P9546#Type Q721747, hourly updated report, SPARQL
Item “instance of (P31): Items with this property should also have “instance of (P31)”. (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/P9546#Item P31, 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/P9546#Item P625, SPARQL
Item “commemorates (P547): Items with this property should also have “commemorates (P547)”. (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/P9546#Item P547, search, SPARQL
Item “image (P18): Items with this property should also have “image (P18)”. (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/P9546#Item P18, SPARQL

Move from String ID to numeric ID

[edit]

The current ID format relies on a component of the URL, but the identifier for the marker is a numeric format. From the Example example ID "fort-ouiatenon" the ID for the marker from the Indiana Government and displayed on the website is "79.1998.2". While an id for linking to the record on the website is needed the ID used to resolve with external data is the numeric format and should be captured as well. Should this numeric ID be captured in a new property? Wolfgang8741 (talk) 20:21, 27 February 2022 (UTC)[reply]

Proposal created for separate numeric ID. Wolfgang8741 (talk) 17:15, 31 March 2022 (UTC)[reply]