Library Management System

The Library Management System supports the day-to-day administration of a physical institutional library. iEncode Tech built it to record both what an institution owns and how those materials move: books and categories at the catalogue level, individual copies at the inventory level, and issue-and-return activity tied to the specific copy involved, keeping catalogue, inventory, and circulation information connected instead of scattered across separate paper registers or spreadsheets. Periodicals are managed as their own distinct record type alongside books, and SMS reminders help staff follow up on due dates without manual tracking, giving library administrators one dependable system for day-to-day collection oversight.

• Book and category records for structured, browsable cataloguing
• Physical-copy inventory tracked separately from title-level records
• Issue and return processes tied to the specific copy involved
• Periodical management as its own distinct record type
• Google-based staff authentication and usage analytics
• SMS notifications for due dates and overdue returns
• Administrative controls for day-to-day collection oversight

The distinction between a book title and an individual physical copy matters in a working library, an institution needs to know not just what it owns in general, but which specific copy is currently issued, returned, or available. The platform was structured to support inventory and circulation records at that level of detail rather than functioning as an e-book reader or digital-content service.

Physical-library administration looks simple until circulation activity is layered on top of a catalogue: a title, its individual copies, and periodicals each need their own record structure without losing the relationships between them. iEncode Tech modelled these as distinct but connected entities, so issue and return activity always references the correct physical copy, and category structures keep the collection browsable without becoming an administrative burden.

• Java and Spring Boot handle application workflows, sharing the same proven backend foundation used across iEncode Tech’s education-sector projects for consistent, maintainable server-side logic.
• MySQL provides structured storage for catalogue, copy, category, periodical, and circulation information, a relational model well suited to the strict links between titles, individual copies, and their issue-and-return history.
• Google APIs support staff authentication and give administrators visibility into system usage through analytics, while Firebase enables notification delivery.
• An SMS gateway sends due-date reminders and overdue notices directly to borrowers, reducing the manual follow-up work library staff would otherwise need to do.
• AWS (EC2, Lambda, S3, Route 53) hosts the application and its infrastructure, giving institutions reliable access to circulation records during working hours.

Built alongside the online examination portal, the system helps educational institutions maintain structured records for physical library resources, giving library staff a reliable, centralised alternative to manual logs. The relational data model keeps titles, copies, categories, and periodicals properly connected, while SMS reminders and AWS-hosted reliability keep the system accurate and available at the level where it actually matters: the individual physical item.