AI cataloging Cataloging
Photograph the title page and copyright page. The fields fill in, each with its source — ready for you to review and save to Koha as a MARC21 record.
AI Cataloging for Koha libraries
Works with the Koha in your building, even when the server has no internet. Photograph the title page and copyright page: CatalogLense reads them, checks them against the Library of Congress, and saves the record and the copy (barcode, call number, shelf) to your Koha in one step, every field showing where it came from.
Android and iOS Works with Koha 19.05+ Runs on a local-network Koha
The backlog
Most school, barangay and parish libraries don't have a cataloger on staff, so every new book waits for someone to type its record by hand. Work out what your own pile costs.
An estimate: photographing a few pages, then checking the fields marked for review. Measure your own during a pilot.
100 books typed by hand is 8.3 working days.
A working day here is the hours you chose above. The CatalogLense figure is your estimate, not a measurement.
Words on this page
Local publications, older stock and donated textbooks come back empty — and it needs your Koha to reach the internet.
Books printed before ISBNs, locally published titles and school editions often don't have one.
Works — at a desktop, away from the shelf, a few books an hour, while the cart refills.
CatalogLense reads the book itself, so it doesn't depend on someone else having cataloged it first.
How it works
Tap a step to see it on the phone. Only one step needs you — the review — and that's on purpose.
Copyright page
The back of the title page — ISBN, publisher, place and year.
• The ISBN is read from here, so make sure the ISBN line is sharp.
Saved to Koha
Under your own Koha account
The camera asks for each page by name, with a framing guide shaped for it and tips for a sharp shot: the title page first, then the copyright page, then optional extras like the CIP block, back cover, contents and spine. Each is captured at its own resolution, so 6-point copyright type gets the pixels it needs.
The photos go to the AI, told which page it's looking at and which fields that page is the source for. That's why a library's accession stamp doesn't get read as the publisher.
The Library of Congress, Open Library and Google Books are searched at the same time. A Library of Congress record wins over what the photos said, and subject headings are matched to the authorized form.
About 34 MARC fields, each marked with where it came from. Anything the AI read that isn't printed on the pages is flagged. Fix what's wrong, get warned if you already hold the title, then add the copy: barcode, call number, shelving location.
The record and the copy are created through Koha's REST API, with your own Koha account and permissions. If the server can't be reached, the save waits on the phone and goes through when it's back.
Why the records can be trusted
A catalog is a permanent record. Four safeguards make sure a guess never looks like a fact — try each one below.
Each value carries a badge naming its source, and the sources are ranked. A subject the AI guessed from cover art never looks as solid as a title from the Library of Congress — so your review time goes to the fields that need it.
The trust ladder — tap a source
Each photo is transcribed word for word, and every value the AI read is searched for in that transcript. A value that isn't printed anywhere is flagged for you. Nothing is deleted automatically — you decide.
Transcript · copyright page
Copyright © 2011 by Anvil Publishing, Inc. All rights reserved. Published by Anvil Publishing, Inc. Pasig City, Philippines First printing, 2011 ISBN 978-971-27-3193-8
Some mistakes don't need AI to find. ISBN check digits, impossible years, language names where a MARC code belongs, LCCN and Dewey formats — all checked on the phone, without AI and without a network.
"Filipino" → fillanguage code2099 → flaggedyear in the futureWhen you edit a record, only the fields you changed are rewritten. Control fields, Koha's own fields, your local notes and every subfield you didn't touch pass through byte for byte — the one piece of logic backed by its own automated tests.
A record in Koha
Nothing edited yet.
CatalogLense assumes a cataloger reviews every record. It doesn't catalog unattended, and it never will.
What's in the app
AI cataloging is the headline, but a cataloger's phone earns its keep at the shelf, the desk and the circulation counter. Each tile shows the feature at work.
Photograph the title page and copyright page. The fields fill in, each with its source — ready for you to review and save to Koha as a MARC21 record.
Scan a shelving location book by book: on shelf, misplaced, not in catalog, lost or withdrawn — and at the end, what never turned up.
Find the record, attach a new copy. No recataloging.
Rather type it? A form with your framework's fields, timed against AI on your own phone.
Keyword, title, author, ISBN or accession number.
Patron lookup; check out, renew, check in, holds and payments. Photos with the CatalogLense plugin.
Auto-detects the format, or lock it to your labels'. Handheld scanners work too.
How many items your Koha holds under each collection code and shelving location, and your cataloging pace on this phone. For today, this month, this year or all time.
Koha unreachable? Saves wait on the phone and upload when it's back. No signal for the AI? Photos wait too.
Built from Dewey, author cutter and year, ready for the spine label.
See full MARC and copies; edit or delete either.
Set once, applied to every book you add.
Save each library's Koha and switch between them. Each keeps its own login, defaults and history.
What the AI got wrong and what you fixed — exportable as JSON.
See what your Koha account can do right after sign-in.
Made for offline libraries
Most school and small public library Koha installs are a machine down the hall, reached by a bare IP address. No domain name, no certificate, often no internet. Tools built for hosted Koha fail at the first screen. This one starts there.
Plain http:// is accepted for addresses the internet can't reach — private ranges, .local names — and refused for public hosts, where your password really would be exposed.
The app checks whether your Koha offers password or API-key sign-in, and prefers API keys: they expire on their own and can be revoked per phone.
A missing RESTBasicAuth setting, an untrusted certificate and a blocked local-network permission look the same from inside most apps. CatalogLense names the likely cause.
Koha server address
http://192.168.1.50:8080Local network — acceptedhttp://koha.localLocal name — acceptedhttps://library.example.edu.phEncrypted — acceptedhttp://library.example.edu.phPublic and unencrypted — refused, to protect staff passwordsThe honest boundary: reading the photos needs internet on the phone, because the AI is a cloud service. Photographing doesn't: books shot with no signal wait on the phone and are read once it's back. Signing in to your CatalogLense account the first time needs internet too. Everything else — review, saving, search, shelf reading, circulation — is between the phone and your own Koha. Your Koha server never needs to be online.
Compared with cloud tools
Cloud cataloging services work from a desk and need to reach your Koha over the internet. CatalogLense works at the shelf, on the network your Koha is already on.
CatalogLense
System requirements
What the phones, the network and your Koha server need. CatalogLense works inside the permissions your library already grants — it never asks for administrator rights and never changes a system preference.
CatalogLense can't work with your library until the REST API is turned on in Koha's Administration panel. In the Koha staff interface, go to Administration → Global system preferences → Web services and enable RESTBasicAuth, RESTOAuth2ClientCredentials, or both. If you don't administer Koha yourself, ask your Koha IT administrator — it takes a minute, and the app can't do it for you.
192.168.1.50 is fine.RESTBasicAuth or RESTOAuth2ClientCredentials enabled — see above.patronimages preference on). Needs Koha 22.11 or newer; installed under Administration → Manage plugins. Everything else works without it, and you can skip covers if your Koha already gets them from Amazon or a Coce server. Download the plugin (v1.1.2, .kpz, 52 KB)catalogue to search and view; editcatalogue to create records and copies; circulate to check out, check in and renew; borrowers (view) to look up patrons. With the plugin, tools (upload local cover images) for covers and borrowers (list) for patron photos. Each is only needed for its own feature, and the app shows what the account can do after sign-in.Plainly, so you can decide quickly.
Being worked on next. No dates we can't keep.
Plans
CatalogLense is in beta: Starter and Pro are free while we test. Every plan has the whole cataloging workflow. Plans differ in AI credits, who can sign in, and two extras. One credit is one book read by the AI.
Always free
15 books to try it
Free while in beta
100 books a month
Free while in beta
500 books a month
Custom
Sized for your libraries
Beyond the app
Every plan: manual cataloging, AI vs manual comparison, barcode scanning, catalog search, record editing, adding copies, patron search, checkout, reports, saved servers for several libraries, the offline queue, photos waiting for AI, the permission check, and the in-app guide.
Help us test it. Testers use Starter free during the beta and tell us what works and what doesn't. Best if your library runs Koha.
Join the betaQuestions
A phone app for Android and iOS that catalogs books for Koha. You photograph the title page and copyright page; it builds a MARC21 record, checks it against the Library of Congress, Open Library and Google Books, and saves the record and the item (barcode, call number, shelving location) to your Koha once you've reviewed it.
Koha 19.05 or newer, with the REST API switched on (RESTBasicAuth or RESTOAuth2ClientCredentials). The optional CatalogLense plugin, for cover images and patron photos, needs Koha 22.11 or newer.
No. The phone talks to Koha directly over your library's network, and a bare local IP address like 192.168.1.50 works. The phone itself needs internet only while the AI reads photos, and to sign in the first time.
Yes. It reads the title page and copyright page themselves, so books printed before ISBNs, local publications and school editions can all be cataloged. When a book does have an ISBN, its check digit is verified on the phone.
Z39.50 copies a record another library already made, so it finds nothing for books nobody has cataloged yet. CatalogLense does original cataloging from the book in your hand, and still uses a Library of Congress record whenever one exists.
Every field shows where it came from, every value the AI read is looked for in a word-for-word transcript of your photos, and anything not printed on the pages is flagged. Nothing is saved to Koha until a cataloger has reviewed the record.
Catalog search, adding copies, editing records, shelf reading for inventory, checkout, renewals, check-in and holds at the circulation desk, barcode scanning, call numbers for spine labels, and reports on your collection.
Starter and Pro are free while CatalogLense is in beta. Free gives you 15 books to try it, Starter is for one cataloger with 100 books a month, Pro for a team of five with 500 a month, and Enterprise is arranged for library systems. Prices will be announced at launch — see Plans.
Catalog, patron and circulation data go only between the phone and your Koha: we never connect to your Koha, unless you have us host it under an Enterprise agreement. Book photos go through our server to the AI (Google or Anthropic) and aren't kept.
Yes, on the Enterprise plan. We can set up and run Koha in the cloud for your library, propose other systems that work around Koha, and provide Koha plugins that connect them. Contact us to talk it through.
Contact
Whether it fits your library, a quote for Enterprise, or help getting your Koha ready — write to us. A person reads every message.
Privacy
We keep your email, your library's name, its plan and how many AI credits it used. That's what the account is for.
Catalog, patron and circulation data go only to the server address you enter. We never connect to your Koha unless you have us host it, and Koha passwords stay in the phone's keychain.
Through our server to Google or Anthropic, and not kept. Accuracy reports tell us how well the AI read. They never contain photos or patron data. No ads, no tracking.