Property talk:P3579
Documentation
Weibo user's identifier
[0-9a-zA-Z_]{2,20}|[0-9]+|u/[0-9]+
”: value must be formatted using this pattern (PCRE syntax). (Help)List of violations of this constraint: Database reports/Constraint violations/P3579#Format, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P3579#Type Q5, Q43229, Q95074, Q1190554, Q4164871, Q16334295, Q729, Q386724, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P3579#Conflicts with P553, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P3579#Entity types
List of violations of this constraint: Database reports/Constraint violations/P3579#allowed qualifiers, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P3579#Label in 'zh' language, search, SPARQL
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
|
|
Discussion
editImport
editI'll work on importing these from zh.Wikipedia shortly. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:08, 3 February 2017 (UTC)
Weibo user ID regular expression
editI 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)
- 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)