Issue Description

Dynix

Horizon

Result

Bandwidth

Low

Dynix was a terminal based product for all the staff functionality.

Higher

Horizon is a client server product for all of staff functionality. Local library networks now impact the individual library's response time.

• LTLS monitors the bandwidth between the local library and the ISP and between the ISP and LTLS. Most of the problems that were associated with this were as a result of local network problems.

Browse Scoping in PAC

In Dynix libraries could choose to scope to their titles in PAC.

In Horizon browse scoping is available but only for alphabetic searches.

• LTLS is working with Dynix to implement the browse scoping option. Dynix staff has provided us mixed signals on whether this will be a problematic search to implement in terms of "drain" on the system resources.

Changing Modules

In Dynix staff had to constantly Log in and out of separate accounts (circulation, cataloging, etc.).

In Horizon the user login gives staff access to everything they need according to their security setup.

• Better workflow management, ease of access to different functions, less wasted time switching between functions.

Changing status of a resource

In Dynix local library staff with appropriate security could easily change item statuses of resources such as to cancel transit holds to set items to trace or lost.

In Horizon if the resource is linked to a patron (i.e., the patron places an item on hold and is waiting for the resource) it cannot be easily changed to lost, trace, or transit by anyone.

• Libraries have to go through additional steps to set items to trace, cancel transits, holds, etc. and be sure that they are honoring the patron request as best the staff can.

Holds Priorities

PAC Agency

In Dynix the location (account) that the patron placed a hold became the place that determined if the borrower was from that library.

For example if I have an Urbana card and I place a hold in the Champaign library, I become a Champaign patron for that request and the material is sent to the Champaign library. If Urbana owns the item and a Champaign patron places a hold on it in Urbana after the Urbana cardholder places the hold in Champaign, the person who placed the hold in Urbana would take precedence over the Urbana cardholder who placed the hold in Champaign.

Borrower Card Agency

In Horizon the library that issues the borrower card determines the priority of the borrower.

For example if I have an Urbana card and I place a hold in the Champaign library, I am still an Urbana patron for that and the material is sent to the Champaign library. If Urbana owns the item and a Champaign patron places a hold on it in Urbana after the Urbana cardholder places the hold in Champaign, the Urbana cardholder would still take precedence over the Champaign cardholder who placed the hold in Urbana.

• Patrons get their library's material first, no matter where the hold is placed (bib level holds) This is a real patron service as the taxpayers of the library that issued the library card get priority service no matter where they are and ultimately it is easier for the patron. The change for library staff is that they may be sending materials to another library to fill an Urbana cardholder request. If there is a concern about sending out new materials, this may be seen as a problem.

• LTLS staff believes that this change really gives priority to the local patron and allows them to make decisions on where they want to interact with the library. It recognizes the mobility of library users while still giving priority to the resources owned by the borrower's home library.

• There is a one basic problem with holds that we are working with Dynix to resolve and that is that if a person places a hold on a specific item (rather than "any copy" of the book) that specific item hold takes precedence over other holds. We hope to get a resolution for this.

Holds Queue – Load Balance

In Dynix LTLS would monitor ILL traffic and work to balance the load between libraries to make it as equal and equitable as possible. We would also manage the queue so that if a library were the next stop on a delivery route, they could get materials faster.

In Horizon, the Holds queue is Alphabetic by library so that larger libraries with names near the beginning of the alphabet are getting more requests than normal.

• Libraries at the beginning of the alphabet are getting more requests than they were on Dynix. LTLS is working with Dynix to see if there is a fix for this.

Index -- Alpha Title Index

In Dynix if there were multiple editions of the same title, the search result would give us a subtotal number of titles – e.g. Gone with the Wind 45

In Horizon if there were multiple editions of the same title, the search result gives you 45 lines of the same title. – e.g. Gone with the Wind

• This requires more scrolling in an alpha search. LTLS is working with Dynix to try to get a fix for this

Indexes -- General

In Dynix some indexes were built on collection codes which libraries assign based on the collection and others were built on Bibliographic record data which is dependent on quality cataloging

In Horizon indexes are built on Bibliographic record data so there is more dependence on quality cataloging

• It is more logical to build indexes on the cataloging data but the result is that some indexes seem to work differently. We are, however, really utilizing the information and the dollars we spend on cataloging to its fullest.

Keystrokes vs. Mouse

Keystroke Driven

In Dynix the client was a text based client and really was not using the resources of computers for staff activities.

Mouse Driven

In Horizon, the client is Windows based and uses the resources of computers for point and click as well as for keystroke. Horizon uses a graphical interface, there is more mouse use, however, most commands have keystroke shortcuts.

• LTLS has discussed keystroke shortcuts in the "We're Live Now What?" training that has been offered since August 18. The information was also listed in the Horizon Basics manual given to libraries in March. The information is also in the Dynix manuals that libraries have had since they first installed the Horizon client.

LTLS staff has also offered to visit Urbana to observe staff processes so that we can assist them in implementing more efficient processes.

Management Data Reports

LTLS had to do a special report anytime a library wanted to produce lists if libraries needed to do collection management, clean up records, etc. In Dynix this was done by using the Recall functionality

In Horizon local library staff can use Create Item Report to create many reports "on the fly" to help with library collection management.

• More functionality for library staff at the local level rather than requiring LTLS to produce the report. This is a wonderful feature of Horizon.

Overdues & Notices

Produced by Circulating Agency

In Dynix the library that circulated the material would generate the overdue and other notices.

Produced by Card Issuing Agency

In Horizon, the library that ≥owns≤ the borrower record generates the overdue and other notices.

• This is a change that library staff and patrons need to ≥get used to≤ and has been complicated because the wording on the notices was not very clear. In the 7.3.2 upgrade the notice wording can be changed and some wording has been changed, but not all as LTLS is waiting for agreement between libraries to make a uniform change.

• Some patrons of libraries that are not automated with LINC are not getting notices, as the libraries don't utilize the function. In the August 6 LINC Update LTLS staff recommended that the owning location of these patrons be the library where the ≥barcode≤ was issued. This solves the problem.

• Other concerns that libraries have raised is that not everyone is issuing notices everyday the library is open. LTLS is addressing this in training.

Security

In Dynix there were a lot of functional passwords that had to be entered many times and editing of library data was limited to the individual library

In Horizon the functional password prompts do not exist, however it is an open system where information created specifically for one agency can be modified by another agency

• All staff members of the LINC consortium have to be trained and very careful not to accidentally alter another library's data. LTLS is getting more "complaints" about unauthorized alteration of library data. We would be very open to suggestions on what to do when we discover who is doing it and if it is deliberate or not. This will be referred to LINC Policy Council, however ideas are welcome. Dynix staff has stated that this will be fixed in Horizon 8.0, which will not be released until late in 2005.

Statistics

Dynix had many statistical reports that libraries used.

Horizon has fewer statistical reports some of which do not provide what the Dynix reports previously provided.

• LTLS is implementing WebReporter, a 3^rd party product, to produce the reports libraries are missing in Horizon. Staff of Champaign, Urbana and Mahomet have assisted LTLS staff in testing this product.