Blocking borrowing requests on books published within the last year
With an active automatic rota for books, borrowing requests sent from Primo to Alma are automatically sent to partner. This applies for books published within the last year as well. Before we activated the autoROTA, we would usually change most of these borrowing requests into purchase requests and place the patron on a waiting list.
New books requested by a patron are often items we want to purchase ourselves, and not spend money on borrowing from our partners in addition. With the autoRota there is no way for us to block these borrowing requests from being sent.
We would like a Sending Borrowing Request Rule with Input Parameter Publication date = within last year (or 2 year, maybe optional range), and Output Parameter Send Request = False.
Peta Hopkins commented
Looks like this is in the Alma roadmap for H2 - 2021 https://knowledge.exlibrisgroup.com/Alma/Product_Materials/010Roadmap/Alma_Roadmap_Highlights_-_January_2021/Fulfillment_and_Resource_Sharing#Automatic_Purchase_Requests
Yes, it would make sense. For us, as already stated, especially the publication date is essential. I believe the user who created the res sha req then will be registered as interested user, and receives the interested in letter, if activated?
We are looking into a feature that would automate the current option to turn a resource sharing request into a purchase request. So, a rule engine would enable to define whether a purchase request should be created based on a number of inputs such as the Requester User Group, Publication Date etc.
Would that make sense ?
Peta Hopkins commented
It would be helpful if there was a way to use publication dates to flag whether the RS or PR request link is displayed in Primo. That would at least help us fine-tune it according to our collection development policy.
Sorry for the delayed answer. On our part the type of patron is irrelevant. We try to have the same level of service to all our patrons. Other institutions may prefer a more differentiated level of service here, I guess.
Rules that would automatically transform a rs req into a purch req makes sense. The important thing is to keep track of history, so we know that this started as a rs req, in case we deny the purch req and prefer to make a ILL instead. Or we like to do both.
What other considerations might make you prefer to manage a patron request as a purchase request as opposed to a resource sharing request ? For example, would it depend also on the type of patron ?
What if we thought about rules that would automatically transform a resource sharing request into a purchase request ? Would that make sense ?
Synnøve Uri commented
I agree - and the request must be overridable.
If the request is held back with status "ready to be sent", like it does with material self ownership=true, then we can approve sending manually.
Reidar Bjorvatn commented
A good suggestion, but naturally these request must be overridable if we choose not to buy the document ourselves.
Effat Zahedifar commented
I agree With this request