On this spreadsheet, you will list the places within your institution which will play a role in the consortial borrowing process. These may be a main library and its branches; service desks within a single library, etc.
Because the functions you provide on the spreadsheet becomes the basis for NRE, I will spend a little time discussing this piece of data.
If library staff at a particular library will do these activities, it is a borrowing library.
If library staff at a library will do these lending functions, that library will be a lender. If your library system allows users to specify where they will pick up an item from a list of possible places, each of those places is a pickup location. Remember that any one library can be perform any of all of these functions.
In this part of the questionnaire, you respond to questions about your ILLiad service. The responses to these questions provide OCLC with the information needed to establish integration between Navigator and ILLiad. If you do not have an ILLiad system, you do not have to respond to this section.
Navigator requires ILLiad 7.4 or 8.0. If you have an earlier version, you will need to update it.
The site codes are the codes in the NVTGC column in the Local Info section of the customization manager.
Your patrons may request an item that is available in your library. In the questionnaire, we will ask you how NRE should handle such requests. Your decision will be applied to all requests for locally held items
If you choose to have the request stop for staff review, this is what will happen in NRE. The request will be in a ‘Check Manual’ status, alerting you that staff attention is needed. From the request details, you can see that the item was found locally and what library owns the item.
You can choose to complete the request so that it is no longer an active request or you could choose to remove your location from the lender string and allow the request to progress.
NRE can be configured to send a notification to your patron if you choose to complete the request. In the questionnaire, you will be given sample text for this notification. You may modify it in any way you’d like to suit the needs of your institution. Request details, such as author, title, request number, patron name, etc. can be added to the notification.
This is a sample. The subject line and the text can be modified.
Your patrons may create duplicate requests for the same item. In the questionnaire, we will ask you how NRE should handle such requests. Your decision will be applied to all requests for duplicate items.
If you choose to have the request stop for staff review, this is what will happen in NRE. The request will be in a ‘Check Manual’ status, alerting you that staff attention is needed. From the request details, you can see the request number of the earlier request.
You can indicate in the questionnaire what should happen to unfilled requests.
This is usually a generic ill email. Because of staff changes, we discourage using an individual’s email address. Using a generic email eliminates the need to maintain this configuration as staff changes.
In this section of the questionnaire, you will specify the text you want to send to your users when a request reaches a particular stage in its life cycle.
You can choose to have NRE send a notification to your patron when you have received a requested item.
If you choose to have the notification sent from NRE, you can specify the text of the email sent to your user. The questionnaire includes some standard text which you may modify as you wish. The notification can include details from the request, such as the title and the pickup location.
This is a sample notification for overdue items. Modify it according to your preferences.
Setting a ‘From’ address that is specific to your library allows your patron to reply to the email. It is also less likely that the email will be considered spam by the mail server.
In this example, the Navigator user interface is accessing Austin Public Library’s catalog to display the location, call number and real-time status information.
When a request is made, NRE searches local catalogs to create a lender string of libraries that own the item and have it available for borrowing.
You may be able to get a list of all of your shelf locations from your OPAC system administrator or vender. DO NOT include a shelf location if all items housed in that location are non-circulating.
In this table, indicate the Availability Status from your OPAC and whether items in that status can be loaned.
The shelf location column is to indicate if the shelf location is significant when determining availability. For example, an item that is ‘On Shelf’ is generally available for circulation. However, if that ‘On Shelf’ item is in Special Collection, it cannot be loaned. In this example, the ‘On Shelf’ status must be defined differently for the Special Collections shelf location. In this case, the shelf location is significant for determining availability for borrowing. However, a status like ‘On Loan’ does not require further definition because, no matter what shelf location the item has, it is not available.
If you want to limit patron requests, please indicate how many requests a patron can have at one time. Then indicate what ‘one time’ means. For example, if a patron is limited to 5 requests per month, answer question 3 as ‘30’.
Your responses will be used to configure the form your patron will fill out to request an item from Navigator.
In the questionnaire, please indicate what system and version you use . If you click ‘Other’, please include the system name
It is common for colleges and universities to use a campus directory as the first authentication step. Public libraries tend to use the patron file associated with their circulation system.
In Texas, special arrangements have been made for a hosted ‘local’ EZProxy. If you are part of the hosted EZProxy, you will not have to maintain a local instance of EZProxy.
Note that a Z39.50 server is not required for access unless you do not have one of the 5 supported ILS systems (ExLibris Aleph; ExLibris Voyager; Innovative Interfaces Millennium; SirsiDynix Horizon; SirsiDynix Unicorn).
If you do not have a Z39.50 server, OCLC may be able to use screen-scraping for this information.
![Introduction ,[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)