Property talk:P1997

Latest comment: 3 years ago by RolandUnger in topic Are some constraints too limited

Documentation

Facebook Places ID
identifier for a place in Facebook
Applicable "stated in" valueFacebook Places (Q98076236)
Data typeExternal identifier
Domain
According to this template: geographical feature (Q618123)
According to statements in the property:
administrative territorial entity (Q56061), neighborhood (Q123705), human settlement (Q486972) or building (Q41176)
When possible, data should only be stored as statements
Allowed values[1-9]\d{14,15}
ExampleSchlatkow (Q15923993)115498741794980
Santa Fe (Q38555)112889718724492
Sourcehttps://www.facebook.com/
Formatter URLhttps://www.facebook.com/$1
https://www.facebook.com/profile.php?id=$1
https://www.facebook.com/pages/-/$1
Tracking: usageCategory:Pages using Wikidata property P1997 (Q28511981)
See alsoInstagram location ID (P4173), Facebook username (P2013), Facebook page ID (P4003), Facebook Gaming game ID (P6913)
Lists
Proposal discussionProposal discussion
Current uses
Total5,221
Main statement5,21099.8% of uses
Qualifier4<0.1% of uses
Reference70.1% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Format “[1-9]\d{14,15}: 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/P1997#Format, SPARQL
Conflicts with “instance of (P31): Wikimedia disambiguation page (Q4167410): this property must not be used with the listed properties and values. (Help)
List of violations of this constraint: Database reports/Constraint violations/P1997#Conflicts with P31, hourly updated report, search, 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/P1997#Unique value, SPARQL (every item), SPARQL (by value)
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). Known exceptions: Copenhagen (Q1748)
List of violations of this constraint: Database reports/Constraint violations/P1997#Single value, SPARQL
Item “country (P17): Items with this property should also have “country (P17)”. (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/P1997#Item P17, search, SPARQL
Scope is as main value (Q54828448): the property must be used by specified way only (Help)
List of violations of this constraint: Database reports/Constraint violations/P1997#Scope, hourly updated report, 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/P1997#Entity types

Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Discussion edit

additional constraint edit

Hi! After adding more then 200 values I noticed that

  1. the value length was always 15 digits
  2. the first digit was never 0

Best regards Gangleri also aka I18n (talk) 02:47, 22 January 2016 (UTC)Reply

Ping @Pigsonthewing! Please help! Thanks in advance I18n (talk) 20:55, 22 January 2016 (UTC)Reply
@Ivan can you help please add the new claim? (The regex?) Thanks in advance! I18n (talk) 23:01, 4 February 2016 (UTC)Reply
  DoneIvan A. Krestinin (talk) 23:27, 5 February 2016 (UTC)Reply

Database reports/Constraint violations ERROR edit

Hi ! I made some changes yesterday and waited for the result. But now the report shows only:

"ERROR: Value type constraint is not applicable for string type properties."

@Ivan can you please fix the constraints:

a) As you can see from the history the lenght of the value might be 16 digits as well. I hope my change covers this.
b) The first digit may differ from "1" so I removed the experimental constraint.
c) It would be nice to detect if either capital (P36) is present or one can trace the country via the tree.
d) This property is for geographical items only. You may add a constraint report if possible,

Thanks for your help in advance! Gangleri also aka I18n (talk) 11:58, 14 February 2016 (UTC)Reply

Are some constraints too limited edit

I have just added this ID to an institution and I got a warning. Is this use a little bit rigid? It would help a lot to use this ID at his full potential.--Alexmar983 (talk) 13:34, 18 February 2020 (UTC)Reply

The range of usable types should be extended. Also sights, hotels, restaurants, institutions and so on can be valid types. It seems that commonalities are "geographical objects" (Q618123) or items have a geo coordinate. --RolandUnger (talk) 07:01, 7 August 2020 (UTC)Reply

Return to "P1997" page.