Primo brings up Aleph Acquisitions Order Request screen for item unavailable
- Article Type: General
- Product: Aleph
- Product Version: 20
Description:
Our goal is to go live with Primo 3 on May 13 so this is a pressing issue for us as Primo is invoking the
Acquisitions Order Opac Request when a Sublibrary ABCS items are not requestable per settings in Tab15 and Tab31.
Search="Spartacus" in Books and more in Primo...
http://library.abc.edu:1701/primo_library/libweb/action/search.do?dscnt=0&scp.scps=scope%3A%28ab%29%2Cprimo_central_multiple_fe&frbg=&tab=default_tab&dstmp=1300212123605&srt=rank&ct=search&mode=Basic&dum=true&indx=1&tb=t&vl%28freeText0%29=spartacus&fn=search&vid=ABC
Action=Select Locations & Request tab
Behavior=
(When logged in)
1. "See Service Desk" displays in Availability column because this item's item status is set in Aleph as "NOT Requestable"
2. Click on "See Service Desk" and it opens the Aleph OPAC Acquisitions Order Request.
We have never had Acquisitions Order Request set up in Primo 2 and to our knowledge we have not set it up in Primo3. We don't understand how and why a non-requestable item is present that it's availabilty status takes the user to a direct acquisition request in Aleph. I walked through the entire request and it did create a PO in Aleph. We would like this to be turned off.
Resolution:
The user's ability to place an order request (/acq request) is determined by the z61_new_book_permission and z61_new_acq_request settings in the user profile.
Looking in the abc00 usr_library, I see that there is just a single profile (ALEPH) with these settings:
z61_new_book_permission ......Y
z61_new_acq_request ..........Y
If, as you say, you don't want patrons to be able to place Acquisitions Order Requests, then these should both be set to "N".
To change these settings, bring up the Circ client, click on Patrons in the top bar, then "Patron Profile".
- Article last edited: 10/8/2013