Voyager 6.1: Some Upgrade Issues
With any software upgrade come changes. For the most part, these changes are functionally sound and
enhance users’ interaction with the system. Sometimes new bugs are introduced with upgrade. This
document gives a brief overview of some of the more obvious bugs in the Voyager 6.1 software.
Fortunately, the list is small, due to the intensive testing efforts made by Endeavors’ 6.1 Field Test
partners. This group really put the software through its paces to ferret out problems. CARLI was a
participant in the 6.1 field testing. To summarize:


WebVoyage Item Status Display
In WebVoyage, the status of a particular title displays on both the titles page [multi-bib view]
and the full record page [singe record view]. In certain cases the status displays do not agree.
For example: On the titles page, a record shows a status of "Damaged". On the full record
page and in the circulation client, it displays correctly as "Overdue, assumed lost". This issue
has been reported to Endeavor [Incident #121573]. As a temporary solution, the text “Click for
Details” will be made to display after the “Status:” label on the titles page [multi-bib view].
Acquisitions Workflow
If you use the following procedure to receive items in Acquisitions at your library, you will need
to alter your workflows after upgrade until this issue has been fixed:
When receiving items in 2001.2 you were able to highlight the item you wanted to receive on
the Receive/Mark screen (see below) and then use the down arrow key and the space bar to
highlight subsequent items. In version 6.1 when you attempt to use the down arrow key you
will get a "Run-Time Error '13'; Type Mismatch" and be kicked out of the client. This issue has
been reported to Endeavor [Incident #121885].




Circulation Reserves/WebVoyage: Problem A
Editing an e-item link in Reserves is not updating the link in the elink_index. Workflow
implications: Link/URL appears in the client to be updated, but does not display correctly in
WebVoyage. CARLI has “Me-Too’ed” this incident in SupportWeb [Incident #113641]
Circulation Reserves/WebVoyage: Problem B
URLs for e-reserve items are sometimes not displaying in WebVoyage. This is only for some
e-reserve items that were already in the catalog before the upgrade. New e-reserve items that
are created post-upgrade display the URL properly in WebVoyage. This has been reported to
Endeavor [Incident #122299]
Circ Alerts at Discharge
Even when properly configured in System Administration, Circulation Alerts for the
route_to_cluster and route_to_location do not work as documented. This problem has been
reported to Endeavor [Incident #114261].
Cataloging/Bulk import: MFHDs not created for long URLs
In bulk import, if the bibliographic record being added to the database contains multiple 856
fields, and at least one of the 856 fields is longer than 200 characters, the associated MFHD is
not added to the database. The log file shows an error message of: No MFHD created.
Failed: MFHD 856. (The bib record is added in this scenario.) [Incident #115990].
(http://www.carli.illinois.edu/I-Share/docs/06upissues.html)