Primo Hold request: “You are not authorized to place requests for this record"

• Article Type: General
• Product: Aleph
• Product Version: 20

Description:
- Access Primo
- Search “Overcome by modernity”
- The first item is the one you need:

- Click on “Request”: error “You are not authorized to place requests for this record” pops up.

Resolution:
It was found that clicking "Request" did *not* trigger any activity in the log of the www_server (-- which is how Primo communicates with Aleph). Therefore, any correction will need to occur in Primo tables or programs.

It looks like the source of the problem is caused by the fact that in the past you had an institute with the code DAB, and the view DBA is behaving as this is still the institute. From site: "The problems we have experienced were caused by wrong configuration of the PDS files, and change of the institution code from DAB into MIN_DAB. After updating the files we see the OvP has started to work in DAB view."

Another case:

"As Aleph didn't even receive the request sent from Primo, Primo must be denying the request internally based on the institute information. We are not sure why it works this way in Primo and if we can change it. We tweaked the PDS institute code and forced both login options to use ABC as the institute code. We can now place a hold request in Primo."

• Article last edited: 10/8/2013