Batch operation for retrieving journals by ISSN in CORE
A documented CORE operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Batch operation for retrieving journals by ISSN
- POSTChanges data · journals
core.ac.uk/journals/get
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. Because this one changes data, it cannot run until you have explicitly granted it.
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
- Get all near duplicate articlesPOST · changes data
- Get articles by similarity to a textPOST · changes data
- Batch operation for retrieving repositories by CORE repository IDPOST · changes data
Questions
- Can HumDay batch operation for retrieving journals by issn 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.
- Will this change my CORE data?
- Yes — this is a POST operation, so it changes something in CORE. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- 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.