April 12, 2005  

2005 - 050

UPCOMING MEETINGS

 

LINC Policy Council – May 18, 1:30 - 3:30

 

 

2005 - 051 HORIZON IS ONE YEAR OLD!
  How many of you realized that on April 8, 2005, we had our one year anniversary with Horizon? It was a year ago, April 8, 2004, that we came up on the Horizon software. Time flies!
 
2005 - 052 ITYPE RECONFIGURATION MEETINGS
 

To manage the process of switching from individual library itypes to shared library itypes, a series of Itype Reconfiguration Meetings have been scheduled. There are still 3 dates left for these important meetings. Each LINC library director must attend one of these meetings:

10:00-11:30 am, April 15 Watseka Public Library
2:30-4:00 pm, April 15 Danville Public Library
2:00-3:30 pm, April 29 Mattoon Public Library

At the meetings, library directors will receive current itype configuration information as well as forms that need to be filled out to map existing local itypes to the new shared itypes.

 
2005 - 053 SCHOOL LIBRARIES – SUMMER RECESS
 

As the school year winds to a close, remember to notify us about important dates so we can change your settings in Horizon. Please send an email to Helen Neal, hneal@lincolntrail.info, with the following information:

-Date for "turning off" holds
-Date for "turning on" holds (if known)
-Date you want to use as a "fixed due date" (last day of school, etc.)
-Date you want the above "fixed due date" implemented

Also, remember to update your school calendar (Calendar Exceptions) in Horizon to reflect the summer days the library will be closed.

 

 

2005 - 054 UPDATE ON NEXT VERSION OF HORIZON
  We have heard from Dynix that the release of the next version of Horizon (7.4) and LINCPac (4.0) has been delayed. It is still being tested by beta sites. Originally, the product was supposed to be ready by April 1. As soon as these products are in general release, we will schedule and announce the upgrade.
   
2005 - 055 CHECKING OUT ITEMS TO NON-AUTOMATED LIBRARIES
 

LTLS has received several phone calls from non-automated libraries asking why they continue to receive books that they have already given to their borrowers. The answer is - these items are stuck in a loop. How did that happen? The answer lies in how the non-automated libraries' requests are being processed in LINC.

When a request pops for a non-automated library, it says send the item to LTN. All items should be checked to make sure that this is a request for a non-automated library versus an employee here at LTLS. The easiest way to do this is to search for the item by barcode (from the CKI screen after you have cleared the hold message, press F4 and highlight the search index "Item Barcode (item out to borrower)", scan the barcode of the item in, click OK to search. This should take you directly into CKO and the borrower's record.

  • If the borrower is a person send it to LTN. Do not check the item out! LTLS is an automated library.
  • If it is a library building, band the item using the three-letter code in the name of the borrower and then check the item out to that library building.

The loop is caused by not checking the item out. LTLS is asking for your cooperation in spreading the word about this type of hold. Please check with all employees that they are aware of this procedure. We appreciate your assistance!

   
2005 - 056 INVENTORY IN HORIZON
  The inventory module in Horizon is similar to the inventory functionality in Dynix Classic with one big exception - it's faster - in regards to processing of the inventoried items!   The library also has more control of when they start and stop an inventory and individual libraries can now collapse their own collection codes without LTLS involvement.   If you are interested in conducting an inventory this year - please contact Donna Schaal at 217-352-0047 ext. 204 or dschaa@lincolntrial.info.
   
2005 - 057 LINC UPDATE QUIZ
 

Be the first person to correctly answer this question and receive a prize!

"What time (not date but actual hour:minute) did LTLS go live with Horizon?"

If you think you have the correct answer, email Amanda McKay.