Jump to content

Property talk:P8299

Add topic
From Wikidata
Latest comment: 1 month ago by Tomodachi94 in topic Required but no way to get it from S2 API

Documentation

Semantic Scholar corpus ID
identifier for an article in the Semantic Scholar database (for hexadecimal ID see P4011)
RepresentsSemantic Scholar (Q22908627)
Associated itemSemantic Scholar (Q22908627)
Applicable "stated in" valueSemantic Scholar (Q22908627)
Has qualitynumeric identifier (Q93868746)
Data typeExternal identifier
Allowed values\d+
Usage notesThis identifier can be found at the top of the page above the title, in the field "Corpus ID".
ExampleP02.91. The effect of a standardized massage application on spinal stiffness in asymptomatic subjects. (Q46028286)37220927
Single-incision laparoscopically assisted appendectomy performed by residents is safe and feasible: A single institution, retrospective case series (Q37643073)9445722
Formatter URLhttps://api.semanticscholar.org/CorpusID:$1
See alsoSemantic Scholar paper ID (P4011), Semantic Scholar author ID (P4012), Semantic Scholar topic ID (P6611)
Lists
Proposal discussionProposal discussion
Current uses
Total248
Main statement23594.8% of uses
Qualifier20.8% of uses
Reference114.4% 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/P8299#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/P8299#Unique value, SPARQL (every item), SPARQL (by value)
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/P8299#Single value, SPARQL
Item “instance of (P31): Items with this property should also have “instance of (P31)”. (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/P8299#Item P31, 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/P8299#Entity types
Item “Semantic Scholar paper ID (P4011): Items with this property should also have “Semantic Scholar paper ID (P4011)”. (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/P8299#Item P4011, search, SPARQL
Scope is as main value (Q54828448): 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/P8299#Scope, SPARQL
Conflicts with “instance of (P31): human (Q5): 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/P8299#Conflicts with P31, search, SPARQL

Required but no way to get it from S2 API

[edit]

The Semantic Scholar API [1] always returns the hex paperID (P4011) but not the Corpus ID. OTOH {{P|4011}} requires a {{P|8299}} stmt because of a constraint made. So I propose to remove that constraint as long as there is no way to get the {{P|8299}} programmatically. SCIdude (talk) 08:25, 29 September 2022 (UTC)Reply

From what I can see, the corpus ID is available if the corpusId field is explicitly requested in the fields parameter like this. —Tomodachi94 (talk) 08:44, 20 April 2025 (UTC)Reply