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.
Cataloging for Koha libraries
Photograph the title page and copyright page. CatalogLense reads them, checks what it read against the Library of Congress, and hands you a MARC21 record to review — then saves it to your own Koha, on your own network, with 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 provider your library chose, 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.
Keyword, title, author, ISBN or accession number.
Patrons with photos; check out, renew, check in, holds and payments.
Auto-detects the format, or lock it to your labels'. Handheld scanners work too.
Koha unreachable? Saves wait on the phone and upload when it's back.
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.
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, because the AI provider is a cloud service — on the phone, at capture time. Everything after it — review, saving, search, shelf reading, circulation — is between the phone and your own Koha. Your Koha server never needs to be online.
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.catalogue to search and view; editcatalogue to create records and copies. 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.
Pricing
The two plans differ in who pays for the AI and how many phones sign in — never in which features work.
Monthly, per library · pricing on request
Monthly, per library · pricing on request
Privacy
No accounts to register, no copy of anyone's catalog. The app talks to your Koha directly.
Credentials are kept in the phone's secure keychain. Catalog and patron data go only to the server address you enter.
Google or Anthropic — whichever you pick. ISBNs and titles go to public book-data services. No analytics, no ads, no tracking.
CatalogLense is a cataloging tool for library staff. It connects to your library's own Koha server — the address you enter yourself. We do not operate a server, we have no user accounts, and we have no way to identify you.
None of this is sent to us. We cannot read it.
Your Koha credentials and the catalog, patron and circulation data you work with — only to the address you configured. On a local network with a plain http:// address the connection isn't encrypted, and the app warns you when this applies.
When you use AI cataloging, your book photos go to the provider you selected: Google (Gemini) or Anthropic (Claude). If you haven't entered your own key, requests may use a key supplied with the app. ISBNs, titles and author names go to Open Library, Google Books and the Library of Congress. These services keep data under their own privacy policies.
No analytics, telemetry, crash reporting or advertising. No tracking across apps or websites. No selling or sharing of personal information.
Everything the app stores is on your device; uninstall it to erase it. Records saved to Koha live on your library's server. Personal data of Philippine residents is protected under the Data Privacy Act of 2012 (RA 10173).
The complete Privacy Policy, Terms and Conditions and Terms of Use are also in the app, under Settings → About & Legal.