Acquisitions: Monograph Ordering
...
The ordering function is an area where it's more possible to imagine an integrated environment than many other technical services functions because of the nature of an order as opposed to actually handling a physical piece. For example, Columbia could order books for Cornell, and have them delivered to Cornell, especially when we arrive at the place where we use the same library management system.
...
- Might Cornell be able to use its corporate Amazon account to order materials for Columbia?
- Might Columbia selectors be able to better streamline the ordering process by making better use of the POOF interface?
- Might the two institutions be able to share one ordering specialist for more difficult/challenging-to-obtain items?
For more, see this group's Phase 1 Report.
Acquisitions: Monograph Receiving
- Meet and discuss findings with the other relevant working groups (Ordering, Copy Cataloging, Batch Processing).
- Explore points of "harmony" and "discord" revealed in Phase 1.
- Critical issues to explore:
- Shelf ready
- Cataloging upon receipt
- University accounting restrictions
For more, see this group's Phase 1 Report.
Acquisitions: Print Serials
...
Cornell's documentation (certainly in the area of print serials) is notably more robust than Columbia's, and sharing documentation and its upkeep would be very useful, although there are limits to what can be standardized between the two institutions.
For more, see this group's Phase 1 Report.
Automation & Technology: Batch Processing
...
Work with other 2CUL TSI groups in areas of functional overlap to coordinate phase II efforts.
For more, see this group's Phase 1 Report.
Cataloging & Metadata: Copy Cataloging
...
Plan for the Columbia 2CUL copy cataloging group to visit Cornell in the fall of 2013
For more, see this group's Phase 1 Report.
Cataloging & Metadata: Database Maintenance
Obviously maintenance is done very differently at both Columbia and Cornell, but ultimately it doesn't make a difference how each system does it as long as the work gets done. Except for a few specific maintenance processes which will need to be reviewed in later phases of this project, it may be best to keep each institution's "database maintenance culture" similar to how they were pre-2CUL, especially since both systems would require major overhauls of maintenance procedures, policies, and personnel in order to make them work the same. Unlike many of the processes being looked at for 2CUL, large changes in database maintenance procedures will affect many staff members in libraries across both campuses.
For more, see this group's Phase 1 Report.
Cataloging & Metadata: Non-MARC Metadata
...
If non-MARC metadata practices at the two 2CUL institutions extend to become fully-integrated, a joint functional-MWG should form. This functional-MWG would be a separate but parallel entity than the current forum-based MWGs; a separate steering group should guide the effort of the forum-based MWG.
For more, see this group's Phase 1 Report.
Cataloging & Metadata: Original Cataloging
...
- Training (and, where appropriate, documentation)
- Developing guidelines for collaborative cataloging covering such areas as balancing demand and capacity, workflow and handoffs, clarifying expectations, communication, etc.
- Identifying areas where changing collection priorities (e.g. as a result of collaborative collection development) may have an impact on cataloging workload
- Identifying and evaluating vendor services of potential interest, e.g. vendor-supplied cataloging, shelf-ready processing, vernacular data, etc.This may progress to joint negotiations with vendors and establishing common service expectations
- Representation on external bodies (e.g. CONSER) and associated activities including reporting and voting
- Joint policy and standards development: this needs to take place within a framework that will accommodate differences due to contrasting collection priorities and service expectations
- System-related services, including batch processing, reporting, troubleshooting, and their impact on workflow
For more, see this group's Phase 1 Report.
E-Resources: General and Troubleshooting
...
- Off-campus access and variable browser configuration testing - BrowserStack - implementation underway. Both CULs had been using a product called BrowserCam until it was discontinued about a year ago. Since then, we have explored a few options to provide staff with a way to test off-campus use of resources. BrowserStack is now in use at both libraries. There is a subscription cost for BrowserStack that is currently being covered by IT units.
- Troubleshooting tracking system|../../../../../../../../../../display/2cullts/Tracking+system+brainstorming|||\ - A single incident tracking system for managing all troubleshooting reports. The team is working on a features wish list to help inform our recommendations. We will consider systems that are already available in addition to other options. Both CULs have access to Jira and potentially other incident tracking systems. Some key features should be:
- LIBIT-L@cornell.edu and cul-eproblem@columbia.edu or other appropriate sources of reports should feed directly into the system to avoid re-entry.
- Easy to identify Cornell or Columbia issues
- Ability to route issues to non-e-resource staff and to communicate with vendors and patrons via the system.
- More information on troubleshooting tracking system can be found here|../../../../../../../../../../display/2cullts/Tracking+system+brainstorming|||\.
- Common ERM/LMS - To improve information access and data normalization that is essential to efficient and effective joint troubleshooting. Key possibilities include:
- Serials Solutions ERM Suite and Consortial add-on - The team is going to examine cost, implementation & migration workload, gain vs. loss regarding Alma migration to develop a recommendation whether to pursue an interim joint ERM option.
- 2CUL's Alma implementation timeline will be an important variable.
- Workflow and information access - We are working to better organize and eventually consolidate useful information about policies, procedures, and best practices.
- Develop guidelines of what to handle at 2CUL level, what to route to "owning" library.
- Provide a dashboard of common responses, access to troubleshooting tools, and contact information for us4e by all troubleshooting staff.
- Automated link/access checking - Callisto - http://sharpmoon.com/callisto/ - This product has to potential to improve our pro-active troubleshooting efforts by helping us identify access problems before our users report them and ensuring that IP address ranges are properly implemented by vendors. Callisto allows for a consortial view, allowing us to compare access to resources across the 2CUL partners.
For more, see this group's Phase 1 Report.