Property talk:P8299

From Wikidata
Jump to navigation Jump to search

Documentation

Semantic Scholar corpus ID
identifier for an article in the Semantic Scholar database (for hexadecimal ID see P4011)
Associated itemSemantic Scholar (Q22908627)
Applicable "stated in" valueSemantic Scholar (Q22908627)
Data typeExternal identifier
Allowed values\d+
Usage notesThis identifier can be found by clicking the "Share Link" button from the page of a paper. A URL in the form of 'api.semanticscholar.org/CorpusID:1234567890 will be copied to the browser's clipboard. The numeric part of this URL (1234567890) is the Semantic Scholar 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
Total18,275
Main statement18,25199.9% of uses
Qualifier3<0.1% of uses
Reference210.1% 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]