Property talk:P4011
Documentation
identifier for an article in the Semantic Scholar database (40 hexadecimal digits; for numeric ID see P8299)
![]() |
List of violations of this constraint: Database reports/Constraint violations/P4011#Format, hourly updated report, SPARQL |
![]() |
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 |
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)
- 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)
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)
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)
- All Properties
- Properties with external-id-datatype
- Properties used on 10000+ items
- Properties with format constraints
- Properties with constraints on items using them
- Properties with unique value constraints
- Properties with single value constraints
- Properties with entity type constraints
- Properties with scope constraints
- Properties with conflicts with constraints