Property talk:P9794

Documentation

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

UCLA Space Inventory LocID
identifier for a University of California, Los Angeles building

Associated item	University of California, Los Angeles (Q174710)
Applicable "stated in" value	UCLA Space Inventory (Q107529904)
Data type	External identifier
Domain	university building (Q19844914) or geographic location (Q2221906)
Allowed values	[1-9]\d*
Example	Royce Hall (Q2171194) → 204 Gonda (Goldschmied) Neuroscience and Genetics Research Center (Q105534933) → 349 UCLA Morton Medical Building (Q105732732) → 251 UCLA La Kretz Garden Pavilion (Q105695290) → 94524 Powell Library (Q4405663) → 240
Source	http://spaceinventory.ucla.edu/
Formatter URL	http://spaceinventory.ucla.edu/#/LocID/$1
Related to country	United States of America (Q30) (See 762 others) (Los Angeles (Q65))
See also	Pacific Coast Architecture Database building ID (P6486)
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/P9794 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 137 Main statement 132 96.4% of uses Qualifier 5 3.6% 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/P9794#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/P9794#Unique value, SPARQL (every item), SPARQL (by value)

Type “university building (Q19844914), geographic location (Q2221906)”: item must contain property “instance of (P31)” with classes “university building (Q19844914), geographic location (Q2221906)” 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/P9794#Type Q19844914, Q2221906, SPARQL

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/P9794#Format, 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/P9794#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/P9794#Scope, SPARQL

Item “located in the administrative territorial entity (P131)”: Items with this property should also have “located in the administrative territorial entity (P131)”. (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/P9794#Item P131, search, 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/P9794#Item P276, search, SPARQL

Identifier linking

• Thank you for creating this property. I have edited format as a regular expression (P1793) and format constraint (Q21502404) to \d+ in order to include "0" (zero). Does it take time for identifiers to link to an external database? I notice that the identifiers in Wikidata property example (P1855) are not linking to the UCLA Space Inventory as they do in Pacific Coast Architecture Database building ID (P6486).--Uzundzhovets (talk) 22:03, 13 August 2021 (UTC)
  • UPDATE: By removing uses of this identifier in qualifiers and statements and then undoing the removal, they now link.--Uzundzhovets (talk) 19:12, 14 August 2021 (UTC)
    • It takes a day or two for the identifiers to become hotlinked after the property is created. There's also no need to remove them and add them back in: you should use Purge instead and save yourself some effort. In your Preferences, under Gadgets, check the PurgeTab box. Then for any item, under the More tab, click Purge and the record will flash and the identifiers will be hotlinked. That still takes a day or so after a property is created. I also don't think \d+ is correct. That matches any value from 0 to infinite. No identifier in this dataset is just the value 0. The correct (or more correct) regex is [1-9]\d* That matches an initial digit of 1 to 9 and then will match any digits from 0-9 after the first digit. UWashPrincipalCataloger (talk) 22:11, 17 August 2021 (UTC)
      • Thank you the clarification about the hotlinking and the regex. I tested the regexes in regex101 and realize now that [1-9]\d* is best for this property's identifiers; I'll revert my edits. It looks like [1-9]\d* should be used for Pacific Coast Architecture Database building ID (P6486) and Pacific Coast Architecture Database person ID (P5745) as well because I don't see any identifiers in those databases that are just 0 (zero).--Uzundzhovets (talk) 19:31, 18 August 2021 (UTC)