DESIGN DOCUMENT: LIBRARY DATABASE SYSTEM

ABSTRACT:-

The project is based on the library database system pertaining to

various need of the user. The basic interface involves querying books

according to language, title, authors, publishers.

We support service for issuing and summiting book in library as well as

getting all information about due dates, due fines and due book about

a student used in specific ABV IITM Gwalior. We build a personal profile

page which is used for checking updates and all information about the

student who get book from library.

OUTLINE :-

1. Information regarding the book: Set of entities that support the

store of the books, author ,publication and general search

queries for their availability in the library. Advanced search

queries are also provided.

2. Information about issuing/submitting : Set of entities that

support personal profiles of the students.it also handles

notification to be send to the book Librarian and Student about

their due dates, completion of the due dates and about due fines.
 3. Information regarding course : information about the course and

recommended book for that course at ABV IIITM G, which in turn

are searched directly in library and result are provided to the

library.

QUERIES AND FUNCTIONALITY:

1. The students can issue the book without logging in, however in

order to issue / Submit books they need to log in with a user

name and password and user name can be used as key for

students.

2. A log id for a particular students is created by the admin of the

library database system.

3. On logging in, the system moves to personal profile page

which will show notification regarding the current books

issued and submitted by the users. The pages will hold

personal information and various option available to the users.

4. Various queries that can be taken by the users:

(a) General search for a book:

  The user can search for book in library section.

 According to library tables would be used for the

search.

 Option such as languages, titles , authors, publishers,

ISBN, publication dates are available.

 We provide features of the portal search of a phrase

or exact world on the phrase.

(b) Add a book in database:

 The person specifies complete information regarding

the book along with the information about the

authors and publication details.

 If the book is not present in the book tables ,the book

tables is updated with the entry.

 If the author of the particular book is not present, the

corresponding entry are added.

(c) Issuing a book :

 A drop down menu that can issued to the students

(d) Storing search Results:

 We provide the option of the user returning to a

particular search results which it has last carried out.

(e) Notification:

 If any time any book is issued a student then their

profile get a notification about the activity.

 titles Copies
Addresses
Book_id
Pub_id

prices Name

Author
s

BOOKS Published PUBLISHERS

by

N 1

DOB

Issue

Issue
Students

Due Date

Students_ID
Student_Name Address

Return
Date
 TABLES
1.PUBLISHER(Pub_ID,Pub_Add,Pub_Name,Pub_Email)
2.BOOKS (Book _ID,Book_Titles,Pub_Date,Pub_ID,Author,Copies)
3.Students(Student_ID,Students_Name,Students_ADD,Student_email,DOB)

Functional Dependencies
(pub_ID) (Pub-Add,Pub_Name,Pub_Email)

(Book_ID) (Book_Titles,Pub_date,Pub_ID,Authors,Copies)

(Students_ID) (Student_Name,Student_Add,Student_Email,Bod)

NORMALIZATION
Publisher Table
Pub_ID Pub_Name Pub_Email Pub_Add
123 Evergreen [email protected] Delhi,Gwalior,Patna
142 TMH [email protected] Kolkata,Asansol,Ranchi
Since it violates 1st normalization rules.
After 1st normalization
Pub_ID Pub_Name Pub_Email Pub_Add
123 Evergreen [email protected] Delhi
123 Evergreen [email protected] Gwalior
123 Evergreen [email protected] Patna
142 TMH [email protected] Kolkata
142 TMH [email protected] Asansol
142 TMH [email protected] Ranchi

Since there is only one primary key so it is already in 2nd

normalization form.
And since all the attributes are functionally dependent on only on
primary key so the above table is also in 3rd normalization form.

After 4th Normalization

Pub_ID Pub_Name Pub_Email
123 Evergreen [email protected]
142 TMH [email protected]

Pub_ID Pub_Add
123 Delhi
123 Gwalior
123 Patna
142 kolkata
 142 Asansol
142 Ranchi

BOOK
Book_ID Book_title Book_author Copies_ID Pub_ID Pub_Date
123 CN Andrew,Bau 101,102 123 28/04/98

It is not in the 1st normalization form because its attributes are not in
atomic.
Book_ID Book_Titles Book Copies_ID Pub_ID Pub_Date
_author
123 CN Andrew 101 123 28/04/98
123 CN Bau 101 123 28/04/98
123 CN Andrew 102 123 28/04/98
123 CN Bau 102 123 28/04/98

Since there is only one primary key and all the attributes are
dependent on that primary key so it is already in 2nd normalization
form.
And because all the attributes are directly dependent on primary key
and not on other columns.
After fourth normalization
In fourth normalization we see whether the table has multivalued or
not, it is having multivalued attributes therefore new table would be

BOOK
Book_ID Book_Table Pub_ID Pub_Date
123 CN 123 28/04/98
123 CN 123 28/04/98
123 CN 123 28/04/98
123 CN 123 28/04/98

AUTHOR
Author_ID Author_Name Author_Email
150 Andrew [email protected]
151 Bau [email protected]

COPIES
Copies_ID Book_ID
101 123
102 123

Since BOOK table and AUTHOR table are many to many relation so
we can make separate tables.
Book_ID Author_ID
123 150
123 151
ISSUE
Issue_ID Due_Date Issue_Date Return_Date
201 30/04/2016 15/04/2016 29/04/2016
202 10/04/2016 25/03/2016 09/04/2016

STUDENT

Student_ID Student_Name Student_Email Issued_ID Student_Dob

1997 Ajay [email protected] 501 01/01/1997
1997 Ajay [email protected] 501 01/01/1997
1999 Vijay [email protected] 506 08/04/1996
1999 vijay vijay@gmail 506 08/04/1996

Student_ID Student_Name Student_Email Student_DOB

1997 Ajay [email protected] 01/01/1997
1999 vijay [email protected] 01/01/1997

Student_ID Issued_ID
1997 501
1999 506