-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CORE API: Add PDF download feature #59
Comments
That's so good to know. Frankly, I'd never thought about programmatic access to PDFs -- that could help resolve some of the errors that we've had at that stage of the workflow. |
I thought we want to use the api's to be able to find and download PDFs where possible |
@ceteri Should a pdf_lookup method return a PDF object or should it return a link to the PDF of the publication? |
Good question. That depends on whether the returned URL has limitations:
Ideally, if there aren't these or other limitations then we'd prefer to simply lookup the PDF URL and it to the KG for later processing. Alternatively we can refactor the PDF download to an early stage of the workflow if needed. I've noticed a trend where publishers are claiming to have "open access" articles, but in reality you must be logged in and use your browser/cookie "watermarks" where the PDF link requires some JavaScript to run -- in other words, it's not a direct download URL. So many of the errors that we see (e.g., Wiley, OUP ScienceDirect) appear to be due to limitations: Although maybe we need to troubleshoot that download code? |
GET /articles/get/{coreId}/download/pdf
The text was updated successfully, but these errors were encountered: