Versions Compared

Old Version 16

changes.mady.by.user user-f9712

Saved on

compared with

New Version 17

changes.mady.by.user user-f9712

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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.

...