As the name suggests, the library management is an application that will help in solving the issues related to the book issue and return. But the maintenance of keeping the records of issuing and borrowing is difficult if you use a normal book as a registry. The students and the faculty will be able to issue the books from the library. If the books are returned late then the fine will also be issued. This library management system will help in keeping track of all these information. The library management system database design will contain the database design of the library management application.
A database is a collection of information or data. A database contains different tables that will have a unique identity. The data will be stored in the form of rows and columns in these tables. The fields that are stored in the tables will be having different data types like integer, varchar, date/time etc. The entity relationship diagram will give logical structure of the database. Model is an approach that is commonly used in the database design. The ER diagram will give the relationships between various entities in the database. Entity is represented as rectangular shape and the relationship is represented in diamond shape. Entity is a thing through which the information is stored. Relationship is the connection between entities. Attributes are the properties of entities. The databases that are included in the library management system are as follows:
- Book details: This database contains the field names like account number, author, title, publication, edition, number of copies, volume price status etc.
- Student: This database contains the field names like name, register number, date of issue, addresses, date of return, course, account number and gender.
- Issue: This database contains the field names like register number, date of issue books, date of return books, account number, name, course, author, volume and edition.
- Return: This database contains the field names like register number, date of issue books, date of return books, account number, name, course, author, volume and edition.
Library Management System Database design:
Database Name: bookdetails
Field Name | Data Type | Size | Relation |
Accno | Varchar | 50 | Primary key |
Author | Varchar | 50 | Not null |
Title | Varchar | 50 | Not null |
Publication | Varchar | 50 | Not null |
Edition | Varchar | 50 | Not null |
No_of_copies | int | Not null | |
Volumn | Varchar | 50 | Not null |
Date_pur | Varchar | 50 | Not null |
Price | Decimal | (18,2) | Not null |
Status | Varchar(50) | 50 | Not null |
Database Name: student
Field Name | Data Type | Size | Relation | ||
Name | Varchar | 50 | Not null | ||
Regno | Varchar | 50 | Primary key | ||
Date_of_issue | Datetime | Not null | |||
Addresss | Varchar | 50 | Not null | ||
Date_of_return | Datetime | Not null | |||
Course | Varchar | 50 | Not null | ||
Accno | Varchar | 50 | Foreign key | ||
Gender | Varchar | 50 | Not null |
Database Name: issue
Field Name | Data Type | Size | Relation |
Regno | Varchar | 50 | Foreign key |
Date_of_issue_books | Datetime | Not null | |
Date_of_return_books | Datetime | Not null | |
Accno | Varchar | 50 | Not Null |
Name | Varchar | 50 | Not null |
Course | Varchar | 50 | Not null |
Author | Varchar | 50 | Not null |
Volumn | Varchar | 50 | Not null |
Edition | Varchar | 50 | Not null |
Database Name: return
Field Name | Data Type | Size | Relation |
Regno | Varchar | 50 | Foreign key |
Accno | Varchar | 50 | Not Null |
Date_of_return_books | Datetime | Not null | |
Date_of_issue_books | Datetime | Not null | |
Name | Varchar | 50 | Not null |
Course | Varchar | 50 | Not null |
Author | Varchar | 50 | Not null |
Volumn | Varchar | 50 | Not null |
Edition | Varchar | 50 | Not null |
Download Database design:
Download Synopsis:
🔥7.9 K Views
0 Comments
Rita Sharma
October 25, 2021 - 7:43 AMIn library management context there is use of accession number in the place of account number.