Project Ideas 2025/26 Quipu eRENEW does not work with discovery system

2

3 days ago

Martha

open0

new feature-categoryOPAC

A tt2 file, erenew.tt2, performs some logic to determine if a patron is eligible for eRENEW and sets a system parameter.

When using a discovery layer like Aspen, the patron fills out a form in the discovery layer’s environment and never interacts with the tt2 files in the Evergreen opac. The renewal fails because the tt2 file never sets the system parameter.

It would be beneficial to have a library setting that indicates that a discovery system is handling eRENEW and pushes the renewal through. It is assumed that the discover system performed the necessary checks.

https://bugs.launchpad.net/evergreen/+bug/2146568

Related Ideas

Context options for some Circulation Permissions

open2 weeks agoCurrently permissions related to circulation use the checkout library as the context for permissions granted at the Branch or System level. In a conso...Read more

Give option to place hold for new adds to a hold group

open2 weeks agoIf a person is added to a hold group for which a hold has already been placed and the holds are still being actively filled (i.e. there are unfulfille...Read more

Max hold enhancements

open2 months ago(Item from 2023 Project Ideas) There isn't currently a way to restrict holds based on circulation modifier. Having a feature similar to circulati...Read more