[Koha-bugs] [Bug 30719] New: ILL should provide the ability to create batch requests
bugzilla-daemon at bugs.koha-community.org
bugzilla-daemon at bugs.koha-community.org
Mon May 9 13:04:36 CEST 2022
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30719
Bug ID: 30719
Summary: ILL should provide the ability to create batch
requests
Change sponsored?: ---
Product: Koha
Version: master
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P5 - low
Component: ILL
Assignee: koha-bugs at lists.koha-community.org
Reporter: andrew.isherwood at ptfs-europe.com
Some interlibrary loan providers, for example Reprints Desk, allow for ILL
requests to be submitted in batches.
In the Reprints Desk case, a batch is created with the supplier, then requests
are then submitted including the batch ID. Obviously, this workflow may differ
according to supplier and these differences should be abstracted away into the
supplier backend.
For core Koha, we should provide the ability for it to recognise if a given
backend can process batch requests. If so, we should provide an interface for
creating and manipulating batches within Koha, then submitting a batch to the
supplier. It should also be possible to view all batches and the contents of a
given batch.
The funding institution has defined the following workflow for creating and
populating batches:
- A encapsulating "batch" is created with a name and a requesting borrower
- Requests are added to a batch via two methods:
- In bulk:
- A form which allows the user to paste in a collection of identifiers,
such as DOI / PMID etc.
- For each of these identifiers:
- The request metadata should be populated via API queries to
metadata suppliers, for example, PubMed API or LibKey/Browzine. This behaviour
is governed by the presence of appropriate plugins.
- (Optional) Once the metadata is populated for an item, we check for
item availability via any installed ILL availability plugins
- Individually:
- A regular ILL request form, requests are added to the batch
--
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.
More information about the Koha-bugs
mailing list