1 of 56

MAINTENANCE AND TROUBLESHOOTING

ELECTRONIC RESOURCE MANAGEMENT

2 of 56

ELIZABETH SZKIRPAN

COLLECTIONS & DISCOVERY SPECIALIST

BAKER LIBRARY, HARVARD BUSINESS SCHOOL

10+ YEARS IN ELECTRONIC RESOURCES WORK

ESZKIRP@GMAIL.COM

3 of 56

LEARNING OBJECTIVES

IN THIS COURSE, WE WILL LEARN:

    • IDENTIFYING NECESSARY TASKS FOR ELECTRONIC RESOURCE MAINTENANCE
    • UNDERSTANDING THE ERM LIFECYCLE IN TERMS OF WHERE ACCESS MAY BREAKDOWN
    • LEARNING HOW YOU CAN TROUBLESHOOT COMMON ACCESS ISSUES

03

4 of 56

AGENDA

01

INTRODUCTIONS

02

MAINTENANCE AND TROUBLESHOOTING IN THE ERM CYCLE

03

MAINTENANCE VERSUS TROUBLESHOOTING

04

THE ACCESS CHAIN

05

DIAGNOSING ISSUES

06

RESOLVING ISSUES

07

08

PROACTIVE TROUBLESHOOTING

WORKFLOWS AND TRAINING

04

5 of 56

HOUSEKEEPING

THIS COURSE IS PART OF THE AMIGOS ELECTRONIC RESOURCES MANAGEMENT (ERM) MICROCREDENTIAL.

    • You can take courses individually or complete all three ERM courses plus a capstone project to earn the microcredential.
    • Each course includes an assignment to be completed after the class session.
    • To earn the microcredential, you must complete all course assignments and the self-paced capstone project.
    • The capstone project is a three-part assignment reflecting the electronic resources lifecycle, using skills and resources covered in the ERM courses. Students have several weeks after the courses conclude to complete and submit the project.

6 of 56

INTRODUCTIONS

PLEASE SHARE:

    • YOUR NAME
    • YOUR ROLE OR TITLE
    • THE TYPE OF ENVIRONMENT YOU WORK IN (SMALL/MEDIUM/LARGE, PUBLIC/ACADEMIC/SPECIAL COLLECTIONS, PUBLIC/PRIVATE)
    • YOUR PERFECT MEAL

06

7 of 56

ELECTRONIC RESOURCE MANAGEMENT

Electronic resource management (ERM) is the practices and techniques used by librarians and library staff to track the selection, acquisition, licensing, access, maintenance, usage, evaluation, retention, and de-selection of a library's electronic information resources.

8 of 56

ELECTRONIC RESOURCES LIFECYCLE

There are six stages in the iterative e-resource lifecycle: investigation of new content, acquiring new content, implementation, ongoing evaluation and access, annual review, and cancellation and replacement review.

9 of 56

THE IMPORTANCE OF MAINTENANCE AND TROUBLESHOOTING

Proactive maintenance prevents user problems and enhances the experience by reducing frustration.

Systematic troubleshooting helps quickly identify and resolve issues. Following a checklist of common e-resource problems ensures clear communication with users and vendors about the source of the issue.

09

10 of 56

WHAT’S THE DIFFERENCE BETWEEN MAINTENANCE AND TROUBLESHOOTING?

Maintenance

Electronic resources evolve rapidly due to new laws (e.g., GDPR), vendor changes, system updates, and technological advances. Maintenance involves ongoing adjustments to ensure continued access despite these changes.

It is typically preventive, addressing potential issues before they arise rather than responding to problems.

Troubleshooting

Troubleshooting happens after a problem arises and focuses on identifying and resolving the cause of the access issue.

Common steps include verifying login methods, recreating the issue in different settings (on-campus, off-campus, mobile, desktop), and checking vendor communications for outages.

10

11 of 56

TROUBLESHOOTING AS PROBLEM SOLVING

Troubleshooting only occurs once a user, including a library staff user, encounters a problem. We undertake troubleshooting so we can identify the source of a problem so we can resolve the problem at hand.

11

12 of 56

DISCUSSION #1

What are some common electronic resources problems your library and your users encounter?

12

13 of 56

E-RESOURCES HAVE MANY POINTS OF BREAKDOWN

14 of 56

E-RESOURCES HAVE MANY POINTS OF BREAKDOWN (INCLUDING PEOPLE)

Person

Person

15 of 56

TWO TYPES OF E-RESOURCES PROBLEMS

People Problem

Human error can be a major contributing factor in why resources are not working as expected, especially because e-resources have numerous caveats depending on the resource, vendor, and access method.

Technology Problem

Technology problems are problems where we’ve ensured that we’ve checked the human errors first and the issue persists. These problems can be localized or globalized and may or may not be reproducible.

15

16 of 56

THE PROBLEM-SOLVING PROCESS

Library staff are often on the front lines of solving e-resources and technology problems in their libraries.

Following a clear problem-solving process and incorporating those practices into the library’s workflow can help streamline problem resolutions.

16

17 of 56

IDENTIFY AND DEFINE THE PROBLEM

There are numerous breakdown “points” in electronic resources that can lead to a resource not performing as expected, users not being able to access the resource as expected, et cetera. The first step is always to identify and define the problem.

18 of 56

EXAMINE THE SITUATION

Who is experiencing the problem? Are they on a deadline? Can the user show you the problem they are encountering or is it a reoccurring problem if you are the user encountering the issue?

18

19 of 56

CONSIDER POSSIBLE CAUSES

Are users accessing the resource in an anticipated way? Is the problem reproducible? Did we remember the pay the bill/renew the resource on time? Did the vendor send out an email or post somewhere that they are experiencing an outage? Is the problem localized (e.g. In our building/on campus) or global (e.g. No Elsevier users can access their resources). Did we try “turning it off and back on again”? Does our EZproxy stanza look correct? Do we have alternative access to this resource?

19

20 of 56

CONSIDER POSSIBLE SOLUTIONS

    • Resource access breakdown will be a people issue or a technology issue.
    • Is this something we can take are of in-house?
    • Do we need to involve the vendor?
    • What can we do for the user right now?

20

21 of 56

IMPLEMENT THE SOLUTION

Knowing the scope of the problem allows us to begin working towards implementing a solution more quickly.

We may implement the solution ourselves or just kickstart the process to implement a solution if the problem is outside our scope of control.

21

22 of 56

COMMUNICATE AND DOCUMENT THE RESOLUTION

22

23 of 56

TROUBLESHOOTING SKILLS

General Purpose Skills

The skills that can be applied across broad disciplines and are not specific to libraries or electronic resources.

    • Communication
    • Emotional Intelligence
    • Teamwork
    • Prioritization
    • Broad-Reaching Technical Skills: Understanding how email works (or sometimes doesn’t work), Knowing that mobile and PC experiences can differ or that different browsers have different capabilities
    • Problem Solving

Domain-Specific Skills

The skills learned in a specific industry or role. These may be more role-specific in a library setting.

    • Conducting a Reference Interview
    • Understanding How Internet Access Works
    • Computer Troubleshooting
    • Library Resource Authentication
    • Resource-Specific Knowledge
    • Vendor-Specific Knowledge

23

24 of 56

Elimination: The systematic approach used to identify what is causing the problem.

TROUBLESHOOTING SKILLS:

GENERAL PURPOSE

Backtracking: Retracing your steps to see if you can identify where/when the problem began appearing.

Re-creation: Testing the problem on your own or with different users/settings to see if the problem appears for other users.

Half-splitting: Systematically isolating and testing different factors that may be causing the problem.

24

25 of 56

TROUBLESHOOTING SKILLS:

DOMAIN-SPECIFIC

Overview of Discovery and Access Enviornment

Authentication and Authorization

OpenURL and Link Resolvers

Discovery Index, Linking Mechanisms

Metadata Quality, Impact on Discovery

Interaction Between Link Resolver, Discovery Index, Discovery Layer, and Learning Management System

25

26 of 56

DISCUSSION #2

What are the various tactics and skills that you most frequently use in troubleshooting e-resources issues?

26

27 of 56

BREAK

Please take a ten (10) minute break to stretch, use the restroom, and hydrate!

27

28 of 56

THE ACCESS CHAIN

28

29 of 56

BASIC ACCESS CHAIN

29

30 of 56

PROXY SERVER ACCESS CHAIN

30

31 of 56

VPN ACCESS CHAIN

31

32 of 56

RESEARCH GUIDE ACCESS CHAIN

32

33 of 56

DISCOVERY INTERFACE ACCESS CHAIN

33

34 of 56

KNOWLEDGE BASE ACCESS CHAIN

34

35 of 56

DISCOVERY SERVICE ACCESS CHAIN

36 of 56

COMPREHENSIVE ACCESS CHAIN

37 of 56

GATHERING PROBLEM REPORTS

Libraries rely on user reports to find problems with e-resources but there is often issues with motivation and capturing enough information in user reports.

We need to know the Who, What, Where, When, and How of the problem while making sure any reporting process is convenient for users.

37

38 of 56

SIMPLE REPORTING FORM

38

39 of 56

EXPANDED REPORTING FORM

39

40 of 56

TROUBLESHOOTING COMPONENTS

Who reported the issue?

What is the issue?

Where did the issue occur?

When did the issue occur?

How was the issue encountered?

Customer Service

40

41 of 56

DIAGNOSING ACCESS ISSUES

PEOPLE-CONTROLLED COMPONENTS

LIBRARY-CONTROLLED COMPONENTS

VENDOR-CONTROLLED COMPONENTS

41

42 of 56

PEOPLE-CONTROLLED COMPONENTS

42

People (both users and library staff) can play a major role in electronic resources components either working or not working. Remember that all users and library staffers are technologically savvy on different levels so approach electronic resources problems with patience and understanding.

43 of 56

LIBRARY-CONTROLLED COMPONENTS

43

Some e-resources problems will be outside of the library’s scope of control, but we do have control over some components. These components are things that we can look to when we are troubleshooting issues, as well as when we are maintaining our resources to prevent future access issues.

44 of 56

VENDOR-CONTROLLED COMPONENTS

44

If a problem cannot be resolved at the user-level or library-level, we should then look to vendor-controlled components for troubleshooting and problem-solving. These components are not in our scope of control at all.

45 of 56

REVISITING TROUBLESHOOTING SKILLS

General Purpose Skills

The skills that can be applied across broad disciplines and are not specific to libraries or electronic resources.

    • Communication
    • Emotional Intelligence
    • Teamwork
    • Prioritization
    • Broad-Reaching Technical Skills: Understanding how email works (or sometimes doesn’t work), Knowing that mobile and PC experiences can differ or that different browsers have different capabilities
    • Problem Solving

Domain-Specific Skills

The skills learned in a specific industry or role. These may be more role-specific in a library setting.

    • Conducting a Reference Interview
    • Understanding How Internet Access Works
    • Computer Troubleshooting
    • Library Resource Authentication
    • Resource-Specific Knowledge
    • Vendor-Specific Knowledge

45

46 of 56

START WITH GENERAL PURPOSE TROUBLESHOOTING SKILLS

Elimination: The systematic approach used to identify what is causing the problem.

Backtracking: Retracing your steps to see if you can identify where/when the problem began appearing.

Re-creation: Testing the problem on your own or with different users/settings to see if the problem appears for other users.

Half-splitting: Systematically isolating and testing different factors that may be causing the problem.

46

47 of 56

TRIED AND TRUE TROUBLESHOOTING

If you can’t reproduce the issue, ask the reporter to clear their cache and cookies, as well as try a different browser.

If you encounter a paywall on campus, check to make sure that a payment has been made.

If you encounter a paywall off campus, double-check your authentication methods.

If you encounter a broken link, try to navigate to the content in a different way.

47

48 of 56

FEELING STUCK?

Contact the vendor

Check the FAQ for the resource

Ask a listserv or other technical support group

Consult a peer (at your institution or at another institution!)

48

49 of 56

RESOLVING ISSUES

STOPGAP SOLUTIONS

EVALUATING SOLUTIONS

IMPLEMENTING A SOLUTION

REVIEWING RESULTS

05

COMMUNICATION AND DOCUMENTATION

06

TRIAGE

07

WORKFLOWS AND TRAINING

08

STAFF AND THEIR ROLES

09

ACCOUNTABILITY

01

02

03

04

49

50 of 56

HONORABLE MENTION: GENERATIVE AI

CAVEATS:

    • GENERATIVE AI (GEN AI) IS ONLY AS GOOD AS ITS CODE AND ITS PROMPTS.
    • GEN AI IS NOT A LAWYER AND CANNOT HELP YOU DECEIPHER LEGAL CONTRACTS.
    • GEN AI IS A TOOL. IT CAN HELP YOU MAKE AN OUTLINE OR EDIT A WRITTEN DOCUMENT BUT IT IS A POOR CREATOR.

PROMPT:

I WORK AT A UNIVERSITY LIBRARY MANAGING E-RESOURCES. USERS ARE REPORTING THAT THEY RECEIVE AN ERROR MESSAGE WHEN TRYING TO ACCESS A LIBRARY RESOURCE OFF-CAMPUS. I'VE TESTED THE RESOURCE ON-CAMPUS AND HAVE PROBLEMS ACCESSING THE RESOURCE. WHAT ARE SOME POSSIBLE CAUSES OF THE OFF-CAMPUS USERS NOT BEING ABLE TO ACCESS THE RESOURCE?

50

51 of 56

MAINTENANCE

    • Maintenance is proactive troubleshooting.
    • Like general troubleshooting, aim to check access to both new and old resources to make sure nothing is broken.
    • Maintenance troubleshooting is virtually identical to actual troubleshooting, but we are proactively resolving issues (i.e. resolving issues before users report that a problem has occurred).

51

52 of 56

MAINTENANCE TASKS

Preemptively locate and repair problems through regular maintenance tasks such as:

    • Analyzing problem reports
    • Performing access checks
    • Working with vendors
    • Being aware of changes with vendors and their resources
    • Working with peers

52

53 of 56

SAMPLE SCENARIO #1

The following message was received through the library’s chat service:

Hi, I’m trying to read an article online, but it says I have to pay to view it. The article is Use of flipped classrooms in higher education by O’Flaherty.

What are some questions we might ask the user to determine whether they should have access to this article or not?

53

54 of 56

SAMPLE SCENARIO #2

A library staff member is wondering why the library does not have access to some e-books that were purchased several months ago. From the troubleshooting interview, we learn:

    • Who: Library staff member
    • What: e-Books that were previously purchased
    • When: Thursday around lunchtime
    • Where: On-campus
    • How: Tried to access the books via the link in the MARC record

What are some possible causes as to why these e-Books are now inaccessible to the staff member?

54

55 of 56

WHAT QUESTIONS DO YOU HAVE?

ELIZABETH SZKIRPAN, MLIS

Email:

eszkirp@gmail.com

LinkedIn: https://www.linkedin.com/in/

szkirp

ASSIGNMENT

Choose a scenario. Provide the access chain that should provide access to the resource. Brainstorm some troubleshooting steps. Provide one possible solution.

ELECTRONIC RESOURCE MANAGEMENT CERTIFICATE

https://www.amigos.org/node/6710

55

56 of 56

RESOURCES

    • Talbott, H., & Zmau, A. (2020). The electronic resources troubleshooting guide. ALA Editions. https://www.alastore.ala.org/content/electronic-resources-troubleshooting-guide

    • Emery, J., & Stone, G. (2013). Techniques for electronic resource management.(Brief article). Library Technology Reports, 49(2), 1.

    • Emery, J., Stone, G., & McCracken, P. (2020). Techniques for electronic resource management : TERMS and the transition to open. ALA Editions.

    • Carter, S., & Traill, S. (2017). Essential skills and knowledge for troubleshooting e-resources access issues in a web-scale discovery environment. Journal of Electronic Resources Librarianship, 29(1), 1–15. https://doi.org/10.1080/1941126X.2017.1270096

56