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

Description:
We are preparing to allow holds on available items across our 2 campuses. So we are mucking with the item-hold-request pages. The form spread across the item-hold-request head, body and tail places the hold. What does the form on the 'confirmed' page (item-hold-request-details) do? What happens if the user does not click on this (second? redundant?) submit button? We need to know whether to emphasize it or not. The func behind the form is item-hold-request-c.

Also, I added a new file called item-hold-request-details-campusyes and it isn't getting used. The other such suffixed pages are controlled out of tab_hold_request_form. Can I add a suffix to item-hold-request-details?

Resolution:
The item-hold-request-details screen is really only there to give confirmation to the user that their request has gone through. If you click the "Go" button on that screen, it re-displays the record you requested. The only thing the form does is to pass the ADM doc-number to the system so it can redisplay the bib record.

No, you can't add a suffix to item-hold-request-details as you have done with those other files. The tab_hold_request_form table is applicable only to the item-hold-request head, body and tail files.

• Article last edited: 10/8/2013