Policy on Itypes

Policy on Shared Itypes- DRAFT

Recommended by: Itype Reduction Committee to LINC Policy Council – January 12, 2005

Background:

In 2004, the LINC libraries migrated from Dynix Classic software to Horizon. To implement the migration, all policies and codes that were implemented on Dynix Classic were transferred to Horizon. Although the software products are similar, they are also very different. Horizon relies on åcirculation tables and matricesπ and this data must be transferred to each staff client workstation whenever the user logs in. We were informed by Dynix personnel that the large number of individual library itypes slow down response time and make management more complex. A committee was formed by LINC Policy Council to study this issue in Fall 2004 , which determined that LINC libraries adopt shared itypes as well as global and location-specific specific settings for these itypes.

Policy:

This policy pertains to the shared itypes that all libraries will use in LINC to manage circulation privileges.

Shared Itype Codes

The following itype codes will be shared by all libraries in LINC.

Shared Itype code	description	allow requests	allow circ	group charge
CR1	Circ Request 1	x	x
CR2	Circ Request 2	x	x
CR3	Circ Request 3	x	x
CR4	Circ Request 4	x	x
CR5	Circ Request 5	x	x
CR6	Circ Request 6	x	x
CR7	Circ Request 7	x	x
CR8	Circ Request 8	x	x
CR9	Circ Request 9	x	x
CR10	Circ Request 10	x	x
NCNR1	No Circ No Request 1
NCNR2	No Circ No Request 2
NCNR3	No Circ No Request 3
NCNR4	No Circ No Request 4
NCNR5	No Circ No Request 5
CNR1	Circ No Request 1		x
CNR2	Circ No Request 2		x
CNR3	Circ No Request 3		x
CNR4	Circ No Request 4		x
CNR5	Circ No Request 5		x
CNRGC	Circ No Request Group Charge		x	x
CRGC	Circ Request Group Charge	x	x	x

Global Settings

Global settings for all shared itypes will be set as follows:

Minimum Fine Amount	Minimum fine that would be different than the daily fine amt.	Leave blank and use individual libraries daily fine rate instead.
Fixed Max Fine?	If you want to keep fines on any item from increasing beyond a maximum numeric amount, mark this box Yes	All shared itypes will be marked Yes
Maximum Fine Amount ($ or %)	If the Fixed Max Fine is marked Yes, enter the numeric amount or percentage of fine (ex: 50% of cost of item)	This will be set to 50% for all shared itypes
Keep Circ History (days)	Number of days for which Horizon should keep information about the borrowers who check out items of this itype. After this number of days, Day End deletes the history. (ex: 7)	All itypes will be set to 7 days

Library-Specific Settings

Individual library-specific settings will be chosen from the values below for the shared itypes listed here. All libraries will be responsible for mapping these values to the itypes they choose to use:

Loan Period (days or hours)	The number of days that materials with this itype can be checked out (ex: 14)	0,1,2,3,5, 7,14,21,28 days s
Renewal Period (days or hours)	The number of days that materials with this itype can be renewed (ex: 14)	Same period as original loan period
Maximum Number of Renewals	The maximum number of times materials with this itype can be renewed (ex: 1)	0,1,2,3,5 times
Hold Shelf Period	The number of days that materials with this itype should sit on a hold shelf waiting for pickup, before becoming an expired hold (ex: 5)	3,5,7 (days), with items with short loan period having shorter hold shelf period
Grace Period	The number of days Horizon waits, after an item is overdue, before it begins assessing overdue fines on items with this itype. In Horizon, if the item is returned after this period, fines will still be assessed for all grace days. If the item is returned during this period, no fines will be assessed. (ex: 3)	0,3,7 (days)
Fine Rate	The amount (in pennies) of each daily fine (ex: 10)	0, 5, 10, 25, 50, 100 (pennies)
First Notice Delay (Days)	The number of days after an item is overdue that Horizon waits before Day End processes an overdue notice (ex: 7)	1,3,7,14 (days)
Notice Interval (Days)	The number of days between notices that Horizon waits before Day End processes another overdue notice (Second, Third, Fourth, etc.)	3,7,14 (days)

Maximum # of Notices	The maximum number of notices that will be generated once items in this itype are overdue (this does not include the Final Notice). This can be no higher than 5.	2,3,4,5 (notices)
Max # Out	The maximum number of items that can be checked out in this itype.	2,5,10,25,50,75, 100,500, 9999 (items)
Lost Processing Fee	A processing fee (in pennies) that is assessed when items with this itype are lost (ex: 300)	0, 300, 500, 1000

Implementation

LTLS will be responsible for training and educating library directors on these changes and how they will be implemented. All LINC library directors will be responsible for submitting mapping information (from old, individual library itypes to shared itypes) by May 1, 2005, with implementation in Horizon completed by June 30, 2005.