...
The team updated the existing 2CUL Systems used for E-Resources (updated March 1, 2013) - This spreadsheet describes the tools and systems used for various aspects of e-resource management at each CUL. E-resource troubleshooting can require access to information and the ability to make changes to records in any of these systems, depending on the source of the problem.
Each CUL maintains a Confluence wiki site to maintain policy, procedures, workflows, and best practice information for handling troubleshooting tasks. Each wiki These wikis contains a considerable amount of information . Work and work is underway to updating these wikis update them to a matching organizational scheme with special focus on making troubleshooting information readily available to staff at both CULs.
...
The team has concluded that our overall goals are essentially the same regarding e-resource troubleshooting, to provide quick and effective response to e-resource access problems. Our user populations and our collections share many similarities. Our libraries share some similar organizational complexities, such as semi-independent health science, law and other libraries that perform some independent of their own e-resources work in addition to being part of the larger institution. Success in e-resource troubleshooting is dependent on access to and skill with a number of different systems and tools to diagnose and fix problems, track and refer complex issues to the appropriate experts, and a broad understanding of the nature of e-resources at each institution.
...
The team gathered information about FTE involvement, troubleshooting job responsibilities, typical top-level workflow, and volume of incidents handled. We have concluded that staffing and productivity levels related to e-resource troubleshooting are very similar between Cornell and Columbia. Both partners currently have front line staff scheduled to address incoming issues, refer to specialists, and follow up from approximately 8am to 5pm, Monday-Friday. Supervisory level staff handle some high-priority incidents over evenings and weekend. Each CUL handles a similar volume of troubleshooting traffic. From January to March 2013, Columbia received 244 incidents and Cornell received 251. Precise comparisons are limited by the varied ways in which each partner receives incident reports. More detailed information about this can be found on the Problem Examples and Staffing levels and general workflow pages.
Chart 1: Breakdown of E-resource Troubleshooting incidents by Type (January-March 2013)
(Click to enlarge thumbnail)
Continuing work:
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 to automatically populate (Jira? other?). . 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 - Information To improve information access and data normalization ? Variables 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 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.