AI for the Koha Side
AI isn’t only for our patrons – librarians can reap the benefits, too!
Learn how to integrate AI into your workflow and make AI work for you.
Practical AI for Everyday Library Work
AI Basics – ground rules
Working with AI responsibly: it’s auto-complete, not a mind. It can gather information and do some fact-checking (not always reliable). It can design; it can’t create.
Rule #1: PRIVACY
Never put patron PII (Personally Identifiable Information), patron circulation history, or financial spreadsheets into free public AI tools. Ask about an enterprise or locally-hosted account – data stays inside your organization.
Rule #2: REVIEW
Trust, but verify. Watch for hallucinations.
Run the CRAAP test: Currency, Relevance, Authority, Accuracy, Purpose. Start with low-stakes tasks – see if it actually saves time, then scale up your work.
A tale of cheese…
Think of AI as a passionate, occasionally unreliable digital intern: fast, enthusiastic, and sometimes confidently wrong. You are the one who can and should decide what is in the end result.
Where Do I Start?
Public/Free Tools
Enterprise / Local Accounts
Most common AI tools available:
ChatGPT (OpenAI) | Claude (Anthropic) | Gemini (Google) | Perplxity.ai
Variables to consider:
Treat it like a reference interview: tell AI who you are and how you want to be helped.
Context
The situation or background
Role
Who AI should act as
Objective
What AI should do
Process
How it should think or work
Grounding
The data or evidence to use
Format
The shape of the output
Writing a Good Prompt
“We are a public library with 13 branches and a bookmobile. We want to send Notices using the Koha ILS version 25.11.06 to borrowers with overdue books via email. Please create HTML for a Notice design that is friendly, concise, includes our library logo…”
REMEMBER: AI IS AN ASSISTANT – NOT A REPLACEMENT. Trust, but Verify.
https://koha-community.org/manual/latest/en/html/index.html
https://koha-community.org/documentation/
AI for Cataloging
Problem: As librarians and data specialists, WE often provide the data that AI uses to give other people answers!! We can see if others have provided this information before us (WorldCat, z39.50, etc.), but often we are the ones doing the work, book by book.
SO HOW CAN AI HELP ME CATALOG?
Importing - If you want to stick to putting in your own data, but still want a faster cataloging option, you can create and import batches of records.
AI for Quicker Work
Circulation and other statistics – make them fun and presentable to your stakeholders. Ask for help explaining them in an impactful way.
Use those same practices when writing Policy and Grant Templates
Cleanup - Export files into .mrc or other files.
Find the problems and clean them up. Even ask how to clean them!
Cataloging FOR you??
Several companies are now working on creating AI programs that will catalog FOR us. Ex-Libris, MarcAI, and OCLC are some of them.
AI for Reports
Create SQL reports using plain language:
Use AI as a teacher for learning SQL. Have it walk you through each part of the report it creates explaining schema, data tables, etc.
You can also start building reports on your own and having AI check them for you and explain what may need to be fixed.
Fix or amend reports already created:
AI for Internal Design
AI can be your very excited helper, and now your friendly IT expert! Let it mentor you in your quest for independence.
Autofill a Marc field or subfield with a given value when I click in that field
Show the Biblionumber in the Orders table.
Remember that AI can find all the documentation it needs for Koha online. (Aspen too!)
Use AI to help you design and customize your sites using jQuery, CSS, and more.
A great use of AI is for Acquisitions and Collection analysis
(Claude, Gemini seem to work well for these)
AI for Analysis
You can also paste any report results into your AI tool and ask what it tells you about trends: circulation, acquisitions, collection imbalances, etc.
Type a natural-language prompt into your AI SQL assistant tool:
Have AI review your Acquisitions invoice analysis for subscriptions.
Review a packing list vs order list in Koha: what's missing?
AI for Staff Who Serve
Consultant:
Intern for the dirty work:
Design:
Automatically cross-references new book acquisitions with local school standards to draft reading lists.
AI for Direct Patron Help
Design a chatbot for common questions with answers based on the information from your library’s website.
Universities require students to participate in a self-guided tour to get to know the library: use AI to build this tour activity.
Create reader’s advisory lists, or design a tool that can generate them.
Design a feedback system, then use AI to analyze that feedback.
Ask for ideas on how to serve certain populations better: those from out of town, those who do not have English as a first language, those with specific disabilities, etc.
Create instructions for the printer, computers, and other equipment with clarity and brevity. Have it include pictures and icons.
Gather Summer Reading Program ideas for each specific age group/grade.
Cross reference circ, pub date, condition notes to flag candidates for weeding.
Analyze hold queues, ILL requests, and purchase suggestions to recommend titles/genres to purchase.
AI for Reference Help
The FEAR: Reference questions that may stump the best of us!
In one of Jane Austen’s books she talks about a book that was really published. What is the title of that book?
There’s a book that was published in the last 10 years or so that was an animal version of Shakespeare’s Hamlet. What book is it?
I want to know the copyright on a book. Its title is "Chautauqua County: A History" by Helen G. McMahon, and it was first published in 1958. Is it still in copyright?
Where is the deadliest volcano on Earth right now? Can I go there? What books will tell me more about them?
The Future of AI for Koha
KohaCon classes about integrating AI - check them out!
The next questions are:
Where do we go from here?
What do we want to see in Koha that AI can do?
How can AI be integrated directly into Koha and our regular processes?
My personal ideas / wish list for our library processes:
If an ISBN or OCLC number has been entered in the record, have a button with the 520 field that will find the summary for that item and import it in.
If the language of the catalog is set to English (or other language), and a foreign language title is detected in the 245$a field, have a button in the 242$a field to generate the English translation, and a button in the 246$a field for a transliteration of the title.
If the 542 field contains information related to the copyright status of a work. Based on U.S. Copyright laws, find and generate the copyright status of a book in this field.
Questions?