Library Management System

Catalog-Point

Built a full-stack library operations platform that manages inventory, borrowing workflows, member activity, and librarian approvals in one Django-based system.

Problem statement

Library systems need more than a simple catalog. They require inventory tracking, category organization, transaction state management, borrowing cost logic, user roles, and a clean workflow for approvals, returns, and user activity history.

Architecture breakdown

I designed Catalog-Point as a structured Django application with a dedicated library app, relational models for books, categories, profiles, costs, and transactions, plus role-aware views for librarians and members. The platform combines server-rendered templates, transactional workflows, profile management, and deployment-ready configuration for a full operations-focused system.

- Relational model design covering profiles, categories, books, costs, and transactions
- Role-based workflows for librarians and members with approval and return handling
- Borrowing engine with date-based cost calculation and debt-aware transaction logic
- Deployment-oriented Django setup with Gunicorn, WhiteNoise, and environment-driven infrastructure support

Tech stack explanation

DjangoPythonPostgreSQLHTMLCSSJavaScriptDjango AllauthGunicorn

System diagram

[ Members / Librarians ]
      |
      v
[ Django Views + Templates ]
      |
      +--> [ Book Catalog ]
      +--> [ Category Management ]
      +--> [ Borrow / Return Transactions ]
      +--> [ Profiles + Authentication ]
      |
      v
[ PostgreSQL Data Model ]

Key challenges

Catalog-Point is a comprehensive library management system built with Django for handling book inventory, user profiles, borrowing transactions, and day-to-day library workflows. It supports both librarian and member experiences, combining operational administration with searchable catalog access and transaction tracking.

- Created a practical operations system instead of a catalog-only demo.
- Showed strength in Django application structure, relational modeling, and workflow-heavy backend design.
- Demonstrated product thinking around administrative tooling and user-facing library interactions.

What I learned

Workflow-heavy CRUD systems become far more valuable when the transaction states are designed carefully.

Django remains strong for admin-oriented products where relational clarity and delivery speed both matter.

User roles shape interface and backend design just as much as the database schema does.

[ Members / Librarians ] | v [ Django Views + Templates ] | +--> [ Book Catalog ] +--> [ Category Management ] +--> [ Borrow / Return Transactions ] +--> [ Profiles + Authentication ] | v [ PostgreSQL Data Model ]