Property talk:P4011

From Wikidata
Jump to navigation Jump to search

Documentation

Semantic Scholar paper ID
identifier for an article in the Semantic Scholar database (40 hexadecimal digits; for numeric ID see P8299)
Descriptionidentifier for an article in the Semantic Scholar database
Associated itemSemantic Scholar (Q22908627)
Applicable "stated in" valueSemantic Scholar (Q22908627)
Data typeExternal identifier
Domainwork (Q386724) (note: this should be moved to the property statements)
Allowed values[0-9a-fA-F]{40}
ExampleThe Semantic Web Revisited (Q29037447)5acd1dd3da5752e1de4c5b46f75b7aec2bc50503
Occupational Safety and Health in Peru (Q40166441)4eb67f8548f76574864003baf314e8141f354cba
Sourcehttps://www.semanticscholar.org/
Formatter URLhttps://www.semanticscholar.org/paper/$1
Tracking: usageCategory:Pages using Wikidata property P4011 (Q55924937)
See alsoSemantic Scholar corpus ID (P8299), Semantic Scholar author ID (P4012), Semantic Scholar topic ID (P6611), Google Scholar paper ID (P4028), CiteSeerX article ID (P3784), PubPeer article ID (P7381), ORKG ID (P10897)
Lists
Proposal discussionProposal discussion
Current uses
Total17,686
Main statement17,657 out of 205,356,917 (0% complete)99.8% of uses
Qualifier2<0.1% of uses
Reference270.2% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Format “[0-9a-fA-F]{40}: value must be formatted using this pattern (PCRE syntax). (Help)
List of violations of this constraint: Database reports/Constraint violations/P4011#Format, hourly updated report, SPARQL
Item “instance of (P31): Items with this property should also have “instance of (P31)”. (Help)
List of violations of this constraint: Database reports/Constraint violations/P4011#Item P31, hourly updated report, search, 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/P4011#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/P4011#Single value, 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/P4011#Entity types
Item “Semantic Scholar corpus ID (P8299): Items with this property should also have “Semantic Scholar corpus ID (P8299)”. (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/P4011#Item P8299, 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/P4011#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/P4011#Conflicts with P31, search, SPARQL

constraint “range constraint (Q21510860)” declaration error: “required qualifier “minimum date (property constraint) (P2310)” is missing”.

Why should I add this property?[edit]

I have just created a number of scholarly article (Q13442814) items that might benefit from my adding their Semantic Scholar paper ID (P4011). I'm not sure of the value of adding this property to these items. I'm happy to do the work, but I'd like a little feedback on why it's worthwhile or if my time is better spent adding/editing other items. Any takers? Thanks. Trilotat (talk) 18:24, 28 August 2019 (UTC)[reply]

Trilotat, it's mainly a benefit if Semantic Scholar has the full text, because then it produces an analysis of the references, extracts figures etc. There is no need to add this identifier manually: Unpaywall has 3 million IDs in its latest dump, we can import these. It might be worth curating the IDs after they're imported, though. Nemo 22:41, 29 November 2019 (UTC)[reply]
Pintoch, do you think you can import these with your bot? Nemo 22:43, 29 November 2019 (UTC)[reply]
I am unlikely to find the time to work on that any time soon, sorry! − Pintoch (talk) 10:52, 30 November 2019 (UTC)[reply]
I'm told the IDs in the latest dump are sometimes outdated (since deleted), so it's probably better to wait for the next dump. Nemo 16:14, 3 December 2019 (UTC)[reply]

Constraint Corpus ID[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 from S2. This would also remove 13786 existing violations. --- SCIdude (talk) 08:27, 29 September 2022 (UTC)[reply]

PS: I was wrong, the Corpus ID can be requested through the ExternalIds field in the S2 paper API. Still, I see no reason for the constraint and propose to remove it. --SCIdude (talk) 08:55, 29 September 2022 (UTC)[reply]