Property talk:P10212

Documentation

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

Stack Exchange user ID
identifier of the account in the Stack Exchange network

Data type	External identifier
Domain	human (Q5)
Allowed values	\d+
Example	Miguel de Icaza (Q62849) → 9211 Randal L. Schwartz (Q93056) → 11625
Formatter URL	https://stackexchange.com/users/$1?tab=accounts
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 Map of people by place values: place of birth educated at work location residence place of death place of burial January 1st dates People with date of birth on January 1 People with date of death on January 1 People with both dates on January 1 Database reports/Constraint violations/P10212 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 137 Main statement 135 98.5% of uses Qualifier 2 1.5% of uses
Search for values

[create Create a translatable help page (preferably in English) for this property to be included here]

Format “\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/P10212#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/P10212#Scope, hourly updated report, SPARQL

Conflicts with “website account on (P553): Stack Exchange (Q3495447)”: 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/P10212#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/P10212#Entity types

Qualifiers “subject named as (P1810), start time (P580), end time (P582), has characteristic (P1552), reason for deprecated rank (P2241), end cause (P1534), retrieved (P813), number of subscribers (P3744), object has role (P3831), subject has role (P2868)”: this property should be used only with the listed qualifiers. (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/P10212#allowed qualifiers, SPARQL

Type “human (Q5)”: item must contain property “instance of (P31)” with classes “human (Q5)” 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/P10212#Type Q5, SPARQL

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/P10212#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/P10212#Unique value, SPARQL (every item), SPARQL (by value)

also add user IDs at various StackExchange sites?

@Dhx1, Germartin1, Rdrg109, Jura1:

I was a bit disappointed there's no prop like "StackOverflow ID"

• then I saw at https://www.wikidata.org/wiki/Wikidata:Property_proposal/Stack_Exchange_user_ID "Stack Exchange lists the existing accounts in the Stack Exchange sites by visiting the profile in the network. Here's an example..."
• I changed the formatter to https://stackexchange.com/users/$1?tab=accounts so it doesn't show just "top Q&A" but all profiles of the person, with reputation and links
• It's great that "by visiting the profile in the Stack Exchange network, we are presented with the links to all the other accounts"
• But I respectfully disagree with "we don't need a property for each Stack Exchange site". I think being able to capture such IDs in WD is beneficial, because then one could display direct links to the more important (or only) exchange that a given user participates in.
• I propose NOT to create extra props, but to use a qualifier to express this data (and the same qualifier to express the different formatter URLs):

Stack Exchange user ID
  formatter URL:
    value: https://stackexchange.com/users/$1?tab=accounts
  formatter URL
    Qualifier: "operator: StackOverflow"
    Value: https://stackoverflow.com/users/$1

Randal Schwartz
  Stack Exchange user ID:
    Value: 11625 -> https://stackexchange.com/users/11625/randal-schwartz?tab=accounts
  Stack Exchange user ID:
    Qualifier: "operator: StackOverflow"
    Value: 22483 -> https://stackoverflow.com/users/22483/

• Rdrg109, would you like to revive this question at a wider audience? I saw your link https://www.wikidata.org/wiki/Wikidata:Project_chat#P553_vs_dedicated_properties_for_online_accounts/usernames, but that discussion is lost in the mists of time...

Vladimir Alexiev (talk) 08:46, 2 May 2023 (UTC)

@Vladimir Alexiev I agree with you that capturing each Stack Exchange site ID in Wikidata is beneficial. Although the user ID in each Stack Exchange site can be inferred from the global Stack Exchange ID, making the user ID in each site available to users can be useful in some use cases where there are limited resources (e.g. computational power, time, etc.)

Now that I think more, I do think we should have a property for the ID in each Stack Exchange site. This because of two reasons:

• Given an account in the Stack Exchange network, its ID is different in different Stack Exchange sites and these IDs are created when the user is willing to interact in that site.
• Most of Stack Exchange sites are created on topics that are relevant to the public knowledge and they are created when there are good reasons to do it (which mostly happens when there is a significant community to maintain it, though sometimes it appears to happen when some business pay some money for having a Stack Exchange site focused on its product).

I'm not associated with Stack Exchange in any way, I just believe having an ID for each Stack Exchange site makes the data in Wikidata more granular and could benefit some users. While it is true that we could use qualifiers, I believe that doing it that way requires extra effort and only a handful of users would remember the qualifier what is intended to be used, so I guess that the community will not consistently contribute.

Let's suppose that we agree that we should have a property "user ID" for each Stack Exchange site. A possible way to avoid having properties that are not used in Wikidata, we could create them as they are proposed and when the user provides relevant examples. For example, let's suppose that Vladimir Alexiev believe that "Stack Overflow user ID" should be created. He would create a property proposal in Wikidata:Property proposal and provide some examples. If there are enough examples and the items on which this property is used are notable, then the property would be created. Now, let's suppose that some other user wants to create "World Building user ID" (link to Stack Exchange site) but doesn't provide notable examples or the items from the examples were just created by him and don't meet Wikidata:Notability, then the property would be rejected.

-- Rdrg109 (talk) 17:29, 2 May 2023 (UTC)

There are pros and cons to both approaches:

• qualifiers are uniform and we could start creating IDs of any StackExchange site tomorrow; also they use the one existing Stack Exchange user ID (P10212) and won't create a plethora of props
• dedicated props are easier to enter and don't need specialized formatterUrl resolution, but will create a plethora of props and each Exchange site will need to pass a separate prop proposal voting

I think we should organize a vote? --Vladimir Alexiev (talk) 13:53, 15 May 2023 (UTC)