Cornell University Library Voyager Implementation Site    

IMT Meeting Notes
5/18/2000

In Attendance: Linda Westlake, Philip Herald, John Saylor, Pat Schafer. Lynn Brown, Susan Currie, Lynne Personius, George Kozak, Diane Hillmann, Karen Calhoun
Handouts: "Detail Implementation Schedule for Cornell Voyager Cut Over" and the final draft of the memo to supervisors regarding security and employee ID's and passwords

Observations from Donna Smith visit
She was surprised at how much we wanted to know. Need to be sure to follow up with her about our unanswered questions and our requests for more documentation. She really couldn't believe that we've come as far as we have. Hopefully, this will mean that production will go much more smoothly for us than it has for other institutions. Learned that left-anchored searches make many queries/reports much easier. Want to try to make some left-anchored indexes. Still need to learn more about SQL reporting. This is really the most appropriate for some of the reports we want to run.

Reporting Working Group - Karen Calhoun
The reporting working group had three main goals for Implementation.
1. Have day 1 printing of notices, fines, fees etc. There is now a body of people that know how to do this.
2. Have some custom accounting reports ready. We're in pretty good shape. Lydia has been working on this and she has a plan. We will have electronic feed to accounting departments and link to the bursar.
3. Have reports for selectors to track expenditures. Didn't plan to have this ready for implementation but have actually made good progress. Still planning to have Alan Manifold come and work with us.

Karen is chairing a subgroup from different units to capture system-wide statistics. They'll be using software from Gary Strawn. This software seems to be a pretty powerful interface. Can use it to mark records, to check records in/out identify sets of records and maybe to address some reserve issues. MyLibrary group may also be able to use this software to solve some issues they've been working on.

It looks as if all goals will be accomplished by June 26th. What will be the future of the Reporting Working Group? This is probably a good question for all the working groups but particularly reporting because it is a new and on-going function. The original intention of the steering committee had been for the library's standing committees to take over post-implementation.

SysAdmin configuration
The source of the SysAdmin files that are copied over to the production database will be the 2nd test migration database. We have until the end of the day Tuesday, May 23rd, to modify these files.

Security - Linda Westlake
Finalized the draft of the security memo that will go out to unit heads. It will contain a description of the security structure as well as the Net ID's, passwords and profiles for each employee in the unit. The unit heads will be responsible for distributing this information to their employees. The memo also mentions that the passwords will not be active until the modules come up. The draft of the memo was distributed at the meeting and will also be passed by the Steering Committee at their next meeting. Any comments about the memo should go to Bill Kara.

Betsy Gamble is preparing a master file of all ID's and profiles as well as definitions of the profiles which will be placed on the documentation web page.

A special thank you goes out to Lyndsi Abbey who input the ID's and profiles of all library staff!

Schedule
Lynne has attempted to combine the schedules for all the functional units into one master implementation schedule. Copies of this schedule were distributed at the meeting. Let Lynne know of any items that should be added or changed in the master schedule. It was mentioned that we should note in the schedule the times when it will be ok to do configuration. Morgan Elmore will post the final schedule on the implementation web page and send an message to cu-lib alerting people that a new schedule has been posted.

The bib extract has been completed. It will not be put on the server until the server has been cleaned out to avoid confusion.

Consulting Opportunity Tomorrow
Dan Sweeney is here for EDI training. He will have time on Friday 5/19/00 in the afternoon to answer other implementation questions. Susan Currie will talk to him about the call slip function. The reporting working group will spend their weekly meeting with him. He knows circulation and cataloging the best so think especially of questions in those areas.

Patron ID and the Patron Empowerment Screens
There has been trouble with these screens that we can't fix because we don't have access to the necessary tools. Voyager needs to do this for us since it is a high priority but we haven't heard anything from them about it.

Patron File Updates
Weekly loads of student records into our patron file have traditionally stopped during finals week. This year, the last student transfer is May 10th. The last transfer of new faculty and staff records will be May 19th. The absolute end date for doing anything to the NOTIS patron file is June 6. Traditionally, we have entered summer students records manually but we are not able to do so this year. This is very important! The patron file must be absolutely in sync with the circulation file for the final load to function properly. Also, Summer Session and Continuing Education are issuing standard picture ID cards for the first time and will have online records for summer students. We will not transfer these into our new Voyager patron file until early July. We want to test the transfer first. This means that any patron with a new ID will have to have manual circulation until early July.
The final patron file extract from NOTIS will be delivered to Endeavor on June 6.

Security
There are some permissions that are not related to clients like access to the server that will need to be defined. The security committee will make a recommendation to the steering committee about how to define these permissions.

Training Database
CUTrain will be the training database until we go live. After implementation, the 1 million record database will be the training database.

Cornell ID cards used to check out library materials
There will be some confusion caused by the phasing out of social security numbers in favor of PeopleSoft Employee ID numbers. While there are many faculty and staff at Cornell whose charge ID (patron barcode in Voyager) is made up of their social security number, the SSN field in Voyager will be blank! Staff will not be able to search by SSN--only by institution ID which is the Employee ID produced by Peoplesoft. Searching can also be done by name and patron barcode (25510---------1). In records passed from the Registrar, the Voyager institution ID is derived from the SSN of the student but the SSN will not be a searchable field for students either. Library employees need to be aware of the distinction between PeopleSoft and social security numbers since they have the same number of digits.


- Library Management System Implementation Site - Cornell University Library - Ithaca NY -
last modified on: June 1, 2000