Choose library inventory software by keeping title information, physical copies and loans distinct. Assess how a copy is identified, who may edit its catalogue data and what happens when it is issued, returned or unavailable. A useful demonstration should follow the same copy through those decisions, rather than show only a searchable list of books.
How does a title differ from a copy?
Koha’s bibliographic record holds information such as title, author and ISBN. Koha allows item records to be attached to a saved bibliographic record. The Koha catalogue management manual provides a concrete model for separating shared descriptive information from records associated with the material.
For a hypothetical library, create a synthetic title called Test Atlas with two synthetic copy records. Decide how a staff member distinguishes the copies during a loan and a later count. Keep the shared title description separate from the identifier used for the particular copy being handled.
Ask what the institution needs to record about each copy: its location, condition and intended circulation treatment, for example. Treat these as requirements to assess in the chosen product. A title-level search result alone does not establish which physical copy is available for a patron.
Identify the catalogue owner who can resolve a duplicate or uncertain description. A neat display should not conceal that two records may refer to the same material or that a physical copy has not been matched confidently.
Who controls catalogue quality?
Koha requires bibliographic frameworks to be prepared before work in the catalogue management module. Include framework decisions in the implementation record. Ask which fields are needed for the library’s material and who can change their meaning or requirement level.
Koha distinguishes mandatory fields that block saving from important fields that only warn. Propose a synthetic record with one required field missing and another with an optional warning. Record the actual response of the configured framework. This helps distinguish a control that prevents incomplete saving from information that merely invites a reviewer to check it.
Koha’s basic duplicate check uses ISBN, or a title-and-author combination when ISBN is absent. Include a possible-duplicate case in the evaluation and ask the catalogue owner to explain the decision. Keep the original identifiers and reason for merging, retaining or correcting a record available to the next reviewer.
Avoid filling uncertain fields with plausible values simply to complete the demonstration. Give the uncertainty an owner and identify the evidence needed. Catalogue quality depends on the meaning of the record as well as whether the application accepts it.
How should a loan identify the right patron and copy?
Koha’s checkout process starts by identifying a patron through barcode or name search. Koha’s checkout screen provides an item-barcode entry or scan field. Use the Koha circulation manual to trace the documented checkout sequence in a controlled environment.
For Test Atlas, propose a loan to a synthetic patron called Test Reader. Ask the evaluator to record which patron was selected, which copy was entered and which loan result the application displayed. Keep the intended outcome and the observation separate until the exercise is performed.
If a search returns several plausible patrons or the copy identifier is unclear, define the staff procedure for resolving the ambiguity. Do not treat a matching name as enough evidence to proceed with a real patron’s loan.
Koha circulation functions require the relevant circulate permission or superlibrarian permission. Establish the actual operator roles and assess them through authorised test accounts. The library should be able to explain who may issue material, who may edit catalogue data and which exceptional decisions require a different owner.
How should due dates and renewal exceptions work?
A manually specified due date is available only when the relevant Koha preference permits an override. Ask the circulation owner to define the rule and the authority needed for an exception. The software setting should reflect that decision rather than become an unexplained route around it.
Koha’s documented automatic renewals depend on both a scheduled job and circulation rules. Include the relevant configuration and operating dependency in the handover. A feature described in documentation still needs evidence that the proposed environment is set up for the intended behaviour.
Choose a controlled renewal case that exposes the rules important to the library. Ask what happens when a copy is needed by another patron or when the ordinary renewal route cannot proceed. Obtain the actual configured result instead of assuming the application grants every requested extension.
Keep a renewal request, an accepted renewal and a denied renewal distinguishable in the review record. The patron-facing explanation should match the library’s decision and tell the operator what to do next when further action is needed.
Which copy-level cases belong in the evaluation?
Use this original title-to-copy-to-loan matrix for the synthetic collection. It links the catalogue decision to the circulation evidence a reviewer needs.
| Case | Record to inspect | Question for the library owner |
|---|---|---|
| Two copies of one title | Bibliographic record and linked items | Can staff identify the particular copy? |
| Possible duplicate title | Identifiers and catalogue-owner decision | Is the duplication resolved with evidence? |
| Required data missing | Framework configuration and actual save response | Does the control match the intended rule? |
| Loan to a synthetic patron | Patron selection, item reference and result | Is the correct copy associated with the right record? |
| Due-date exception | Applicable preference and authorised role | Who may make the exception and why? |
| Renewal cannot proceed | Relevant circulation rule and observed response | What should the operator communicate or investigate? |
| Copy not found at count | Copy identity, location and circulation evidence | Is the absence explained or still unresolved? |
For the count case, ask the reviewer to inspect the loan and location information before deciding that a copy is missing. Keep an unexplained absence distinct from a copy whose current disposition is supported by the records.
Use a short handover exercise: another staff member should be able to start from the synthetic copy identifier, find its title information and explain the recorded loan outcome. Record any step that needs undocumented help and improve the procedure before accepting it.
What should the selection decision retain?
Keep the material types, title/copy model, catalogue controls and circulation rules together with the completed evaluation matrix. Identify unresolved import, role or exception questions and the person who can answer each one.
For the wider systems scope, see web development and business email. Discuss your requirements with Spout using a representative title, copies and the loan decisions your institution needs to support.
By Spout Team. AI-assisted drafting by Codex using the linked primary documentation.