Get article by CORE ID
A documented CORE operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
Get article by CORE ID
- GETReads data · articles
core.ac.uk/articles/get/{coreId}
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which CORE operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
Other CORE operations
- Batch operation for search through all resourcesPOST · changes data
- Batch operation for search through articlesPOST · changes data
- Batch operation for search through journalsPOST · changes data
- Batch operation for searching through repositoriesPOST · changes data
- Batch operation for retrieving articles by CORE IDPOST · changes data
- Batch operation for retrieving journals by ISSNPOST · changes data
- Get all near duplicate articlesPOST · changes data
- Get articles by similarity to a textPOST · changes data
Questions
- Can HumDay get article by core id in CORE?
- Yes. This operation is published in CORE's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Does this change anything in my CORE account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in CORE.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your CORE account.
Where this came from
Read from a published API description for CORE at core.ac.uk/api-v2/doc. The description above is the provider’s own wording, not ours. Last published 2019-07-22.