[24] in ad-lib
Meeting notes, 2/21/95
daemon@ATHENA.MIT.EDU (mgm@MIT.EDU)
Wed Feb 22 13:44:49 1995
To: acq2@MIT.EDU
Cc: fleish@MIT.EDU
Date: Wed, 22 Feb 95 13:41:25
From: mgm@MIT.EDU
ACTIONS resulting from of our ACQ2 meeting on 2/21 afternoon:
Subgroups were formed with three purposes in mind:
a.) to begin addressing the issues & decision points surrounding their
areas,
b.) identify what needs to be tested, and
c.) what documentation is needed before we proceed with training.
Groups with membership are listed below.
NOTE: It was agreed that these are flexible memberships, and if other staff
are needed, they'll be drawn in as appropriate, or some staff may be needed
only for part of the discussions.
Serials Acquisitions Funds (Structure & use):*
Sheelah (convener), Jennifer, Donna, Ellen, Charlene, & Marilyn
Journal checkin, claiming, binding, routing (central & local):
Ellen (convener), Buddy, Mark
Centralized Serials/Monog. Series (ordering, checkin, holdings):*
Ellen (convener), Buddy, Barbara Ives, Sam, Walter Powers, Marylin
Eastwood, David Van Hoy
Serial publication patterns:*
Ellen (convener), Buddy, Stephanie Stavinsky, Mark, Walter
Serials invoicing:
Ellen (convener), Buddy, Donna
Monograph ordering:*
Charlene (convener), Christine Moulen, Sam
Monograph receiving and invoicing:
Charlene (convener), Charlene, Christine, Sam, Donna
* indicates that these groups will try to meet before the next meeting to
identify issues.
Reports and printing issues will be considered during the course of each
groups discussions, and we'll have chances in our large group to discuss
our needs. We know Grant is now working on printing and Tom is scheduled
to go for Geac report writing training, so we anticipate more on this
later.
Other topics discussed to be continued:
** how to quickly let divisional library staff take a "look see"
without waiting until we can give a polished demonstration. Purpose to
help with the buy in and give them a glimpse of things to come.
** although we will distribute the passwords beyond 14E-210 and Acq2,
how can we insure that people dipping in to see the system don't alter data
that will throw off our testing or modify things that will confuse our task
of identifying problems with the GMA?
** is there a benefit to talking through or putting onto paper an
existing workflow for serials check-in and cataloging interfaces to help
identify areas that we need to be sure to cover in the new system flow?
** given our short time frame for learning, training, testing, and
bringing up the systems, should we be trying to change existing workflows
or just automate what we have, and plan to examine them more closely after
we go live? This may be more obvious for some functions than others.
NEXT MEETING: Thursday, March 2, Library Conference Room 3:30-5
(Charlene & Sam will not join us until 4, but we might
begin with discussing some serials issues first)
