Webhook events for withdrawn items should include MMS-ID
I would like to suggest that webhook events for withdrawn items should include the MMS-ID the item was associated with. Why does this matter? We've created a custom solution for locations in Primo VE, and to save on the number of API requests to Alma and speed up the loading, we're caching the results. We're using webhooks to update the cache as needed, based on MMS-ID. However, as withdrawn items does not include information on MMS-ID, we cannot automatically update the cache when items are withdrawn.
1
vote
Niklas Lehto
shared this idea