What you will learn
- What research databases libraries licence, and how members use them
- How authentication works for on-site and remote access
- How federated search spans databases without merging them badly
- How database descriptions help members choose the right source
- How usage data informs renewal and cancellation decisions
What the project is
Academic and large public libraries licence dozens of research databases: journal collections, citation indexes, newspaper archives, and specialist subject databases, each with its own interface, access rules, and content. Members, especially students and researchers, struggle to know which database covers their topic, whether they can access it remotely, and how to sign in. A portal organises that maze into a single, described, accessible listing.
The portal serves members, who find and access databases, and librarians, who manage listings, access, and renewal evidence. It does not replace the databases themselves; it makes them findable and reachable.
Core features
Database listings are the core: each database with a plain description, subjects covered, content types, access conditions, and a direct access link, organised by subject and by type. Authentication handling routes members through the library's sign-in, so licensed access works on site and remotely without separate passwords per database. Federated search lets members search across selected databases from one box, with results grouped by source, so they can start broad and then go deep in the right database.
- Database listings with descriptions, subjects, and access conditions
- Single sign-in routing for on-site and remote access
- Federated search across selected databases, grouped by source
- Subject guides linking databases to topics and courses
- Access troubleshooting: status, known issues, and alternatives
- Usage reporting per database for renewal decisions
How it is built
Start with listings and authentication for the most-used databases, because those carry the daily value. Federated search follows, for a selected set of databases where it works well, rather than for all databases at once, where result quality degrades. Usage reporting should be built early enough to inform the next renewal cycle.
- Inventory licensed databases with descriptions and access conditions.
- Build listings by subject and type with single sign-in routing.
- Add access troubleshooting and status information.
- Add federated search for a selected database set.
- Add subject guides and usage reporting.
Technology considerations
Authentication is the technical core. Libraries use federated identity and proxy systems to give licensed access remotely, and the portal must integrate with those systems correctly, or members will hit paywalls on content their library already pays for. Access failures should be diagnosed plainly: whether the problem is the member's sign-in, the database, or the licence.
Federated search quality needs honest limits. Searching across databases with different metadata produces uneven results, and the portal should group results by source and show each source's own ranking, rather than pretending to merge them into one perfect list.
Challenges to plan for
The main challenge is licence churn. Databases are gained, lost, and renamed at renewal, and a portal that is not updated becomes a list of dead links that teaches members to distrust it. A named owner per database, with renewal dates tracked, is the practical fix. A second challenge is access confusion: members cannot tell whether a paywall means no licence, a sign-in problem, or an embargo, and the portal should explain the difference.
- Dead links from databases lost or renamed at renewal
- Paywalls that members cannot distinguish from sign-in problems
- Federated search results of uneven quality across sources
- Usage data that counts sessions without showing research value
Who it is for, and its limits
This portal fits academic libraries with licensed research collections, large public libraries offering research databases, and library consortia sharing database access across members.
It does not licence or own the databases; it organises access to them. Renewal and cancellation decisions remain with librarians, informed by usage data and academic need. Costs and timelines vary with database count and authentication scope, so confirm with a quote before budgeting.
Frequently asked questions
How do members access a licensed database remotely?
Through the portal's single sign-in routing, which authenticates the member as a library user and passes them to the database with licensed access, without a separate password per database.
What is federated search?
Searching across selected databases from one box, with results grouped by source, so members can start broad and then go deep in the database that fits their topic.
Why do I sometimes hit a paywall?
Either the library does not licence that content, the sign-in failed, or the content is embargoed. The portal should explain which, with alternatives where available.
How do librarians choose which databases to keep?
Through usage reporting combined with academic need and cost. Usage alone does not decide renewal, but it informs the decision alongside subject coverage.
Can databases be organised by subject?
Yes. Listings are organised by subject and type, with subject guides linking databases to topics and courses, so members start from their topic, not from a vendor name.
What if a database I need is not listed?
Members can request it through the portal, and librarians can assess the request against subject need, cost, and existing coverage before the next renewal cycle.