60 likes | 297 Views
Automatic Request Deflection Based on Local Holdings Records (LHR s). What is it?. Deflection on individual items, based on information in the Local Holdings Record (Field 008 bytes 20 & 21)
E N D
Automatic Request Deflection Based on Local Holdings Records(LHR s)
What is it? • Deflection on individual items, based on information in the Local Holdings Record (Field 008 bytes 20 & 21) • Lending libraries do not see requests for loans or photocopies of materials they have specified they will not loan or photocopy.
How does it work? • Libraries can edit their Local Holdings Records to specify their lending and reproduction policies. WRS uses the information for automatic deflection. • Requests containing article data are regarded by the system as copy requests. • All other requests are regarded by the system as loan requests • If the system determines the request cannot be filled due to the settings in the LHR, the request will automatically move to the next lender in the string. • The borrower’s Reason for No report will read “Auto-Deflection: request type”.
What happens if I (and the catalogers at my institution) don’t do anything? No deflection occurs unless the default of “undefined” is changed in Field 008 bytes 20 & 21.
Field 008 bytes 20 & 21 • Lending: a=will, b=won’t, u=undefined • Reproducing: a=will, b=won't, u=undefined
What’s next? • A link from within WorldCat Resource Sharing and ILLiad to the local holdings record. • Policies Directory Deflection, Summer 2006: • Lenders can set up deflection in their ILL Policies based on categories like maxcost, type of material, or affiliation. • Exceptions to rules set in the Policies Directory can be defined at the item-level based on Local Holdings Data Deflection. • More information is expected in May or June.