Release date: June 7, 2023

Pull slips are now generated from a Jasper Report .jrxml file in ReShare. A default pullslip.jrxml file will be provided upon upgrade to release 1.12 that will replace the current hard-coded pull slip in ReShare.
The existing pull slip generation from the Supply app now calls an endpoint to get a PDF of the pull slip(s).
Staff now have the ability to produce a batch of pull slips up to 500 requests. The previous limit was 100. (Release 1.12.1)
Staff can save the pull slip(s) prior to printing.
Staff will need to explicitly click “Mark pull slips printed” when generating pull slip(s) for printing, in order to have their state updated from “Awaiting pull slip printing” to “Searching”.

...

Added a flag “Attach PDF” to the pull slip notification table to allow staff to indicate that they wish to have the pull slips attached to the email notification as a PDF, rather than simply including a link to those requests in the ReShare UI.
If “Attach PDF” is enabled for a pull slip notification, the pull slips in the batch will automatically have their state updated from “Awaiting pull slip printing” to “Searching”. This will allow staff to print their pull slips from the email notification directly. When they next sign into ReShare, they will be in a position to directly fill the request when they call it up.
A maximum of 100 500 pull slips can be created in one batch. If a pull slip notification contains greater than 100 500 pull slips, multiple emails will be sent. The email subject line will clearly indicate this, e.g. You have 104 504 new ReShare pull slips - requests 1-100500, You have 104 504 new ReShare pull slips - requests 101501-104504.

A new “Pull slip configuration” setting has been added to Settings>Resource Sharing
In the Pull slip configuration setting, tenants can upload a different logo to use on their pull slips.

Note: the default logo for the consortium will be uploaded at upgrade time and staff do not have to update this setting.

In the Pull slip configuration setting, tenants can upload a custom pull slip .jrxml file to generate a different pull slip from the default.

Note: the default pullslip.jrxml for the consortium will be uploaded at upgrade time and staff do not have to update this setting.

...

If the validation of a patron fails, the request is put into a state of “Invalid patron”. If staff use the action “Redo borrower check” and the check fails again, they are currently being presented with a confirmation that the check was successful. This has been corrected to display the proper response.

With the Borrower Check = NCIP turned on in Host LMS integration settings, if a request was initially in a state of “Invalid patron” and staff use the “Override borrower check” to override the check, the system returns a “Success: Override borrower check” message but the action is NOT actually successful. The request stays at a state of “Invalid patron” when it should move on to the next state. This has been corrected to move the request to the next state.

Non-functional changes

Completed the changes required to support different state models within ReShare. (This will enable ReShare to support non-returnables and Controlled Digital Lending workflows in future releases.)
Upgraded stripes and other UI dependencies
GenerateRequestsByState had been duplicated in the StatisticsController and ExternalApiController. It has been moved to a shared location so if a bug occurs it will be fixed in both.
The mod-rs rs/directoryEntry API now returns a complete directory entry that matches the format returned by the mod-directory /directory/entry API
Extended logging so that it outputs the information in a structured format
Added an endpoint to allow dynamically changing of the log level

...

Versions Compared