Fulfillment Proxy Should Receive On Hold Shelf notifications for AFN items
We have found:
---While Fulfillment Proxy users can request both local and AFN items on behalf of the Proxy Sponsor,
---And Fulfillment Proxy and Proxy Sponsor users receive On Hold Shelf notifications for local items,
---Only the Proxy Sponsor receives On Hold Shelf notification emails for AFN items. The Fulfillment Proxy does NOT also receive the letter for AFN items on hold.
We would like Alma to send an On Hold Shelf notification to the Fulfillment Proxy patron for items requested through the AFN by a Fulfillment Proxy. This will mirror functionality for requests placed for local items by a Fulfillment Proxy user.
Debbie Campbell commented
Yes please! We would like the behavior to be consistent between local and AFN items. It causes confusion and inconvenience for our libraries' patrons and library staff when the behavior is inconsistent.
Ex Libris explained to us in a ExL support ticket that:
--For the most part, when working with a Fulfillment Network all notifications are sent from the Item owner, not the patron's home institution. So even though your proxy and sponsor are from your home institution, the notifications being generated are all coming from the 'lenders,' which are the other AFN institutions.
--In this AFN situation, the fulfillment proxy user is placing the request, as you described. But, when it comes time to create the AFN request, it only gets associated with the sponsor user (as there is no field in the Borrowing Request menu to allow for the fulfillment proxy information). And by design, linked accounts cannot be created for fulfillment proxy users, so we have to rely on the information for the sponsor user. So when the request is sent to the lender/item owner, only the sponsor's information is shared and available.
--Because the item owner sends the notification, and only the sponsor's information is sent to the item owner, they are the only one to receive the notification. This is why it differs from local requests - when everything is local, all of the information is available for both parties, so a notification gets sent to both.
So in order to have this behavior modified for consistency for our staff and patrons, it'll need to come through Idea Exchange voting.