Cataloging for Koha libraries

Catalog a book by photographing it.

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

Validate Bibliographic DataLAN · koha.library.net
1 AI value not found on the pages
245 $aTitleLoC
Noli me tángere
100 $aAuthorLoC
Rizal, José, 1861-1896.
020 $aISBNscan
9789712731938
650 $aSubjectLCSH
Philippines -- History -- 1812-1898 -- Fiction.
490 $aSeriesAI
Philippine Classics Library
Not found on the photographed pages — check this value.
Save to Koha

The backlog

Thirty minutes of typing. Now it's a phone camera.

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.

100 books
Typing one record by hand30 min

An original record usually takes 20–40 minutes: about thirty fields, with indicators, punctuation and subject headings.

Hours a day spent cataloging6 h
5 min

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.

Typed into Koha50 h · 8.3 days
Reviewed in CatalogLense8.3 h · 1.4 days

Working days, to scale.

6.9working days back
12books a day, typed
72books a day, reviewed

A working day here is the hours you chose above. The CatalogLense figure is your estimate, not a measurement.

Words on this page

Original cataloging n.
Making a catalog record from scratch, by reading the details off the book itself. What CatalogLense speeds up.
Copy cataloging Z39.50
Importing a record another library already made, over the Z39.50 search protocol. Only works if someone cataloged the book first.
MARC record MARC21
The standard format for a catalog record. Each piece of information sits in a numbered field: 245 is the title, 100 the author, 650 a subject.

Z39.50 copy cataloging

Local publications, older stock and donated textbooks come back empty — and it needs your Koha to reach the internet.

ISBN lookup tools

Books printed before ISBNs, locally published titles and school editions often don't have one.

Typing it into Koha

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

From the shelf to Koha in five steps.

Tap a step to see it on the phone. Only one step needs you — the review — and that's on purpose.

Step 2 of 7 · Required · Next: CIP data block

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.

Capture the pages that count.

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.

Title page AACR2 · RDA
The page the cataloging rules treat as the book's own statement of its title and author. The cover isn't — it's often shortened or restyled.
CIP block Cataloging in Publication
A small block of catalog data some publishers print on the copyright page. A head start, when the book has one.

Why the records can be trusted

An AI that's confidently wrong is worse than a blank form.

A catalog is a permanent record. Four safeguards make sure a guess never looks like a fact — try each one below.

Every field says where it came from.

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.

Provenance n.
A record of where something came from. Here: which source supplied each field.

The trust ladder — tap a source

Nothing reaches Koha without a person.

CatalogLense assumes a cataloger reviews every record. It doesn't catalog unattended, and it never will.

What's in the app

Useful for the rest of the day, too.

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.

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.

Shelf reading Inventory

Scan a shelving location book by book: on shelf, misplaced, not in catalog, lost or withdrawn — and at the end, what never turned up.

Add another copy

Find the record, attach a new copy. No recataloging.

Catalog search

Keyword, title, author, ISBN or accession number.

Circulation desk New

Patrons with photos; check out, renew, check in, holds and payments.

Barcode scanning

Auto-detects the format, or lock it to your labels'. Handheld scanners work too.

Offline queue

Koha unreachable? Saves wait on the phone and upload when it's back.

Call numbers

Built from Dewey, author cutter and year, ready for the spine label.

Record maintenance

See full MARC and copies; edit or delete either.

Cataloging defaults

Set once, applied to every book you add.

Correction log

What the AI got wrong and what you fixed — exportable as JSON.

Permission check

See what your Koha account can do right after sign-in.

Made for offline libraries

Built for the Koha server in your building.

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.

A bare IP is a supported address.

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.

Sign-in adapts to your server.

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 failed connection says what's wrong.

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 — accepted
http://koha.localLocal name — accepted
https://library.example.edu.phEncrypted — accepted
http://library.example.edu.phPublic and unencrypted — refused, to protect staff passwords

The 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

Check in ten seconds.

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.

Your Koha's REST API must be enabled

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.

Phones and tablets Staff devices

Android
Android 7.0 or newer
iPhone and iPad
iOS / iPadOS 16.4 or newer
Camera
A rear camera with autofocus, for small print on copyright pages.
Barcode scanner Optional
The phone camera reads barcodes. A handheld scanner that types like a keyboard works too.

Network Where the phone connects

To your Koha
The phone must reach the Koha server — usually the library's staff Wi-Fi. A bare local IP like 192.168.1.50 is fine.
Internet At capture time
Only on the phone, only while the AI reads the photos. Your Koha server never needs to be online.
Offline
Saves made while Koha is unreachable wait on the phone and upload later.

Koha server Set by your administrator

Version
Koha 19.05 or newer
REST API
RESTBasicAuth or RESTOAuth2ClientCredentials enabled — see above.
Cover images Optional
A small companion Koha plugin adds the upload route Koha lacks. Not needed if your Koha already gets covers from Amazon or a Coce server.

Accounts Per library

Koha staff account
catalogue to search and view; editcatalogue to create records and copies. The app shows what the account can do after sign-in.
AI provider key
Google Gemini or Anthropic Claude, entered in Settings and kept in the phone's secure keychain.

What it doesn't do

Plainly, so you can decide quickly.

  • It doesn't catalog unattended. Every record passes a review screen.
  • Reading photos needs internet. Offline covers saving, not reading.
  • It doesn't replace Koha. It's a phone app for the Koha you already run.
  • It reads books. The field set covers monographs, not serials or non-print.
  • Photo quality matters. Glare, a curved page or a steep angle costs fields. The app guides each shot and flags photos too small to read.
  • Book photos leave the phone — to the AI provider your library picks. Nothing else does.

What's coming

Being worked on next. No dates we can't keep.

  • Offline shelf reading — a whole shelf session with no network.
  • Bigger shelves — sessions beyond 500 items in one pass.
  • Framework choice — pick the MARC framework new records are filed under.
  • Cleaner imported values — Library of Congress data without stray MARC punctuation in the review form.

Pricing

One subscription per library.

The two plans differ in who pays for the AI and how many phones sign in — never in which features work.

Standard

At launch

Monthly, per library · pricing on request

AI provider key
Your library's own, entered in Settings
Books per month
Unlimited — you pay your AI provider directly
Every feature
Yes
Support
Email

Managed

Coming later

Monthly, per library · pricing on request

AI provider key
Included — no Google or Anthropic account needed
Books per month
Up to a monthly allowance
Every feature
Yes
Support
Email and setup assistance
Annual invoice available — pay yearly against a purchase order. If you stop subscribing, your records stay in your Koha. They were never anywhere else.

Privacy

Your catalog never passes through us.

No CatalogLense server

No accounts to register, no copy of anyone's catalog. The app talks to your Koha directly.

Records stay in your Koha

Credentials are kept in the phone's secure keychain. Catalog and patron data go only to the server address you enter.

Book photos go to your AI provider

Google or Anthropic — whichever you pick. ISBNs and titles go to public book-data services. No analytics, no ads, no tracking.

Read the full privacy policy

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.

What stays on your device

  • Your Koha username and password, or API key, if you use "Remember Me" (iOS Keychain / Android Keystore).
  • AI service API keys you enter (also in the Keychain / Keystore).
  • Your server address, cataloging defaults and barcode settings.
  • Recent cataloging history, records captured offline and their photos, and the correction log.

None of this is sent to us. We cannot read it.

What is sent to your library's Koha server

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.

What is sent to other companies

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.

What we do not do

No analytics, telemetry, crash reporting or advertising. No tracking across apps or websites. No selling or sharing of personal information.

Your rights

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.