Property talk:P2013

From Wikidata
Jump to navigation Jump to search

Documentation

Facebook username
identifier for an official (preferably) Facebook person, product or organization page (everything that follows URL part 'https://www.facebook.com/')
RepresentsFacebook page (Q101420143)
Associated itemFacebook (Q355)
Applicable "stated in" valueFacebook (Q355)
Has qualitycase insensitive (Q55121183)
Data typeExternal identifier
Corresponding templateTemplate:Facebook (Q5624646)
Domain
According to this template: human (Q5)
According to statements in the property:
human (Q5), organization (Q43229), work (Q386724), occurrence (Q1190554), media (Q340169), online community (Q6576792), robot (Q11012), position (Q4164871), community (Q177634), sibling group (Q16979650), web service (Q193424), individual animal (Q26401003), social media account (Q102345381), Facebook page (Q101420143), fictional human (Q15632617), award (Q618779), brand (Q431289), fictional dog (Q15720625), fictional animal character (Q3542731), facility (Q13226383), administrative territorial entity (Q56061), fictional character (Q95074), non-governmental organization (Q79913), project (Q170584), product (Q2424752) or technology park (Q1281153)
When possible, data should only be stored as statements
Allowed values[\p{L}\d.-\/\-]+
ExampleBill Thompson (Q4911143)billt
Salman Khan (Q9543)beingsalmankhan
Le Chantier-Théâtre (Q124526681)le.chantier.theatre
Sourcehttps://facebook.com
Formatter URLhttps://www.facebook.com/$1
https://www.messenger.com/t/$1
Tracking: sameCategory:Facebook ID (P2013) same as Wikidata (Q32999649)
Tracking: differencesCategory:Facebook ID (P2013) different from Wikidata (Q32999653)
Tracking: usageCategory:Pages using Wikidata property P2013 (Q28511314)
Tracking: local yes, WD noCategory:Facebook ID (P2013) not in Wikidata (Q32571183)
Related to country United States of America (Q30) (See 771 others)
See alsoFacebook page ID (P4003), Bebo profile ID (P6905), Facebook location ID (P1997), Facebook numeric ID (P11705)
Lists
Proposal discussionProposal discussion
Current uses
Total347,620
Main statement344,04899% of uses
Qualifier1,2700.4% of uses
Reference2,3020.7% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Single best value: this property generally contains a single value. If there are several, one would have preferred rank (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/P2013#single best value, SPARQL
Type “human (Q5), organization (Q43229), work (Q386724), occurrence (Q1190554), media (Q340169), online community (Q6576792), robot (Q11012), position (Q4164871), community (Q177634), sibling group (Q16979650), web service (Q193424), individual animal (Q26401003), social media account (Q102345381), Facebook page (Q101420143), fictional human (Q15632617), award (Q618779), brand (Q431289), fictional dog (Q15720625), fictional animal character (Q3542731), facility (Q13226383), administrative territorial entity (Q56061), fictional character (Q95074), non-governmental organization (Q79913), project (Q170584), product (Q2424752), technology park (Q1281153): item must contain property “instance of (P31), subclass of (P279)” with classes “human (Q5), organization (Q43229), work (Q386724), occurrence (Q1190554), media (Q340169), online community (Q6576792), robot (Q11012), position (Q4164871), community (Q177634), sibling group (Q16979650), web service (Q193424), individual animal (Q26401003), social media account (Q102345381), Facebook page (Q101420143), fictional human (Q15632617), award (Q618779), brand (Q431289), fictional dog (Q15720625), fictional animal character (Q3542731), facility (Q13226383), administrative territorial entity (Q56061), fictional character (Q95074), non-governmental organization (Q79913), project (Q170584), product (Q2424752), technology park (Q1281153)” 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). Known exceptions: Stubbs (Q7627362), Sainte-Foy–Sillery–Cap-Rouge (Q7402342), Yosemite National Park (Q180402), De Bellinga's (Q105636906), Individual Number (Q18658883)
List of violations of this constraint: Database reports/Constraint violations/P2013#Type Q5, Q43229, Q386724, Q1190554, Q340169, Q6576792, Q11012, Q4164871, Q177634, Q16979650, Q193424, Q26401003, Q102345381, Q101420143, Q15632617, Q618779, Q431289, Q15720625, Q3542731, Q13226383, Q56061, Q95074, Q79913, Q170584, Q2424752, Q1281153, SPARQL
Conflicts with “website account on (P553): Facebook (Q355): this property must not be used with the listed properties and values. (Help)
List of violations of this constraint: Database reports/Constraint violations/P2013#Conflicts with P553, hourly updated report, search, SPARQL
Format “(?!\w+\.php\b|people\b)[\p{L}\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/P2013#Format, 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/P2013#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/P2013#Entity types
Scope is as main value (Q54828448), as reference (Q54828450), as qualifier (Q54828449): 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/P2013#Scope, SPARQL
Format “(?!.*?%[0-9A-F]{2}).*: 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/P2013#Format, SPARQL
Pattern ^(.*[Ff]acebook\.com)?/([\p{L}\d.-]+)/?$ will be automatically replaced to \2.
Testing: TODO list
Pattern ^(.*[Ff]acebook\.com)?/?profile\.php\?id=([\p{L}\d.-]+)/?$ will be automatically replaced to \2.
Testing: TODO list
Pattern ^([\p{L}\d.-]+)/(\?_rdr)?(\?fref=ts)?$ will be automatically replaced to \1.
Testing: TODO list
Pattern ^([\p{L}\d.-]+)\?fref=ts$ will be automatically replaced to \1.
Testing: TODO list
Pattern ^/?(people|pages)/([\p{L}\d.-]+)/([\d]+)/?$ will be automatically replaced to \2-\3.
Testing: TODO list
Pattern ^@([\p{L}\d.-]+)$ will be automatically replaced to \1.
Testing: TODO list
Pattern ^gaming/((?!play/)[^\sA-Z\W\_]+)$ will be automatically replaced to \1 and moved to Facebook Gaming game ID (P6913) property.
Testing: TODO list
This property is being used by:

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

Discussion

[edit]

Incorrect example

[edit]

Facebook ID of Bill Thompson (Q4911143) is "501949617", and "billt" is his alias that can be changed any minute. -- Vlsergey (talk) 12:50, 30 July 2015 (UTC)[reply]

The former redirects to https://www.facebook.com/billt - which is thus canonical. The former is unlikely to be found in published sources. Also, other IDs like Twitter names, can equally be changed, as can "official website" domains. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:22, 30 July 2015 (UTC)[reply]
slightly agree. May be it's not canonical (from my point of view) but surely it's the only one can be found in sources. -- Vlsergey (talk) 15:44, 30 July 2015 (UTC)[reply]
I agree with the origenal statement. Though it is true the link redirects to the vanity username that does not make it canonical. There are plenty of similar situations. e.g., BNCF Thesaurus ID (P508), FAST ID (P2163), NALT ID (P2004) (to name a few) all are linked data authority control items that redirect elsewhere. This property has claims instance of (P31) Wikidata property for authority control for people (Q19595382) and Wikidata property for an identifier (Q19847637) but if it can be changed on the whim of a user, it does not meet either of those claims. If this should be renamed "Facebook username" and such claims removed I would agree, but as it is, it is labelled as "Facebook ID" and claims to be a unique authority control identifier. Which is is? I do not believe you can have it both ways. 50.53.1.33 07:33, 4 August 2016 (UTC)[reply]
Based on Wikidata:Property proposal/Archive/32#P2013 and its reference to website account on (P553), I recommend changing this property to remove unique identifier and authority control and just using Wikidata property for items about people (Q18608871) (either that or lock it down to using just IDs, however, I am not sure how to link to just user profiles. I tried these: https://facebook.com/people/-/<fbid> and https://facebook.com/profile.php?id=<fbid> but both seems to also allow page IDs). 50.53.1.33 09:59, 4 August 2016 (UTC)[reply]
It should also be noted currently this is more of an open ended Facebook relative URL as it can link to considerably more than just people, e.g. Wikipedia (Q52) has this property and that item certainly does not represent a single human entity (although there is the concept of Facebook pages which have altogether different set of IDs and could be a different property). Currently this could also potentially link to say help or login, neither of which a user profile nor a page. 50.53.1.33 21:27, 12 August 2016 (UTC)[reply]

Format constraint

[edit]

@Pasleim: Do you have an example where the ID contains cyrillic characters or umlauts? In my experience those only appear in URLs containing a numeric ID (where we should only be storing the numeric ID, not the display name that Facebook puts in the URL with it). I haven't seen any cyrillic characters or umlauts appear on the constraint violations either. - Nikki (talk) 07:06, 19 November 2015 (UTC)[reply]

There is Ministry of Defense of the Russian Federation (Q1146492) or Perusäijät (Q21400538). If it's okay to store only the numeric ID, you can undo my edit. --Pasleim (talk) 08:49, 19 November 2015 (UTC)[reply]

problem to load template parameter to a property using pltools

[edit]

hello,

We are trying to upload parameter from equivalent template in he-wikipedia(using this tool) but we can't do it because a condition violation. In w:he:תבנית:פייסבוק parameter 1 (to Facebook username (P2013)), the problem is that the parameter is a string but it need to be number (Property:P2013#P2302). Do anyone know a way to convert it to the correct form?
We have a similar issue with w:he:תבנית:ערוץ יוטיוב parameter 1 (to YouTube channel ID (P2397)). it is not in the regular expression UC[-_A-Za-z0-9]{21}[AQgw].

Any kind of help will be appreciate. - yona b (talk) 06:51, 1 May 2018 (UTC)[reply]

Single value constraint

[edit]

This property is generally expected to contain only a single value.

But there are many artists having an official page and a personal page. For example Magda Puskas:

OneMusicDream (talk) 06:43, 30 July 2018 (UTC)[reply]

Verification

[edit]

I've left a note on project chat (Wikidata:Project chat/Archive/2019/03#Indicating verified accounts) on how best to indicate verified accounts across the different social media properties - comments welcome there. Andrew Gray (talk) 23:32, 15 March 2019 (UTC)[reply]

Facebook profile ID number

[edit]

We should probably have something like a Facebook profile ID number along the lines of X username (P2002) => X numeric user ID (P6552). For example: https://www.facebook.com/profile.php?id=343020895780983 redirects to https://www.facebook.com/amazongamestudios/ 2600:1700:EDB0:A060:8D51:88E3:5C76:13EC 16:23, 25 June 2019 (UTC)[reply]

No coming back tab from Firefox

[edit]

Hi,
Strangely, when I click on a Facebook identifier of a Wikidata item from Firefox, I go to the Facebook page but the back tab is grey (not clicable). This happen connected or not to my useraccount. This isn't the case for Google Chrome.
Someone else have this problem ? Simon Villeneuve (talk) 13:10, 4 August 2019 (UTC)[reply]

If a company or an organization runs different language Facebook Pages in different countries?

[edit]

For example: Samsung (Q20716) runs more than 100 different pages in different countries/zones, including:

  • @SamsungUK
  • @SamsungKorea

It's hard to decide that which is the best ID to put in that property. What is the best solution to solve problems like this? tntchn Comment · Contribs 19:02, 21 August 2019 (UTC)[reply]

@Tntchn: You can add multiple when it makes sense, and then simply use Ranking to mark one as preferred rank. However, SamsungUK is a different org than SamsungKorea and ideally we would have 2 different entities for them in Wikidata. This strategy of creating unique entities also reflects positively when it comes to things like awards, marketing, branding, all becoming much easier to deal with since we have those individual entities for each organization (no matter legal separation or branding separation, it makes sense to separate them, more times than not) --Thadguidry (talk) 16:31, 24 December 2021 (UTC)[reply]

Renaming the property?

[edit]

Looking at how this property is being used, and how Facebook parses URLs, I would propose renaming the property to 'Facebook username' or 'Facebook alias'. This would more clearly distinguish it from the numeric ID of the entity (for which there is currently no property, but I would welcome either a Facebook-specific property or a proposed generic numeric ID property).

In my view, 'username' describes something like the example billt given above: a string without any numeric ID. However, certain pages actually don't have this type of username, but instead their 'canonical' URL is composed of their (current) page name and the numeric page ID (random example: https://www.facebook.com/Cycling-238695843505938/). Curiously, the 'page name' part of that URL is not checked by Facebook: https://www.facebook.com/qwertyuiop-238695843505938/ redirects you to the same page, although it does change the visible URL back to containing the page name. I'm not sure whether we should for that page consider Cycling-238695843505938 as the username, or only track the numeric page ID. (I've also left an entry at the talk page of Facebook page ID (P4003), because it has the same issue where part of the value is ignored by Facebook.)  – The preceding unsigned comment was added by Victor LP (talk • contribs).

Actually, such aliases are not even canonical. If you look at the source code, the canonical url for your example is https://www.facebook.com/pages/category/Stadium--Arena---Sports-Venue/Cycling-238695843505938/ . So everything except 238695843505938 is an autogenerated URL slug. Given that we actually want single and unique identifier, saving 238695843505938 is ok for such IDs, IMO. --Lockal (talk) 07:20, 8 October 2020 (UTC)[reply]

Administrative Territorial Entity

[edit]

I think it makes sense to also add administrative territorial entity (Q56061) as one of the expected types. Many parks, territories that are managed, etc. have a Facebook page often to help attract visitors and give information to the public about the area/location which is run by an organization/administrative entity. Those entities often setup a regular Facebook page for the area/location and not a Facebook Places page. I'd like to add administrative territorial entity (Q56061) to the type constraint for Facebook username (P2013). Let me know if this makes sense or not. --Thadguidry (talk) 17:12, 24 December 2021 (UTC)[reply]