A full-stack library operations system with 5 core relational models, 2 user role types, a borrowing transaction engine with date-based cost calculation, and a deployment-ready Django stack.
5
Core relational models
2
User role types
Deployed
Gunicorn + WhiteNoise
Problem statement
Library systems need more than a catalog. They require inventory tracking, transaction state management, borrowing cost logic, user roles, and a clean workflow for approvals, returns, and activity history — without the complexity getting in the way of day-to-day use.
Architecture breakdown
I designed Catalog-Point around 5 relational models (profiles, categories, books, costs, transactions) with role-aware views separating librarian administration from member access. The borrowing engine handles date-based cost calculation and debt-aware logic, and the stack is production-configured with Gunicorn and WhiteNoise.
Tech stack explanation
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 Django-based library management system covering the full operational surface of a real library: inventory tracking, category management, borrowing workflows, cost calculation, approval states, return handling, and user activity history — for both librarians and members.
What I learned