Property talk:P9515

Documentation

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

Nevada SHPO marker ID
alphabetical identifier for an historical marker of the Nevada State Historic Preservation Office, in Nevada

Associated item	Nevada State Historic Preservation Office (Q58013302)
Data type	External identifier
Domain	commemorative plaque (Q721747)
Allowed values	[a-z]+(-[a-z]+)*
Example	Spooner Summit (Q111458238) → spooner-summit Tonopah (Q111458239) → tonopah The Camel Corps (Q111458240) → the-camel-corps
Source	https://shpo.nv.gov//nevadas-historical-markers/historical-markers
Formatter URL	https://shpo.nv.gov/nevadas-historical-markers/historical-markers/$1
Related to country	United States of America (Q30) (See 762 others) (Nevada (Q1227))
See also	Historical Marker Database ID (P7883), Indiana State Historical Marker Program ID (P9546), Florida Historical Marker List ID (P6567), NC Highway Historical Marker Program ID (P9492)
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) Database reports/Constraint violations/P9515 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 9 Main statement 3 out of 266 (1% complete) 33.3% of uses Qualifier 6 66.7% of uses
Search for values

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

Format “[a-z]+(-[a-z]+)*”: 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/P9515#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/P9515#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/P9515#Unique value, hourly updated report, 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/P9515#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/P9515#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/P9515#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/P9515#Item P31, search, SPARQL

Capturing Numeric ID for Markers from P9515

Currently this property uses a string instead of a numeric ID. Example the string ID "tonopah" relates to No. "147" as listed on the page https://shpo.nv.gov/nevadas-historical-markers/historical-markers/tonopah from a reference standpoint the marker number may be more stable in records matching than the string. Should a new property ID be created for the numeric form or should this property move to the marker number? Shouldn't the marker number should be captured as a qualifier to maintain linking and entity resolution with external data if string ID and link break? Wolfgang8741 (talk) 19:36, 27 February 2022 (UTC)