Property talk:P12007

From Wikidata
Jump to navigation Jump to search

Documentation

Substack profile ID
identifier for profiles on substack.com
Associated itemSubstack (Q63435709)
Applicable "stated in" valueSubstack (Q63435709)
Has qualitynumeric identifier (Q93868746)
Data typeExternal identifier
Domainhuman (Q5)
Allowed values^\d+$
Usage notesOnly link to substack author profiles not substacks itself. The id can be either numeric or in the form "@username"
ExampleRyan Grim (Q7384105)281006
Adam Tooze (Q351075)2779232
Luke O'Neil (Q85117541)546815
Sourcehttps://substack.com
Formatter URLhttps://substack.com/profile/$1
Lists
Proposal discussionProposal discussion
Current uses
Total146
Main statement13995.2% of uses
Qualifier32.1% of uses
Reference42.7% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
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/P12007#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/P12007#Unique value, SPARQL (every item), SPARQL (by value)
Format “(^\d+$)|(@\w*$): 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/P12007#Format, 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/P12007#Type Q5, 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/P12007#Entity types
Scope is as main value (Q54828448), as reference (Q54828450): 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/P12007#Scope, SPARQL
Item “instance of (P31): human (Q5): Items with this property should also have “instance of (P31): human (Q5)”. (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/P12007#Item P31, search, SPARQL

Adding "@username" format

[edit]

Substack changed the default presentation of user profiles to show the "@username" in the URL instead of the numeric id. The numeric ID can still be found with more technical means probably, in for ease of use extending the regex to allow for both seemed like the most simple solution. Kristbaum (talk) 22:00, 14 September 2023 (UTC)[reply]

I would also like to see this addresses.
Unfortunately the URL formats are different for handles vs IDs.
For example: @billwillingham doesn't work in the profile url https://substack.com/profile/@billwillingham
I wonder if we can follow what we do for YouTube where some bot takes the channel name and converts it to channel ID. https://www.wikidata.org/wiki/Property:P2397 RayScript (talk) 09:03, 15 September 2023 (UTC)[reply]
Unfortunatelly now any items using '@username' style IDs don't work with this property. Perhaps splitting into two properties, like YouTube's YouTube channel ID (P2397) and YouTube handle (P11245), is in order. Trivialist (talk) 02:24, 21 September 2023 (UTC)[reply]
Or this can be solved by allowing both syntaxes (distinguishable by the format) and choosing the proper destination URL in a linking helper (cf. e.g. https://wikidata-externalid-url.toolforge.org). --Mormegil (talk) 15:42, 22 September 2023 (UTC)[reply]
In the meantime, how do you find the numeric ID? Profiles URLs that I see are in the form https://substack.com/@profile and I have no idea how to get the equivalent https://substack.com/profile/123 format? Nclm (talk) 10:43, 27 April 2024 (UTC)[reply]
Just open Network Monitor in Firefox DevTools and just paste status-code:200 into the Filter URLs thingy.
and you will find the https://substack.com/api/v1/profile/posts?profile_user_id=546815&offset=0&limit=13 come up in the search result
status-code:200
status-code:200
status-code:200
I hope this helped you
(Also Wikidata for Web (Q99894727) this is awesome tool, but that dose not work for finding that ID maybe it should be programed for finding that id thingy?) Johshh (talk) 06:03, 25 August 2024 (UTC)[reply]
Also, for us poor clumsy non-robot humans, in addition to the difficulty in locating the numeric id, any property that requires one to insert the "@" symbol before a handle is very poor form. X username (P2002), Instagram username (P2003), YouTube handle (P11245) and probably most other social media identifier properties do not require it. This property is an outlier in addition to a mess. -Animalparty (talk) 01:40, 1 September 2024 (UTC)[reply]