You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

1.  JSMIN discussed our vision for Phase 2.  The effect of the decision to postpone Alma implementation and the clarification of limitations on supervision may result in course correction in several areas. The group agreed on the importance of making demonstrable progress and the need to lower barriers for the teams to test workflows. Concern was raised that without ALMA teams are expected to "play together without a toy", meaning that  increased imagination and creativity will be necessary to achieve integration.

2.  Making it easier to work in each other's Voyager systems is a priority.  Adam will investigate in the Virtual Desktop Group. The importance on being on the same Voyager release was stressed. Jim and Kate will discuss making sure that Systems help is a priority with Bob and Xin. 

3.  Should we unify our macros?

4.   JSMIN talked about whether workflows developed in Phase 2 really needed to be "transferable" to our ultimate shared system.  We should think instead that Phase 2 lays the groundwork for integration through deeper understanding of how we can realistically work together.

5.  We need a "proof registry."

6.   JSMIN reviewed the talking points and re-articulated the vision for TSI Phase 2. We will move forward without a joint LMS and we believe that the supervisory issues may be difficult but they are not show stoppers.

Re-Articulation of Vision for TSI Phase 2

1. Continue purely local procedures when appropriate for cost, efficiency, legal or political reasons.  Assume integration unless proven otherwise. Question long held political and other reasons for maintaining the status quo.

2.  Measure and evaluate the costs of TSI including the less tangible benefits of collaboration.  Do not be afraid to take risks and keep in mind that a seeming inefficiency in one area may lead to benefits up or down stream just as they do in one's own institution. Your data will aid in evaluating 2CUL at the macro level.

3. The new 2CUL "integrated technical services operation" will continue to have separate reporting lines within Columbia and Cornell but will (to the extent possible) operate as a single unit and set priorities and allocate resources to achieve maximum efficiency across the two library systems as a whole.

4. The integration of 2CUL technical services will take place without a joint LMS.  We should not wait for Alma but should continue to plan for a shared system at some point in the future.  Workflows developed now will lay the groundwork for a joint system.  We should keep in mind that we still expect to implement a common library management system (necessary to achieve the "full benefits of technical services integration," as stated in the project description) in the future.


  • No labels