Property talk:P3579

From Wikidata
Jump to navigation Jump to search

Documentation

Applicable "stated in" valueWeibo (Q92526)
Data typeExternal identifier
Corresponding templateTemplate:Weibo (Q14191586)
Template parameterzh:template:Sinaweibo
Domain
According to this template: person or organisations
According to statements in the property:
human (Q5), organization (Q43229), fictional character (Q95074), occurrence (Q1190554), position (Q4164871), group of humans (Q16334295), animal (Q729) or work (Q386724)
When possible, data should only be stored as statements
Allowed values[0-9a-zA-Z]{2,20}|[0-9]+|u/[0-9]+
ExampleUnited Nations (Q1065)un
Karen Mok (Q716027)karenmok62
Global Times (Q970443)u/1974576991
Xinhua News Agency (Q204839)1699432410
Formatter URLhttps://weibo.com/$1
https://weibo.com/$1?profile_ftype=1&is_all=1#_0
Tracking: sameCategory:Sina Weibo ID same as Wikidata (Q51292077)
Tracking: differencesCategory:Sina Weibo ID different from Wikidata (Q51292076)
Tracking: usageCategory:Pages using Wikidata property P3579 (Q44275648)
Tracking: local yes, WD noCategory:Sina Weibo ID not in Wikidata (Q53173657)
Related to country People's Republic of China (Q148) (See 127 others)
Lists
Proposal discussionProposal discussion
Current uses
Total12,243
Main statement11,70195.6% of uses
Qualifier12<0.1% of uses
Reference5304.3% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Format “[0-9a-zA-Z]{2,20}|[0-9]+|u/[0-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/P3579#Format, 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/P3579#Scope, hourly updated report, SPARQL
Conflicts with “website account on (P553): Weibo (Q92526): this property must not be used with the listed properties and values. (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/P3579#Conflicts with P553, search, 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/P3579#Entity types
Label required in languages: zh: Entities using this property should have labels in one of the following languages: zh (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/P3579#Label in 'zh' language, search, SPARQL

Discussion[edit]

Import[edit]

I'll work on importing these from zh.Wikipedia shortly. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:08, 3 February 2017 (UTC)[reply]

Weibo user ID regular expression[edit]

I changed the regular expression to more accurately match Weibo ID. There are two kinds of Weibo identifier. The first one is username/个性域名, it is unchangeable once set and it includes digits and Latin alphabet, it is case-sensitive and its length is 1-20 bytes, though Weibo claimed 4-20. The second one is digital number id which is like Twitter/Facebook. By the way, the second digital one can be prefixed with "/u". Anyone who see the discussion can check it. Kethyga (talk) 13:53, 15 July 2021 (UTC)[reply]

I checked their API and according to my findings, for integer form the ID is the part after /u/ (not including /u/). Also https://weibo.com/1699432410 == https://weibo.com/u/1699432410 there. Therefore, to enforce unique & single constraints, I suggest to strip /u/ prefix for integer form. Lockal (talk) 08:22, 29 March 2023 (UTC)[reply]