Endeavor Meeting Minutes


Endeavor/Voyager Meeting
December 6, 1999 10:00 - 2:00
CPE Meeting Room A

Present:
Endeavor -- Jim Miesse, Linda Voyles
UK -- Dave Block, Tari Keller, Herman Collins
UofL -- Keith Stevenson, Weiling Liu, Cindy Page
WKU -- Nelda Sims
Morehead -- Elsie Prichard, Gary Flanagan
KCTCS -- Paul Fuller
KCVL -- Susan Brown, Miko Pattie
CPE -- Dennis Taulbee

1. Communications:
1.1. Communications Plan: The KCVL Technology Subcommittee will draft a communications plan that will contain the following:
1.1.1. Contact list for hubs, client sites, GOT, Endeavor, KCVL
1.1.2. Task list and assigned flow for problem solving. The Plan then will be verified and established by KCVL and shared with Endeavor.
1.2. Endeavor Incidents Log: Linda will send the Excel file to Miko once a month. This file will be housed at kcvl.org with password protection.
1.3. Incidents Sharing: Sites will use the Endeavor listserv to share info on their incidents so hubs and other client sites are aware of them in a timely fashion.
1.4. Contacts for Other Statewide Implementations: Linda will send us the contacts from other consortial sites with hubs.

2. Support:
2.1. Voyager & Oracle Passwords: Hubs and clients will work out the server password issue. Keith is to file the Oracle password issue as an incident officially.
2.2. Log Entry for Endeavor/Log File for Hubs: Endeavor will routinely create a log entry when they log on to one of our servers. Both hubs will create a log file of local customizations.
2.3. Operational & Trouble-shooting Procedures: The Communication Plan can serve as the basis for these.

3. Adding New Sites to the KCVL Consortium:
3.1. Official Process:
3.1.1. Potential sites will contact Miko. Established cost info for both regular and add-on will be shared.
3.1.2. Miko will contact UK and Uof L to see if either one will host.
3.1.3. Miko will contact Endeavor and the site.
3.2. Cost Model:
3.2.1. UK and UofL will work on the hub site overhead cost.
3.2.2. Miko and Endeavor will work on the licensing, migration, and training costs for both regular (e.g. KDLA) and add-on (e.g. LexMark) new sites.
3.2.3. Miko will poll the private institutions to see how many are interested in joining the consortium. This info will help with our planning.
3.3. St. Catherine's College: Miko will find out if the Endeavor implementation will help with the college's accreditation process. If yes, we will initiate the official process for them. (Note: UofL has since decided to take on St. Catherine.)

4. Software Upgrade Schedule:
4.1. The group have decided to upgrade to Voyager 99.1 for AIX beginnning 3/13/2000 as AIX 4.3.3. upgrade is a prerequsite. It will take 3 days and require taking down the system. There is no provision to do this during off-hours.
4.2. Test Database: Endeavor will make a test database available for 99.1 for all libraries. The group suggested for KCVL to have a test server. Keith will work on cost for this.

5. Funding Requests: Dennis asked that one-time cost funding requests for enhancing the consortium need to be submitted to CPE asap (by end of Jan.) Miko advised the hubs to put these on a priority order.