HomeModulesOther ToolsLibrary Management | Titles, Copies, Loans, Holds and Fines
Library Management | Titles, Copies, Loans, Holds and Fines
Other ToolsAuraOdoo Verified

Library Management | Titles, Copies, Loans, Holds and Fines

Run a library on Odoo Community: a catalogue of titles with as many

Technical Specifications & Compatibility

Technical Module Name
Supported Odoo Versions
v19.0
License
Odoo
Deployment Support
Odoo OnlineOdoo.shOn Premise
Lines of Code
1460 lines (Python / XML / JS)

Overview & Description

Odoo 19 Odoo 20 Community and Enterprise OPL-1 Version 19.0.1.0.0 Library Management A catalogue of titles with as many copies as you own, issue and return by barcode, a hold queue that works, borrowing limits and overdue fines. Built around the distinction every naive library system gets wrong: a title is not a copy. A reader wants the book, not barcode 000123. Module Overview What this module solves. Odoo ships no library app There is nowhere in standard Odoo to record a title, a physical copy, a loan, a hold or a fine. This module is a complete lending system, and it depends only on base and mail. A title is not a copy Loans are against a copy, because a specific physical volume left the building. Holds are against a title, because any copy will satisfy the reader. Get this backwards and the queue never works. A returned copy goes to the queue first, the shelf second. Whoever asked first is offered the book, it is held for them for a few days, and if they do not come it passes to the next reader rather than back onto the shelf. Key Features Everything included in the module. The Catalogue Titles with author, ISBN, publisher, year, language, pages and cover As many physical copies per title as you own Barcodes issued automatically from a sequence Shelf location and condition recorded per copy A category tree, searchable down the branch Live per title: on the shelf, out on loan, readers waiting Members Card numbers issued automatically Each reader belongs to a policy, so a second kind of borrower is data Live standing: books out, overdue, fines owed When they cannot borrow, the desk is told which reason it is Suspend, reactivate and close, with holds cancelled on closing A card cannot be closed while books are still out Borrowing Policies Loan period and how many books at once How many renewals are allowed Grace days before a fine starts Fine per day, and a cap it never exceeds The debt level at which borrowing is blocked How long a copy waits on the hold shelf Issuing and Returning The due date comes from the policy the moment a reader is chosen Issue by barcode: one card, one book, one answer Limit, suspension and unpaid fines all checked before it goes out Checked on create, so desk, import and any future kiosk meet the same wall Renew, unless renewals are used up, somebody waits, or it is overdue Lost takes the copy out of circulation and stays on the reader's record The Hold Queue Holds are on the title, so any copy satisfies them A hold on a title with a copy on the shelf is filled at once Queue position is computed from the queue, never stored A held copy cannot be lent to anybody else, and the desk is told who it is for Uncollected after the hold days, it goes to the next reader One live hold per reader per title Fines Grace, then the daily rate, then the cap, in that order A running total while the book is out, frozen when it comes back Outstanding fines are searchable and summable Mark paid, or waive with a reason kept on the record Owing over the threshold blocks borrowing; paying unblocks it A daily job leaves a note on overdue loans, not an email Business Benefits Why it matters day to day. A Fair Queue Whoever asked first gets the copy that comes back, held for them and then passed on. No reader is quietly skipped. A Fast Desk Issue by barcode is one card, one book, one answer, with every rule checked before the book leaves the counter. Stock You Can Trust Copies are tracked individually and can be marked lost or withdrawn without deleting their history, so nothing vanishes silently. Rules Without Code Staff, students and the public are three policies, not three customisations. Change a limit and the whole class follows. Screenshots A tour of the interface. Catalogue Of Titles Screenshot Placeholder Titles with cover, category and live copy availability. Issue By Barcode Screenshot Placeholder The desk view: scan a card, scan a book, get an answer. The Hold Queue Screenshot Placeholder Readers waiting on a title, in order, with ready holds flagged. Member Standing Screenshot Placeholder Books out, overdue items, fines owed and whether they can borrow. Workflow From an empty catalogue to a working desk. Build the catalogue. Add titles with their bibliographic details, then a copy for each physical volume. Barcodes are issued for you. Set the policies. A Standard policy ships with the module. Add others if staff, students and the public borrow on different terms. Register readers. Card numbers are issued automatically. Each reader is attached to a policy, which decides their limits. Issue. Scan the card and the barcode. The due date appears from the policy, and limits, suspensions and fines are checked before the book leaves. Take holds. A reader asks for a title. If a copy is on the shelf the hold is filled at once; otherwise they join the queue. Return, renew and collect fines. A returned copy goes to the front of the queue if anybody is waiting. Overdue fines accrue after the grace period and stop at the cap. What Happens To A Returned Copy Situation Where the copy goes Nobody waiting Back on the shelf, available to anyone Readers in the queue Onto the hold shelf for whoever asked first Held reader collects it Issued to them, and the hold is marked collected Held reader does not come Offered to the next reader, not back to the shelf Held reader cancels Passed on the same way, to the next in line Returned damaged or lost Out of circulation, with its history intact Configuration Menus, roles, policies and jobs. Menu Structure Menu Purpose Desk, then Loans Issue, return, renew and mark lost Desk, then Overdue Everything out past its due date Desk, then Holds The queue, and copies waiting on the hold shelf Catalogue, then Titles and Copies The bibliographic records and the physical stock Members Readers, their cards and their standing Configuration Borrowing policies and catalogue categories User Roles Action Desk Librarian Issue, return, renew, take holds Yes Yes Register readers Yes Yes Edit the catalogue No Yes Change a policy No Yes Waive a fine, withdraw stock No Yes Scheduled Jobs Job Runs What it does Library: expire uncollected holds Daily Passes a copy nobody collected to the next reader in the queue Library: note overdue loans Daily Leaves a chatter note on every loan that is past its due date Nothing is emailed to readers automatically. The overdue job leaves a note on the record. A module that starts mailing your readers the day it is installed is a module that gets uninstalled, so notification is left to you. Technical Details Models, dependencies and design. Module Information Technical Name library_management_aura Version 19.0.1.0.0 Category Services / Library License OPL-1 Dependencies base, mail External Libraries None beyond a standard Odoo installation External Service None. Everything runs inside your own Odoo instance. Automated Tests 57 unit tests and a browser tour Models Model Description library.book A title, with its bibliographic details library.book.category The catalogue category tree library.copy A physical volume, with barcode and condition library.member A reader, their card and their standing library.policy Borrowing terms: periods, limits and fines library.loan A copy out with a reader, with the fine on it library.reservation A hold on a title, and its place in the queue Design Notes Loans on copies, holds on titles. The one distinction the whole module turns on, and the reason the queue can be satisfied by whichever copy comes back first. Queue position is computed. Never stored, so it cannot go stale, and tie-broken by record id so holds placed in the same second still order deterministically. Rules are enforced on create. Not in the button, so the desk, a data import and any future self-service kiosk all meet the same wall. Policies are data. A second class of borrower is a new record, not a new branch in the code. History is never deleted. A copy can be marked lost or withdrawn, but its loans and its chatter stay, so the question of where a book went can still be answered years later. Compatibility Where the module runs. Item Supported Odoo Version 19.0 Current Hosting Odoo.sh, On-Premise and any self-managed deployment Multi-Company Yes, with record rules on titles, members and loans Multi-Currency Yes, fines follow the company currency Multi-Language Yes, all labels and messages are translatable Mobile and Tablet Yes, standard responsive Odoo web client Barcode Scanners Yes, any keyboard-wedge scanner works at the desk Supported Editions Both editions, one code base. Community Edition Supported The edition this module was written for. It depends only on base and mail, so it runs on the leanest installation. Enterprise Edition Supported Runs unchanged on Enterprise, alongside the standard apps and with no conflicting models. Odoo.sh Supported No extra Python packages to install, so it deploys with no change to your build configuration. Installation Four steps to an open library. Copy the module. Place the library_management_aura folder in your Odoo addons path. Update the apps list. Activate developer mode, then choose Apps and Update Apps List. Install Library Management. Search for it in Apps and install. Only base and mail are required. Assign the roles. Give counter staff Desk and give cataloguers Librarian, then start adding titles. A Standard borrowing policy is installed with the module, so a member form is never faced with an empty required field on the very first day. Frequently Asked Questions The questions asked most often. A title is the book as a work; a copy is one physical volume on your shelves, with its own barcode, shelf location and condition. Loans are against a copy because a specific volume left the building. Holds are against a title because any copy will do. Whoever asked first. The returned copy goes onto the hold shelf for them rather than back into general circulation, and it cannot be lent to anybody else meanwhile. If they do not collect it within the hold period it is offered to the next reader, not returned to the shelf. Yes. Create a policy for each and attach readers to it. Loan period, how many books at once, renewals, grace days, fine rate, fine cap, the blocking threshold and the hold shelf period are all per policy, so a new class of borrower is data rather than a customisation. Grace first, then the daily rate, then the cap, in that order. The total runs while the book is out and freezes when it comes back, so it never keeps climbing after a return. Fines can be paid or waived with a reason that stays on the record. When the reader has used up the renewals their policy allows, when somebody else is waiting for the title, or when the loan is already overdue. The desk is told which of the three it is. Yes. Issuing by barcode takes a card number and a copy barcode and gives one answer, which is exactly what a keyboard-wedge scanner at the desk produces. Copy barcodes are issued automatically from a sequence, so you can print your own labels. Not by default. The daily job leaves a note on the loan rather than sending mail, because a module that starts emailing your readers on the day it is installed is one nobody keeps. The notes are there to build a reminder on when you are ready. Mark the copy lost or withdrawn rather than deleting it. It leaves circulation but keeps its loan history and its chatter. A copy that is currently on loan cannot be withdrawn behind the reader's back. Changelog Release history. Version 19.0.1.0.0 Initial Release Catalogue of titles with a searchable category tree Multiple copies per title, each with an automatic barcode Members with card numbers and live borrowing standing Borrowing policies covering periods, limits, fines and hold shelf Issue and return, including issue by barcode for a desk scanner Limits, suspensions and unpaid fines enforced on create Renewals, with the three refusal reasons reported to the desk Hold queue on titles with computed, deterministic ordering Returned copies routed to the queue before the shelf Uncollected and cancelled holds passed to the next reader Fines with grace, daily rate and cap, payable or waivable Desk and Librarian roles with multi-company record rules Two daily jobs for expired holds and overdue notes 57 unit tests and a browser tour Support We answer, and we keep our modules current. Email odooaura@gmail.com Website www.auraodoo.tech YouTube youtube.com/@Auraodoo Free support for bug fixes on the Odoo version you downloaded. Customisation and installation help available on request. Aura Odoo Tech Odoo modules built to be understood, not just installed. Odoo 19 OPL-1 library_management_aura www.auraodoo.tech | odooaura@gmail.com | youtube.com/@Auraodoo

Key Capabilities & Features

  • Titles with author, ISBN, publisher, year, language, pages and cover
  • As many physical copies per title as you own
  • Barcodes issued automatically from a sequence
  • Shelf location and condition recorded per copy
  • A category tree, searchable down the branch
  • Live per title: on the shelf, out on loan, readers waiting
  • Card numbers issued automatically
  • Each reader belongs to a policy, so a second kind of borrower is data
  • Live standing: books out, overdue, fines owed
  • When they cannot borrow, the desk is told which reason it is
  • Suspend, reactivate and close, with holds cancelled on closing
  • A card cannot be closed while books are still out
  • Loan period and how many books at once
  • How many renewals are allowed
  • Grace days before a fine starts
  • Fine per day, and a cap it never exceeds
  • The debt level at which borrowing is blocked
  • How long a copy waits on the hold shelf
  • The due date comes from the policy the moment a reader is chosen
  • Issue by barcode: one card, one book, one answer
  • Limit, suspension and unpaid fines all checked before it goes out
  • Checked on create, so desk, import and any future kiosk meet the same wall
  • Renew, unless renewals are used up, somebody waits, or it is overdue
  • Lost takes the copy out of circulation and stays on the reader's record
  • Holds are on the title, so any copy satisfies them
  • A hold on a title with a copy on the shelf is filled at once
  • Queue position is computed from the queue, never stored
  • A held copy cannot be lent to anybody else, and the desk is told who it is for
  • Uncollected after the hold days, it goes to the next reader
  • One live hold per reader per title
  • Grace, then the daily rate, then the cap, in that order
  • A running total while the book is out, frozen when it comes back
  • Outstanding fines are searchable and summable
  • Mark paid, or waive with a reason kept on the record
  • Owing over the threshold blocks borrowing; paying unblocks it
  • A daily job leaves a note on overdue loans, not an email
  • Build the catalogue. Add titles with their bibliographic details, then a copy for each physical volume. Barcodes are issued for you.
  • Set the policies. A Standard policy ships with the module. Add others if staff, students and the public borrow on different terms.
  • Register readers. Card numbers are issued automatically. Each reader is attached to a policy, which decides their limits.
  • Issue. Scan the card and the barcode. The due date appears from the policy, and limits, suspensions and fines are checked before the book leaves.
  • Take holds. A reader asks for a title. If a copy is on the shelf the hold is filled at once; otherwise they join the queue.
  • Return, renew and collect fines. A returned copy goes to the front of the queue if anybody is waiting. Overdue fines accrue after the grace period and stop at the cap.
  • Loans on copies, holds on titles. The one distinction the whole module turns on, and the reason the queue can be satisfied by whichever copy comes back first.
  • Queue position is computed. Never stored, so it cannot go stale, and tie-broken by record id so holds placed in the same second still order deterministically.
  • Rules are enforced on create. Not in the button, so the desk, a data import and any future self-service kiosk all meet the same wall.
  • Policies are data. A second class of borrower is a new record, not a new branch in the code.
  • Copy the module. Place the library_management_aura folder in your Odoo addons path.
  • Update the apps list. Activate developer mode, then choose Apps and Update Apps List.
  • Install Library Management. Search for it in Apps and install. Only base and mail are required.
  • Assign the roles. Give counter staff Desk and give cataloguers Librarian, then start adding titles.
  • Catalogue of titles with a searchable category tree
  • Multiple copies per title, each with an automatic barcode
  • Members with card numbers and live borrowing standing
  • Borrowing policies covering periods, limits, fines and hold shelf
  • Issue and return, including issue by barcode for a desk scanner
  • Limits, suspensions and unpaid fines enforced on create
  • Renewals, with the three refusal reasons reported to the desk
  • Hold queue on titles with computed, deterministic ordering
  • Returned copies routed to the queue before the shelf
  • Uncollected and cancelled holds passed to the next reader
  • Fines with grace, daily rate and cap, payable or waivable
  • Desk and Librarian roles with multi-company record rules
  • Two daily jobs for expired holds and overdue notes
  • 57 unit tests and a browser tour
  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.

Screenshots & Previews

1 image available
Library Management | Titles, Copies, Loans, Holds and Fines screenshot 1
Expand Preview
The AuraOdoo Quality Guarantee
100% Tested

Verified with Odoo 17, 18, and 19 test pipelines for stability and no conflicts.

Clean Architecture

Built according to official Odoo guidelines and PEP 8 standards with zero bloat.

Dedicated Support

Free installation assistance and quick bug turnaround from our team.