[175] in magellan

home help back first fref pref prev next nref lref last post

Third Barton Project Bi-Weekly Report

daemon@ATHENA.MIT.EDU (Carl Jones)
Wed May 19 16:38:23 1999

Message-Id: <2.2.32.19990519203309.00f2d9f8@po10.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Wed, 19 May 1999 16:33:09 -0400
To: magellan@MIT.EDU
From: Carl Jones <carlj@MIT.EDU>
Cc: 3rdbc@MIT.EDU, 3rdbarton@MIT.EDU

Project Name:  Third Barton Project (Project to find a replacement  
for the MIT LIbrary Management System)
Project Management. Team: Carlj Jones, Nina Davis-Millis,  Joan Kolias
Report Date: May 19, 1999
URL: http:/macfadden.mit.edu:9500/c3/3dbarton

Accomplishments Past Period:
- Met with Endeavor and Ex-Libris Sales Representatives. With both vendor
reps, although the discussions were "casual", not only were we able to get a
better sense of where their companies are going and what kind of
functionality is being offered; we were also able to discuss some of our
concerns, including our thoughts on an extended on-site testing period,
concerns about data migration, etc.

- Final work continues on the Market Survey and Request for Solution
documents. Submitted drafts to Eric Celeste upon his return for comments. 

- Sent belated thank you email note to Functional Checklist and Market
Survey group members.

Goals for the Coming Period: 
- Turn in final working drafts of Request For Solution (RFS) and Market  
Survey documents by Monday, May 24th, to MIT Libraries Steering Committee
members. We will then meet with the Steering Committee on May 27 to discuss
their response to the documents.

- Collect whatever remaining information needs to be gathered for this phase
of the Market Survey, including, where appropriate, making calls to a few
customer sites to ask about their experiences with particular systems. 

- Integrate feedback from Steering Committee into the RFS and, if all goes
well, send out the RFS to selected vendors.

Key Learnings:
-   None this session

Team Dynamics:
It would be beneficial to plan for some team-buidling time in the
not-too-distant future. The team has been working relatively well together,
but now might be a time to step back and review how far we have come,
changes we might want to make to our operating methods, etc. 

Issues: None

Additional Comments:
None


home help back first fref pref prev next nref lref last post