What BiblioMeta is
BiblioMeta is a metasearch engine with artificial intelligence, developed by BiblioLabTech, that lets users search all of a library's resources in real time from a single place: the catalog, subscribed databases, digital journals and the repository. Unlike traditional discovery tools, it does not depend on a prebuilt index. It goes directly to the up-to-date information in each source.
The problem it solves is familiar to any academic library. A typical one runs at least four separate systems: the catalog of its integrated library system, the open access repository, a set of subscribed commercial databases and, increasingly, its own journals on OJS. Each has its own interface, its own search syntax and, for commercial databases, its own login. A student has to decide where to search before typing anything, tries one source, finds nothing relevant and gives up. That is the most common and least discussed reason why subscribed databases show low usage: users never get to them. Our guide to library metasearch explains the mechanics in depth.
Real-time search versus a prebuilt index
| Aspect | Real-time federated search (BiblioMeta) | Prebuilt index (classic discovery) |
|---|---|---|
| When sources are queried | At the moment of each search | In advance, through periodic harvests |
| Currency of results | Always current | Depends on harvest frequency |
| Response speed | Depends on how fast sources respond | Fast, independent of external systems |
| Restricted resources | Queries the source directly, within its license | Depends on the vendor allowing indexing |
| Your own material | Queried live, as current as the source | Often the worst covered |
A central index gives broad commercial full-text coverage and very fast answers, which is valuable for institutions with very large subscriptions. Real-time search wins on currency, on visibility of your own content and on independence from the agreements a third party holds with each publisher. They are different choices rather than better or worse in the abstract, and we say so before you sign.
Which sources it connects, and how
| Protocol | What it usually connects |
|---|---|
| Z39.50 and SRU | Library catalogs such as Koha, queried live |
| OAI-PMH | Institutional repositories such as DSpace, and OJS journals, harvested on a schedule |
| REST APIs | Commercial databases that expose them, each with its own authentication and limits |
| SPARQL | Linked data sources, where they exist |
Whether a database can be integrated depends on three things: whether the provider exposes one of these protocols or only a web interface designed for people; whether your license allows automated queries from an external system; and how access is authenticated. Before quoting, BiblioLabTech inventories every source and checks the protocol confirmed by its technical documentation, not the one promised in a brochure. When there is no technical or contractual route, we say so before signing. In practice, the catalog and the repository connect within the first week, and commercial databases take the rest of the project.
An experience built for exploration
BiblioMeta goes beyond the keyword box. Interactive buttons guide users straight to what interests them, letting them explore by emotions, topics, resource types and user profiles. The interface adopts your institution's colors, typography and brand elements, and it can be published as the main search entry point on the library website, so the first place users search is also the one that covers everything.
A dashboard that shows what your users need
The administration panel shows real-time metrics: what people search, which resources they open, which queries return nothing and how usage evolves over time. For a library, the most useful figure is usually the searches with zero results, because they point to real gaps in the collection or in how it is described. It also shows which resources are actually used, not just which ones the library pays for.
BiblioMeta or BiblioMeta Académico?
BiblioMeta is the base edition, designed for libraries in general, whether public, school, special or academic, with centralized real-time search, exploration by topics and profiles, and a usage dashboard. BiblioMeta Académico adds what universities typically need: natural-language questions turned into optimized search equations, integrated remote access so students reach subscribed databases off campus, a statistics module for collection decisions, and the AI Research Assistant included. If your users must reach licensed resources from home, read our guide to library proxy and remote access.
How a project runs, and what it costs
A typical implementation takes two to three months, and the number of sources and the state of their interfaces dominate the schedule. Connecting a Koha catalog or a DSpace repository is direct; a commercial database may require arrangements with its provider that do not depend on us. No infrastructure is needed on your side, because the platform runs in the cloud.
As a reference, an initial BiblioMeta implementation that connects a catalog and a handful of standards-based sources falls between USD 2,000 and 4,000. Hosting and ongoing support are quoted as a separate annual line, and the number of sources, how standard each one is and the level of visual customization move the price. A library that already runs Koha and DSpace starts with an advantage, because both expose standard protocols. If your library has only a catalog and no subscriptions, there is nothing to federate yet, and we will recommend waiting until a second system is in place.
Sources change: a provider updates its API, the library cancels or adds a subscription, the catalog is upgraded to a new version. A metasearch engine without maintenance starts failing silently, returning fewer sources than users believe they are searching. That is why the annual service covers monitoring and adjusting every connection.
Where BiblioMeta runs today
At the Escuela Colombiana de Ingeniería Julio Garavito, BiblioLabTech implemented BiblioMeta on a platform that already included Koha, DSpace and a reference chatbot. It is published as the library's single search entry point, with an administration panel and real-time usage statistics, so the library can see what is searched and which resources are actually used. Read the case study.
BiblioLabTech works remotely with libraries in any country. Send us your list of sources and we will reply with a proposal built source by source, with the protocol and effort of each one.