Working with the Task-Lists API
Alma gives staff users the ability to view lists of items that require action. Such lists are called task lists.
For example, task list of borrowing requests includes list of requests that should be reviewed by a resource sharing staff. The staff will review each borrowing request in the list, and will decide whether to fulfill it or not.
A typical task list workflow is to retrieve the task list relevant items (using filters, “find” option or facets), printing it and start working on each task in the list.
Some institutions manipulate the task list items before printing them, or use them in an external application. This can be done using the Print Slip Report option in the task list UI:
- Requested Resources (parallel to the “pick from shelf” task list in the Alma UI)
- Lending Requests (parallel to the “lending requests” task list in the Alma UI)
- GET – in order to retrieve the list of items in the task list. This action supports various filters, according to the business of the task list. It also have a “printed Y/N” filter.
- POST – In order to retrieve the list of items in the task list, as well as marking each item in the task list as “printed“.
The common workflow is to retrieve task list of items which were not printed before, assuming that printed items were already under someone responsibility (the one who printed them). Then, marking each item in the task list as printed. for example, for the Requested Resources API:
This way, the task list’s items will be marked as reported and will not show up again. The retrieved XML/JSON information should then be used by the calling application, for example for printing out slips.
Note that reprinting needs to be handled outside of Alma, in the calling application. It is of course also possible to call the API in a GET mode, so that requests will not be updated with a ‘reported’ status. This of course runs the risk of new requests being added into the system by the time the processing is done and the subsequent POST call is made.