C. Sterback reported that Access Services personnel have successfully completed their training and migrated most of their work to the J Client. Since the Booking module will not be added to the J client until the next software release, the units that use Materials Booking will still need access to the C client until the next software upgrade.
b. Two J client training sessions for Cataloging and Metadata Services staff have been planned. A third session might be added. C. Sterback will attend one of the sessions.
c. Acquisitions is currently planning their migration to the J client. Their training sessions will cover ordering and fund lookup. Selectors will be invited to this session.
d. DTS' J client training will cover serials control and holdings/item maintenance. Training sessions will be held at the end of August.
e. Some units still have workstations that do not meet the minimum requirements for the J client, such as those at the Dana circulation desk. Once these workstations are upgraded, they should begin using the J client. As a reminder, the system requirements for the J client are Windows 2000 or XP, 700MHz processor (1 GHz preferred), 512K of memory (1 GB preferred), and 1024x768 resolution.
f. G. Smulewitz reported that some of the Keyboard Express macros are not operating properly in the J Client. R. Warwick noted that inserting a "delay" by one-fourth of a second allows the J client to catch-up and enables macros to tab appropriately. DTS staff have added delays but they are still not working as expected. DTS staff is compiling a list of their most commonly used macros and will submit it to R. Warwick and A. Butman for review and troubleshooting.
g. C. Sterback noted that some staff members have reported problems using specific ALT+letter combinations that are assigned to Keyboard Express macros. Further investigations revealed that these same key combinations activate Workflows wizard helpers and the wizard helpers take precedence over the Keyboard Express macro. Since there is no way to disable this functionality in the J client, macros that are launched by ALT+letter combinations should be avoided.
h. Some units reported that they were having trouble discharging items in the J client that were going into transit. Specifically, items that were discharged and being routed to another branch library were discharged and listed twice in the discharge wizard. They also yielded a dialog box with an OK prompt that needed to be clicked. C. Sterback investigated and found that it was a barcode scanner issue and that reprogramming the barcode scanner solved the problem.
i. The J Client provides a symbol table for entry of symbols and diacritics that is similar in look and feel to the character map table in Windows. There is a need to explore whether a Keyboard Express macro can be created for this function, as entering diacritics this way is clumsy and time-consuming, especially when there are a lot to enter. It was noted that anyone who uses diacritics must set their J client to use the font named Ariel Unicode MS.
j. It was also noted that adding an item is a two-step process when using the J Client.
C. Sterback distributed a proposed list of goals for discussion. LIS discussed the merits of the goals and proposed the following:
a. Complete the migration to the J client - in-progress
b. Migrate to new Unicorn server/Install Oracle - planned for Spring 2008
c. Test open-source ILS software called Evergreen
d. Explore/implement user-initiated bookings - currently underway by J. Sloan, J. Reinhart, and R. Warwick.
e. Implement EDI for Harrassowitz serials invoices - C. Sterback is currently working with a programming contact at Harrassowitz and an EDI contact at SirsiDynix. Harrassowitz has not delivered an EDI file of serials invoices to a US SirsiDynix site before, so Rutgers is a beta partner in this project.
f. Explore and implement one of two possible options for e-commerce - C. Sterback stated that there are two e-commerce options available in Unicorn. They are 1) paying for fines and fees through iLink (IRIS), and 2) paying for fines and fees via a web interface to the Envisionware software currently in use in the Imaging Center. Access Services would like to begin by reviewing the Envisionware solution so Darryl Voorhees will set up a meeting with the appropriate staff and our Envisionware representative in late summer or early fall.
g. Explore log-in to IRIS using LDAP - In Unicorn GL3.1, SirsiDynix released support for LDAP authentication for iLink (IRIS), so that sites could use it to log in to My Account instead of barcode and pin. Given the limited documentation, we're not sure how SirsiDynix has implemented LDAP, but we should review the code to see whether it will meet our needs.
The next generation ILS was briefly discussed.
C. Sterback reported that the next version of Unicorn, formerly known as GL3.2 and then Rome or Project Rome, would now be known as Symphony. The mergers with DRA and Dynix resulted in a multitude of products that were becoming hard to support and this announcement represents the decision to consolidate their product lines and focus research and development on one platform. SirsiDynix describes Symphony as:
C. Sterback will give a TAS Strategic Training Committee presentation on Symphony in about two weeks. An announcement is forthcoming.
C. Sterback reported that G. Agnew distributed an email to Task Force members outlining the charge and inviting them to serve. It was reported to C. Sterback that all members have not received this message. He will check the names on the list to confirm they have been invited. [Subsequent to this meeting the additional individuals were invited and all have agreed to participate.]
A. Montanaro reported on the SirsiDynix Academic Users Group meeting that she attended during the ALA Annual Conference in June. There were about twenty attendees, including representatives from University of Virginia, Brigham Young University, and Penn State University. There is a rumor that SirsiDynix will be moving their headquarters to Provo, Utah. New owners of SirsiDynix, Vista Equity Partners, have one fourth of their equity in SirsiDynix.
One Director's Station class will be offered this summer and has a full slate of participants. There is already a waiting list for the next round in the fall.
A. Montanaro reported on the VALE OLS project. The VALE committee recommended implementing Evergreen software and the VALE Steering Committee accepted the proposal and recommended further discussions and testing. Other than acquisitions and academic reserves, the software has all needed modules. As part of the paper, Ann prepared a list of functional requirements for Rutgers. Other VALE institutions will review the list, by module, and indicate if the functionality is required, optional, or not needed for their site. In order to test Evergreen software, it will be loaded on a server at Rutgers.
The next LIS meeting will be held on Thursday, September 13 at 1:30 p.m. in the TSB conference room.