LMS Implementation Management Team
Meeting minutes 8/26/99, 10:30 AM
Rm. 303 Olin Library

Present: Lynne Personius, Chair, Lynn Brown, Karen Calhoun, Susan Currie,
Philip Herold, Diane Hillmann, John Saylor, Linda Westlake, Scott Wicks

Lynne reported that the "workflow questions" are due and that copies have
been distributed to various members. She wants members to contact her if
they need additional manuals/documentation. The Technical and Conversion
Manual and the Accessories User's Guide are 1998 editions. Lynne
distributed a list of materials available from Endeavor (Appendix E) and
she asks that people notify her if they need additional items from this list.

Prior to the October training period, members should review manuals
relevant to their specific functional areas. In addition everyone should
review the System Administration User's Guide, which outlines what will be
covered during the October meetings/training period.

Lynne is meeting regularly with the LMS Steering Committee: Sarah Thomas,
Ross Atkinson, Tom Hickerson and, from CIT, Helen Mohrmann, Director of
Network Operations. Lynne feels very, "lucky to have this support". 

Lynne presented the Implementation Management Team's charge:

1. Configuration Decisions for each functional module
2. Data migration planning, decisions, specifications
3. System installation - hardware and software
4. Cornell coordination for development of Voyager/GFA interface
5. Implementation of electronic reserve
6. Coordinating the development of customized reporting capabilities
7. Planning for the distribution of Voyager reports - hardware, training needs
8. OPAC customization/Gateway/PES Integration
9. Recommend Cornell trainers, who will be confirmed by LMT, consult as needed
10. Contribute to the Project Web Site maintained by Jennifer Conklin
11. Involve, coordinate, and inform appropriate library committees of progress
12. Test, and approve, Voyager installation

Discussion of each charge as presented:
1. Configuration decisions will be made for each functional module. We
will make decisions based on what's covered in the System Administration
manual and how things will work locally at CUL. 
2. Data Migration: Review data migration questionnaire. One question we
will need to review will be how "pattern data" for specific ISSNs is
handled. Voyager provides pattern "templates" not specific pattern data
for individual titles. This means that to allow checkin of serial titles
in Voyager, each title will need to be matched with a pattern template, and
exceptions, captions, levels of hierarchy, etc., designated as well. We
would like to explore the option of loading specific third party pattern
(not template) data, which could be linked to our titles via ISSN. This
strategy (for which we would need to contract and pay for Voyager
programming) would save us considerable time and effort at a critical
juncture in our transition. Data clean-up needs to be a part of the data
migration component. Peter Hoyt, along with others in TSSU, are already
working on this.
3. System Installation: Surinder is coordinating this effort. The
hardware has arrived but the boxes were in poor shape. The Sun engineers
will begin setup next Monday. 
4. The GFA Interface is new and will be a joint development effort between
CUL and Endeavor. S. Currie suggested that Pat Schafer join in this effort.
5. Electronic Reserves will be made available across campus.
6. Customized reporting: May require significant work up front but will
have major payoffs down the road.
7. Planning for the distribution of reports and training needs, will be a
significant effort.
8. Expect a significant amount of work to successfully integrate the OPAC,
Library Gateway and PES into the Voyager.
9. Need to pick trainers. These folks will receive specialized Endeavor
training and then will train the rest of the staff. Normal job assignments
and tasks will have to be altered in order for these folks to assume this
responsibility. Need people with the "right stuff". Endeavor staff will
sit through mock sessions to ensure trainers are prepared. Pamela Rothbard
and Susan Markowitz will assist with logistics and general support.
10. Jennifer Conklin is setting up a project Web site. Ed Weissman will
champion this effort.
11. All members will need to communicate effectively with the library
community at large. Individual members will be assigned various standing
committees so as to facilitate this communication. We will work through
these committees to get specific work done and tasks accomplished. Need to
be "good listeners" as well as conveyors of information! Individuals were
assigned committees for which they will be responsible. 
Univ. Faculty Library Bd. - Ed W.
LMT - Ed W.
Council of Librarians - John S., Linda W.
Academic Assembly. - Bill K. Elaine E.
Library Gateway - Lynn B.
TSEG - Diane H.
Working Group on Cataloging - Karen C.
PSEC - Pat S.
CD Exec - Scott W.
IRPC Steering - Philip H.
Access Steering - Susan C.
PES Working Group - Surinder G.
General Selectors - John S. and Scott W.
ERC - Ed (several members of the Implementation Team are on ERC)

In addition to these liaison roles, members will need to communicate
effectively with department libraries that have their own acquisition
operations. IMT recommends that the LMT policy decision (July 20, 1999
meeting) that all library units will use all of Voyager's basic functional
modules, including acquisitions, be clearly stated in early LMS
communications. 

John Saylor will be setting up an IMT-L listserv for the implementation
committee. Minutes will be sent to CU-LIB for broad library access.

12. Test, and approve, Voyager installation. Implementation team will need
to make it work and make decisions accordingly.

Implementation needs: It has ben recommended that any technical processing
be done on a 21 inch monitor. A 19 inch monitor is the smallest unit
acceptable. Most members will need upgrading to the large monitor [Note:
Library management is reviewing the overall equipment needs and related
funding issues.]

Endeavor Training Program:
CUL has contracted for the following, so far:
1. Project Planning, 9/9 and 9/10 -- The Implementation Team will attend
the morning sessions on 9/9 and then all day on 9/10. Details for the
sessions are being worked out between Lynne and Marlene Harris, Endeavor.
2. In addition we are to go through Orientation Training on either October
5 and 6 or on October 8 and 9. These will be two repeat sessions covering
two days each. Please let Lynne know soon your preferred set of dates.
3. Training for data migration will be scheduled over a three day period.
4. Functional training will be approximately four days this fall.
5. Customized Reporting training will be held in the spring.
6. Other training efforts:
Voyager OPAC
Production
Training our local trainers
Installation and technical training (during project planning phase)
Follow-up training after we are up and running
Image server training (Digital Library Initiative -- will use with
electronic course reserve

The following documents were distributed at the meeting:
Today's meeting agenda
Appendix E: Endeavor Printed Documentation
Appendix C: Cornell University List of Contract Issues and Endeavor
Responses (amended)
Appendix B-3 (continued) Customized Training For Cornell University
Appendix B-1 Voyager Software for Cornell University
Cornell's Library Workflow Questionnaire and Customer Contact Profile (copy
of memo sent to Marlene Harris)
Implementation Management Team Computer Needs (inventory)
Voyager 98.1 Technical Manual, March 1, 1999
Voyager 98.1 Accessories Manual, March 1, 1999

Minutes recorded by Lynn Brown
_________________