The access problem
Institutions frequently hold valuable subscribed and archival content that legitimate users find hard to reach remotely, while administration of subscriptions, publisher relationships and usage reporting consumes a disproportionate amount of staff time.
What good digital library access looks like
Good access means a single point of secure entry regardless of where the user is, role-based authentication that does not create friction for legitimate users, usage reporting that genuinely helps justify subscription decisions, and streamlined administration of publisher relationships and subscriptions.
Common obstacles
Many library systems were never designed for remote or mobile access and show it. Authentication is often either too weak to be trusted or so cumbersome that users find ways around it, and there is frequently no clear visibility into which resources are actually being used.
Balancing security and usability in authentication
Authentication that is too weak puts subscribed and licensed content at risk of misuse well beyond its intended audience. Authentication that is too cumbersome pushes legitimate users towards workarounds that are often less secure than the system it was meant to replace. The right balance usually means role-based access tied to institutional identity, not a single shared credential or an overly manual verification process.
Making usage data useful, not just collected
Most library systems already log some form of usage data, but that data is rarely turned into something decision-makers can act on. Useful usage reporting shows which resources justify their subscription cost, which are barely used and worth reconsidering, and where demand is growing faster than current access allows.
Supporting more than one type of user
Students, faculty, researchers and administrative staff all have different access needs and different tolerance for friction. A system designed around a single generic user type tends to underserve most of them. Role-based configuration should reflect the real range of users, not a single assumed profile.
A practical improvement path
Start by mapping current access points and pain points from the user’s perspective first, then the administrator’s. Introduce authentication that is secure without being a burden, and use real usage data to inform future collection and subscription decisions rather than relying on assumptions.
A practical checklist
- Access points and pain points have been mapped from the user’s perspective, not only the administrator’s.
- Authentication is role-based and tied to institutional identity, not a single shared credential.
- Usage data is reviewed regularly and used to inform subscription decisions, not just archived.
- The system accounts for different user types with different access needs, not one generic profile.
- Publisher and subscription administration has been reviewed for unnecessary manual steps.