...
- 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
...
E-Resources: General and Troubleshooting
...
A sub-group of the eResources Group will be analyzing the knowledge bases of systems currently and/or potentially used. Selection and shared implementation of joint systems will be critical to realizing an integration of eResources activities.
A critical part of this review will need to be the requirements demanded by the University level financial services units. The number of institution specific procedures or policies for managing funds and payments will have a major impact on our ability to blend and streamline workflows. During TSI and the implementation of a new system it will be important to look critically at procedures and practices and where common ground and efficiencies would be found.
The team has begun working on Phase 2 objectives, particularly in the areas of better harmonizing points of discord and recommending tools to enhance the potential for joint 2CUL troubleshooting. A few of the eventual recommendations we will be making will be dependent on other 2CUL efforts, such as the timeline for a joint LMS. Some of the specific topics or tools we have been exploring are:
- 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 - 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.
- 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.