The Library Management System Database Web Application is a full-stack web application that manages a library’s core operations. The system provides a web interface that allows users, librarians and administrative staff to interact and perform basic actions (create, read, update, delete) on the database.

The application manages five primary entities, each a key component of the library system:

Books: Stores details about the library’s book inventory, including book ID’s, titles, genres, and ISBN numbers.

Authors: A record of authors, linking them to their corresponding books.

Borrowers: Tracks who borrow books, storing personal and contact information.

Librarians: Manages library staff details, enabling access control and accountability.

Loans: Captures borrowing transactions, including loan dates, due dates, and return dates.

Users can perform the following operations:

Add new records (e.g., registering new books, adding borrowers) View stored data in structured tables Modify existing entries to correct errors or update information Delete obsolete or incorrect records from the database

Overall Structure I built a full-stack web application using a three-layer structure: Frontend → HTML + CSS Backend → Flask (Python) Database → MySQL

Database (MySQL) The database is built using MySQL and it has multiple connected tables, the same as the frontend and backend. Each table stores information related to the library system. Join operations allow the system to combine data from multiple tables, making it possible to view detailed information like loan records with book titles and borrower names.

Relationships Between Tables The database is relational, so the tables are connected. The books table links to authors using author_id The loans table links to:

• books
• borrowers
• librarians

This allows tracking of which user borrowed which book and who processed it.