Library Management System

Overview

The Library Management System is a full-featured academic operations product on the MERN stack: catalogue, members, borrowing, and staff workflows. It treats a library as a set of entities and transactions — titles, copies, borrowers, loans — with a REST API and a React UI.

This is early full-stack work that trained the same muscles later used on Srijaya (inventory and operations) and MediTracker (records and search): model the domain, expose an API, build the staff UI.

Problem

Libraries that run on paper or disconnected spreadsheets lose books and cannot answer “who has this title?” Staff need cataloguing, member records, and a loan lifecycle in one place. Students need search. Admins need both.

What I built

• Book catalogue and inventory (titles and copies)
• Member registration and borrower records
• Loan issue / return workflow
• Search and browse for available titles
• Admin workflows for library staff
• RESTful API (Express / Node) with a React frontend
• MongoDB persistence for catalogue, members, and transactions

Impact

• Complete CRUD and loan lifecycle for a teaching / campus library scenario
• Practice in REST + React + document database that transferred to later products
• A domain model (catalogue / loan / member) that maps cleanly onto other inventory systems

Key features

• Catalogue and stock
• Members and borrowing history
• Search
• Staff admin
• API-backed UI rather than a single PHP page

Technologies

MongoDB stores catalogue and member data. Express.js and Node.js power the API. React delivers the user-facing interface.

My role

Solo academic / personal full-stack build: schema, API, and UI.