FAQ

 Update Committee Member Info
 Submit Minutes
Circulation SubCommittee
Using Recall/Hold in LUIS
I. Current NOTIS functionality

The library user submits a recall/hold request to a public service desk. The terminal operator places the recall/hold using the current NOTIS recall/hold functionality.

The recall/hold function allows a user to request an item that is currently checked out to another patron. In order to use this function, the operator must have the appropriate authorization level to place the recall/hold and the library user must be of a patron category that is eligible for recall/hold transactions.

A recall causes the system to notify the current user of an item that it is needed by another user. The loan period may be shortened--if your library's policies require this.

A hold request does not cause notification to the current user. However, it may block renewal of the item when it is returned--if your library's policies require this.

When the recall/hold item is discharged, a message is shown that instructs the operator to route the item to a hold shelf or area. Also, a printed message is generated automatically to notify the requestor that the item is available and will be held for a specified length of time.

When multiple recalls and/or holds are placed on an item, the system maintains a first come, first served queue. However, "recall" receives priority over "hold", and "rush recall" has priority over all other requests.

II. New Functionality Priorities

1. Eligible library users will be able to request holds and recalls by submitting their request via LUIS. a) Phase I: Requests will be forwarded to library staff for input into LUIS using current functionality. b) Phase II: Requests will be input into the LUIS system directly by library users with staff mediation.

2. Eligibility will be verified by the system using the patron's library ID number.

3. The terms "recall" and "hold" will not be used in any screen or help documents when referring to this procedure. Instead, 'request" or "request for item checked out" will be used.

4. This feature will be selectable at the institution level only.

5. Only those location codes identified by each institution as eligible for recall/hold will be used with this function.

6. An eligible user may only request a recall/hold for items owned by their LUIS designated home institution.

7. The search context is stored in order to allow the patron to return to the OPAC screen after the "request" is completed.

8. Requests will be made available to library staff via batch files and email.

III.Overview of Procedure

Screen 1: Patron is using his home institution OPAC (on site or remotely). Notes: Recalls/Holds are, by definition, requests for materials at one's home institution. If the REQ command is to appear 'in context' on the screen, the patron must be at his/her home.
Screen 2 : Patron finds the bibliographic record of a needed item. If the item is eligible for recall, 'REQ' now shows in the 'command choices' at the bottom of the screen. Notes: REQ does not appear when items are available. Available is defined as on the shelf or NOT eligible for recall (Ref materials, etc.) Each institution must specify--for programming purposes-- all locations NOT eligible for Recall/Holds online.
Screen 3a: Patron types REQ and is sent to the ID verification screen. This screen briefly explains the 'Request for Item Checked Out' service and directs the patron to her/his library's circulation desk if more information is desired. Near the bottom of the screen is a place for the patron to type in a library card number. The patron has the option to type in the 14-digit number or type 'C' to cancel and return to his/her search screen. If s/he types in the ID, one of two screens will appear:
Screen 3b: Patron types "EXP REQ" to read policy information of his home library.

Screen 4a: Ineligible patron Patron types in the ID number. A message appears on the screen stating that s/he is not eligible and gives a brief explanation (same as used for proprietary databases). Patron types 'c' and is returned to her/his search, i.e., the LUIS screen where REQ was typed. Screen 4b: Eligible patron Patron types in the ID number, and is sent to the next screen.

Screen 5:For verification by the patron, this is a display of the requested title. Also, displayed is the current address on file for that patron. Instructions tell the patron where to get more information-if his/her address is not correct. The same screen also has an input field for the patron to use if s/he wants to be notified by email concerning this item. If the patron chooses to continue, one of two screens will appear.

Screen 6a: The screen lists pickup points (libraries and branches) and allows the patron to choose where s/he will pick up the item. The patron will select a place and press . At that time, the patron will be returned to his/her search at the screen where REQ was typed. Notes: This screen is to be selectable by institution. For those institutions who plan to use this screen, a list of pickup points (Circulation Desks by Service Unit) must be submitted to FCLA. All others will use the following screen.

Screen 6b: This screen simply states that, when the item is available, the patron will be notified where to pick it up. To confirm the transaction, the patron presses . Patron is returned to the bibliographic record where s/he typed REQ. Notes: This screen is to be selectable by institution.

After the patron has completed the request of an item, the request will be saved to a file. Each request will be assigned to a service unit. An institution may choose to have the requests printed with the daily Circ reports or have the requests sent to a file which can then be accessed and downloaded to a PC. Some institutions may also choose to send an email copy to an assigned library email address. (See the example of Recall/Hold Requests file. )


  CSUL HOME | FCLA | WEBMASTER | UPDATE COMMITTEE MEMBER INFO
[ TOP ]