Library Management System | ENGLISH LINGUISTICS AND LITERATURE (K40) | Đại học Khoa học Xã hội và Nhân văn, Đại học Quốc gia Thành phố HCM

The Library Management System is an essential component of the English Linguistics and Literature program at Ho Chi Minh City University of Social Sciences and Humanities. This system serves as a centralized platform for organizing, cataloging, and accessing a wide range of literary resources, including books, journals, and digital materials. Through this system, students can efficiently search for and borrow materials, facilitating their research and academic pursuits. Additionally, the Library Management System plays a crucial role in promoting a culture of reading and lifelong learning among students and faculty members alike.

lOMoARcPSD| 40190299
Library Management System
ENGLISH LINGUISTICS AND LITERATURE (Đại hc Khoa hc Xã hội và Nhân văn,
Đại hc Quc gia Thành ph H Chí Minh)
lOMoARcPSD| 40190299
LIBRARY MANAGEMENT SYSTEM
The Library Management System database keeps track of readers with the following
considerations;
The system keeps track of the staff with a single point authentication system
comprising login Id and password.
STAFF maintains the book catalog with its ISBN, Book title, price, category (novel,
general, story), edition, author Number and details.
A PUBLISHER has publisher Id, Year when the book was published, and name of
the book.
READERS are registered with their user_id, email, name (first name, last name),
Phone no (multiple entries allowed), communication address. The staff keeps track of
readers.
READERS can return/reserve books that stamps with issue date and return date. If
not returned within the prescribed time period, it may have a due date too.
STAFF also generate reports that has readers id, registration no of report, book no
and return/issue info.
Entities and their Attributes
Book Entity: It has authno, isbn number, title, edition, category, price. ISBN is the
Primary Key for Book Entity.
Reader Entity: It has UserId, Email, address, phone no, name. Name is composite
attribute of firstname and lastname. Phone no is multi valued attribute. UserId is the
Primary Key for Readers entity.
Publisher Entity: It has PublisherId, Year of publication, name. PublisherID is the
Primary Key.
Authentication System Entity: It has LoginId and password with LoginID as
Primary Key.
Reports Entity: It has UserId, Reg_no, Book_no, Issue/Return date. Reg_no is the
Primary Key of reports entity.
Staff Entity: It has name and staff_id with staff_id as Primary Key.
lOMoARcPSD| 40190299
Question 1, 2 and 3 Answer
ENTITY
ATTRIBUTES
DATATYPE
Book
Authno
varchar (20)
ISBN
varchar (13)
title
varchar (50)
edition
varchar (20)
category
varchar (30)
price
Double (18,2)
Reader
UserId
varchar (20)
Email
Varchar (50)
Address
Varchar (20)
Phone_no
varchar (20)
Firstname
varchar (30)
Lastname
varchar (30)
Publisher
PublisherId
varchar (10)
YearofPublication
Datetime
Name
varchar (50)
Authentication_System
LoginId
varchar (20)
Password
varchar (20)
Report
UserId
Varchar (20)
Reg_no
varchar (10)
Book_no
int
Issue/Return
Datetime
Staff
Name
varchar (30)
staff_id
varchar (20)
Reserve/Return Relationship Set: It has three attributes: Reserve date, Due date,
Return date.
Question 4 Answer
THE SCHEMA DIAGRAM
Let FK = Foreign Key and PK = Primary Key
BOOK
Price
Category
Edition
ISBN(PK)
Title
READER
UserId(PK
Email
firstNam lastName Address
)
e
lOMoARcPSD| 40190299
PUBLISHER
Publisher_Id(PK YearofPublication
Name
)
PHONE NUMBER
UserId(FK
Phone#
)
AUTHENTICATION SYSTEM
LoginId (PK)
Passwor
d
STAFF
Name Staff_Id(PK)
REPORTS
UserId(FK Reg_no(PK Book_no
Issue/Return_dat
)
)
e
Question 5 Answer
This Library ER diagram illustrates key information about the Library, including
entities such as staff, readers, books, publishers, reports, and authentication system.
It allows for understanding the relationships between entities.
ENTIY RELATIONSHIP SCHEMA DIAGRAM
lOMoARcPSD| 40190299
Relationships between Entities
A reader can reserve N books but many books can be reserved by only one reader.
The relationship 1:N.
A publisher can publish many books but a book is published by only one publisher.
The relationship 1:N.
Staff keeps track of readers. The relationship is M:N.
Staff maintains multiple reports. The relationship 1:N.
Staff maintains multiple Books. The relationship 1:N.
Authentication system provides login to multiple staffs. The relation is 1:N
lOMoARcPSD| 40190299
THE SCHEMA RELATIONAL DIAGRAM
Let FK = Foreign Key and PK = Primary Key
BOOK
Price
Category
Edition
Authno
ISBN(PK)
Title
READER
UserId(PK
Email
firstNam lastName Address
)
e
PUBLISHER
Publisher_Id(PK YearofPub Name ISBN(FK)
) lication
PHONE NUMBER
UserId(FK)
Phone#
AUTHENTICATION SYSTEM
LoginId (PK)
Passwor
d
STAFF
Name Staff_Id(PK)
REPORTS
UserId(FK
Reg_no(PK Book_no
Issue/Return_dat
)
)
e
| 1/6

Preview text:

lOMoAR cPSD| 40190299 Library Management System
ENGLISH LINGUISTICS AND LITERATURE (Đại học Khoa học Xã hội và Nhân văn,
Đại học Quốc gia Thành phố Hồ Chí Minh) lOMoAR cPSD| 40190299
LIBRARY MANAGEMENT SYSTEM
The Library Management System database keeps track of readers with the following considerations;
The system keeps track of the staff with a single point authentication system
comprising login Id and password.
STAFF maintains the book catalog with its ISBN, Book title, price, category (novel,
general, story), edition, author Number and details.
A PUBLISHER has publisher Id, Year when the book was published, and name of the book.
READERS are registered with their user_id, email, name (first name, last name),
Phone no (multiple entries allowed), communication address. The staff keeps track of readers.
READERS can return/reserve books that stamps with issue date and return date. If
not returned within the prescribed time period, it may have a due date too.
STAFF also generate reports that has readers id, registration no of report, book no and return/issue info.
Entities and their Attributes
Book Entity: It has authno, isbn number, title, edition, category, price. ISBN is the Primary Key for Book Entity.
Reader Entity: It has UserId, Email, address, phone no, name. Name is composite
attribute of firstname and lastname. Phone no is multi valued attribute. UserId is the
Primary Key for Readers entity.
Publisher Entity: It has PublisherId, Year of publication, name. PublisherID is the Primary Key.
Authentication System Entity: It has LoginId and password with LoginID as Primary Key.
Reports Entity: It has UserId, Reg_no, Book_no, Issue/Return date. Reg_no is the
Primary Key of reports entity.
Staff Entity: It has name and staff_id with staff_id as Primary Key. lOMoAR cPSD| 40190299 Question 1, 2 and 3 Answer ENTITY ATTRIBUTES DATATYPE Book Authno varchar (20) ISBN varchar (13) title varchar (50) edition varchar (20) category varchar (30) price Double (18,2) Reader UserId varchar (20) Email Varchar (50) Address Varchar (20) Phone_no varchar (20) Firstname varchar (30) Lastname varchar (30) Publisher PublisherId varchar (10) YearofPublication Datetime Name varchar (50) Authentication_System LoginId varchar (20) Password varchar (20) Report UserId Varchar (20) Reg_no varchar (10) Book_no int Issue/Return Datetime Staff Name varchar (30) staff_id varchar (20)
Reserve/Return Relationship Set: It has three attributes: Reserve date, Due date, Return date.
Question 4 Answer THE SCHEMA DIAGRAM
Let FK = Foreign Key and PK = Primary Key BOOK Price Category Edition Authno ISBN(PK) Title READER UserId(PK Email firstNam lastName Address ) e lOMoAR cPSD| 40190299 PUBLISHER
Publisher_Id(PK YearofPublication Name ) PHONE NUMBER UserId(FK Phone# ) AUTHENTICATION SYSTEM LoginId (PK) Passwor d STAFF Name Staff_Id(PK) REPORTS UserId(FK Reg_no(PK Book_no Issue/Return_dat ) ) e
Question 5 Answer
This Library ER diagram illustrates key information about the Library, including
entities such as staff, readers, books, publishers, reports, and authentication system.
It allows for understanding the relationships between entities.

ENTIY RELATIONSHIP SCHEMA DIAGRAM lOMoAR cPSD| 40190299
Relationships between Entities
A reader can reserve N books but many books can be reserved by only one reader. The relationship 1:N.
A publisher can publish many books but a book is published by only one publisher. The relationship 1:N.
Staff keeps track of readers. The relationship is M:N.
Staff maintains multiple reports. The relationship 1:N.
Staff maintains multiple Books. The relationship 1:N.
Authentication system provides login to multiple staffs. The relation is 1:N lOMoAR cPSD| 40190299
THE SCHEMA RELATIONAL DIAGRAM
Let FK = Foreign Key and PK = Primary Key BOOK Price Category Edition Authno ISBN(PK) Title READER UserId(PK Email firstNam lastName Address ) e PUBLISHER
Publisher_Id(PK YearofPub Name ISBN(FK) ) lication PHONE NUMBER UserId(FK) Phone# AUTHENTICATION SYSTEM LoginId (PK) Passwor d STAFF Name Staff_Id(PK) REPORTS UserId(FK Reg_no(PK Book_no Issue/Return_dat ) ) e