Allow request-type webhooks to be triggered only under certain conditions
We would like the ability to configure request webhooks such that they are triggered only when certain conditions are met. Request webhooks for patron physical item requests include the user’s primary ID and the title they have requested. This type of circulation information should in most circumstances stay within the library and not be shared with third parties. But it may be necessary to enable a third-party integration in order to provide needed services, such as a smart locker delivery service. Currently, request-type webhooks are triggered by any request in Alma, regardless of request type or destination. We would like our webhook to be triggered only by requests that designate our smart locker “library” as a destination. This way we would send user data to the third party only when it is necessary to perform the service the user has requested. This enhancement would enable us and our students to benefit from this integration without sacrificing patron privacy.
Jeff Karlsen
shared this idea
-
Megan K @ CCSF
commented
This seems like it should be a priority in California due to CCPA.