Community e-Library System

Chapter-1

1.1 Introduction

All of the needs for managing libraries will be addressed by the E-Library
Management System. It will include the process of preserving data on books and
a variety of other items, as well as transactions that take place in the library
about book issuance, return, and renewal. It makes it easier for the administrator
to do his job. It allows users to sign up for the library and then sign in every time
they want to look for something in the library. The user may also manage and
change his personal information. A user may log in and search for things in the
library and borrow items if they are available. The database contains all user
information as well as library information. The user does not need to go to the
library every time they need to locate anything; instead, they may search for
goods from their computer.
This project is used to keep track of and govern library transactions. This will
provide us with all of the necessary information about the library. This project
focuses on adding/updating members and adding/updating books. We will be
able to distribute the reader to the members and keep track of their records and
examine available books, active members, and issue books.Admin can keep
track of the books that have been returned.It can keep track of late fees for
members who return books beyond the due date. All of these Are carried out by
the library's administration. Admins can add, remove, and alter user information.
Students can only see or access their information.Additionally, we implemented a
book suggestion system. After successfully logging in, the student can suggest a
book to any other students. They can write suggestions about the book.
Other students can view the suggestions of everyone in a simple forum. Students
can send a private message to the admin to collect new books. The personal
statement only can be seen by the admin. Admin can take the report about the
book, the student, and the fine and written books.

1.2 Existing system

All book transactions in the previous system are done manually. This is the time
consuming process.it takes too long to complete a transaction, such as
borrowing or returning a book and looking for books. Another significant
drawback is that it will take longer to prepare a list of books borrowed and
available in the library. Now, this is a one-day procedure for checking all data.
The "Community e-library" primarily focuses on fundamental library activities
.This project has several features not often seen in traditional library
management systems, such as the ability to log in to a teacher. The Community
e-library is intended to assist users in maintaining and organizing their library
transactions. The user may create various reports, including lists of enrolled
students, lists of books, and issue and return reports.

Librarians use it to administer the library using a computerized system. They may
record different transactions.The proposed system is a library management
system that is automated. It has an admin login feature,It is for controlling all
things. Students can use this system to check in to their accounts online and
examine a list of books that have been issued and their issuance and return
dates.This project is designed to reduce the human labour cost and easily search
and find the available books for students. This computerized method will not lose
book or member records, which is common with non-computerized systems.
 ● The beginning Library management is done by hand. It took a long time to
record or obtain the information. Employees who are responsible for
recording the details must do it with extreme caution. Even a minor blunder
would result in a slew of issues. Information security is essential.
● The process of maintaining the library catalog and arranging the books in
the catalog is quite complicated. Manually keeping member data, issue
dates, and return dates, among other things, is a complex undertaking.
● All activities must be completed flawlessly to maintain the library without
causing any deterioration, which might lead to the system's collapse.

1.3 Drawbacks Of Existing System

The following are some of the issues with manual systems:
1.Report generation is not easy.
2.Searching a book is complicated.
3. Returning book information record keeping is a headache process

1.4 Proposed System

1. Keeping track of books and users.
2. Entering the transaction.
3. Reports.
4. Secured Database
5. Accessible from any location.

Some Solution in Proposed system

1. It gives members "better and more efficient" service.
2. It is a web-based system that can be accessed from any location.
3. The user may get information on the book without having to go to the library.
4. Reduce the employee's workload.
5. Information regarding the selected book may be retrieved more quickly.
6. Provide a facility for adequate monitoring and a reduction in paper effort and
data security.
7. All information will be available with a single click.

1.5 Vision
The goal is to create a streamlined online library administration system. Users
from all around the globe may utilize online search to find books in the library.
This enables members to the library's ability to manage activities through the
internet Administrators and students can also use it.Keep an eye on what's going
on at the library.

1.6 Scope
An improvised search algorithm is the scope of the library management system.
Real-time searching methods can also be used to increase the search's
functionality.The book name may be used to look for information about a book on
the internet and obtain it for the user. All of these things can be done to improve
the current solution.

1.7 Objectives
The project aims to establish a community e-library system that separates
administrators, books, and students. Users and administrators can look for and
borrow/take books from the library.It also organizes library materials and allows
administrators to keep track of books and members and make reports for them.
 Chapter-2

2.1 System Analysis

In this unit, we shall describe , evaluate the Library System development

process, including software requirements and specifications. The SRS portion
includes functional and non-functional requirements to offer a thorough
description and overview of system needs before the development process
begins.

2.2 Software Requirement Specification

2.2.1 General Description

Problem Statement:
The following issues happened before the use of a computerized system:
● File loss:
When an automated system is not implemented , The files are always lost
due to human error. Records may be lost due to human mistakes.
● The file has been damaged :
When we are not storing these details in e format,the entire file will be lost.
Finding information is always challenging:
When Records if the number of records is huge when there is no
automated system in place.
● Expenses a lot of money:
Because there is no electronic system, each recording paper will have to
be added manually, increasing the cost of library administration.
2.2 System Objectives

● Improvements in control and performance have been made to the system

to address current library difficulties and challenges.

● The system is bug-free,the system has the ability to validate users. Save
money By implementing a computerized system, low human cost will be
necessary to manage the library, lowering overall costs.
● Save time : The admin can search the whole record in simple clicks
● The students able to send messages to admin and student can suggest
the books to his friends

2.3 System Requirements

2.3.1 Non Functional Requirement

EFFICIENCY REQUIREMENT:
When this system is implemented , librarians and users will have much
easier access to the system since searches and book transactions will be much
faster.

RELIABILITY REQUIREMENT:
Member registration, member validation, report creation, book transaction,
message sending, book suggestion, and search should be appropriately made by
the system.

USABILITY REQUIREMENT:
The system provides a user-friendly environment in which students and
library personnel may effortlessly and effectively complete various activities.
IMPLEMENTATION REQUIREMENTS:
The entire system is implemented using HTML on the front end, python as
the server side scripting language, and the Django framework for database
connectivity and the backend.Sqlite3 is used to create the database.

DELIVERY REQUIREMENTS:
The complete system is planned to be implemented and delivered in one
month, with a weekly project guide review.

2.3.2 Functional Requirement

2.3.2.1 STUDENT (USER) LOGIN

The user can log in to the system in our application. The primary user is the
admin and students. Students can log into the system by entering the user name
and password. If the user name and password are correct, only the system will
allow the user to enter the user view page or panel. If the user name or password
is invalid, then the user can access the system.
● The user id and the username are provided by the admin one registering a
new user.
● Our application will allow the user to enter the side of the system if the
username and the password are valid.
● The students should logout after finishing their work on the system.

2.3.2.2 ADD NEW USER

After admin login, the admin can create a new user. While making the new user,
the admin should provide details about the user like username password user
first name user last name user branch details, user mobile details user email
extra. The admin can list all the users' details and delete an update based on
request.
● The admin provides the initial username and password.
● The system will process the information to save the data on the database.
● The admin can take the crud action on each user.

2.3.2.3 UPDATE AND DELETE USER

Admin can update or delete the student details from the list of students'
information. Admin can change any data related to the user on the update page.
By simply clicking the delete button, the admin can delete the user details from
the DB.
● If the admin updates the user information, it's also updated on the user
view page.
● So the user and admin can't access the deleted user information anymore.
● The system will validate provided data while updating.

2.3.2.4 INSERT BOOK DETAILS

Admin can insert the book details into the system. Initially, the system doesn't
have any book information. After successful login, the admin will do the
processes. Admin can be uploading the book information admin should provide
some details about the book. It is beneficial to the students to search and view
the book information. The pieces of information of the book title, the author's
names, the publication information. Book related to which category.
● The system will verify the book provided book information is correct or
wrong.
● The system will generate a book ID for each book.
● The book ID is a primary key in the database table.
 ● If all the information is correct, then the book objective will be saved in the
database.

2.3.2.5 INSERT BOOK DETAILS

Admin can update or delete the book details from the list of book information.
Admin can change any data related to the book on the update page. By simply
clicking the delete button, the admin can delete the user details from the DB.

● If the admin updates the book information, it's also updated on the book
view page.
● So the user and admin can't access the deleted book information anymore.
● The system will validate provided data while updating.

2.3.2.6 SEARCH USER AND BOOK INFORMATION

After successful login, the student and the admin have the option to search the
book details. But when we are discussing searching the user details, it is only
possible for the admin.Searching is implemented on the front-end side using ajax
and JavaScript.
The HTML table tag is derived to use some libraries in JavaScript. The
JavaScript library is a third-party API for sorting and searching. Based on
user-provided information, the table will automatically change.The end column of
the table is attached with two buttons. One for viewing the information and
another one for deleting the data.
● The JavaScript and ajax Library are used for searching.
● Based on user information, it will Fetch the data from the database.
● When a user has selected a book, it will pass the book ID to the controller.
● If the user entered the wrong information, that table would be empty.
2.3.2.7 ISSUE THE BOOK TO THE USER

After searching the book, the student can inform the librarian or admin to borrow
the book. Then the admin can issue a book to the student. There is no limitation
for giving the book to the student. Students can borrow any number of books.
When issuing the books, the admin will send some information like student id and
student id unique for every student, The book name or book ID. The book ID is
also unique for each book. When issuing a book, the admin should select the
book's return date.
● It will validate the admin-provided information.
● The issued book's details will be stored in a table in DB.
● After issuing a book, the student can view the book transaction details in
their account.

2.3.2.7 RETURN THE BOOK

Before the returning date, the student should return the book to avoid the fine.
When the student is logged into the system, they can see the book details in their
account. The system will check the returning date of the book separately.

FUNCTIONAL REQUIREMENT :
● The returning date will be validated from the database.
● If the student returns the book before the date, then there is no fine.
● Based on the fine table, the admin can create the report.

2.3.2.7 SUGGEST THE BOOK

This is the different future in the library system. After the successful login, the
student can suggest the book details to their friends. This means that if a student
has a good suggestion about the book, they can write their feedback in a joint
blog. The suggestion is not private. This is available for everyone. Based on the
recommendations, the other students can borrow these books. In simple terms
this is a feedback system about the book from the Student side.

FUNCTIONAL REQUIREMENT :
● The suggestions details will be stored in separate tables in DB.
● There is no crud operation available for suggestions.
● This page is available for every user after login.

2.3.2.8 MESSAGE TO THE ADMIN (LIBRARIAN)

This is another additional feature in this library system. After login, the student
can send a private message to the admin. The admin can see the message. This
message is about the new books available in the market.
FUNCTIONAL REQUIREMENT :
● This is a private message. We have implemented a message type in the
database.
● There is no length restriction, and there is no number restriction in the
database. So a student can share a long message multiple times.

2.4 System Design

In this chapter, we are discussing the system like the use case diagram and class
diagram.

2.3.1 USE CASE DIAGRAM

The admin and StudentStudent are the two main actors in this system. The
admin can use cases like login register issue book and collect fines.When the
admin is logging the verification processes, they are included. The extended Use
case is an error message showing.Admin has the register use case. In this case,
the admin has the privilege to add the new Student and add the details of the
new books with crud operations.Issue the book to the StudentStudent based on
their request. This is another use case for admin. When a student fails to return
the book within a date, a use case is collected fine. Collect fine use cases used
to manage the fine from StudentStudent.
Another primary actor is StudentStudent. This shouldn't have some use cases
like login, search book, suggest a book, and message to the admin.The Student
will get the username and password from the admin. By using this username and
password, StudentStudent can log in to the system. Successfully login students
can search the book details from their home page.

2.3.1 CLASS DIAGRAM

In the Class diagram, we designed all the entities included in the methods with
an instance variable.The main classes described in the class diagram are a
returnbook ,suggestbook ,issuebook,book, student,and message.

The student is the main class, and This class is related to all other classes.
Student class has the cardinality to other classes.One Student can borrow many
books. The issue book classes include the book details and student details with
foreign key functionality in the database. One student can suggest many books.
This is one of many relationships.One student can send multiple messages to the
admin. This is also one to many relationships.

2.3 Cost Analysis

DEVELOPER TASK (Designer (6 USD / Hour))

Frontend Hours

Login 2

Book 4

Student 4

Admin DashBoard 6

Issue Book 3

Return book 3

Suggestion 3

TOTAL 25

Programmer (12 usd / Hour)

Backend HOURS

Login 1

Book 2

Student 2

Admin 2

Issue Book 3
Return book 2

Suggestion 2

Message 2

TOTAL 16

QA Expert Task (8 usd / Hour)

Specification review 4

Test cases preparation 4

Test cases execution 6

Total 14

Designer= 25*6 = 150

Programmer =12*16=192
Qa expert=8*14=112
Total: 454 USD

Chapter-3

3.1 Methodology Used

We are developing the waterfall model. In this type, Distribute the software into
phases. It is a long time taking methodology. It is effortless for a software
progress company to survive. One of the drawbacks of this model is, the
following phase can only start after completing the earlier step.
3.1.1 Requirement collection and analysis

This is the preliminary discussion to catch all the functionality of the community
library system. In this phase, the software development team should create a
meeting with the client, ask their requirements, and make a document to follow in
upcoming stages.

3.1.2 Feasibility Study

The Feasibility Study is the next phase.In this phase we want to discuss
Economics, Legal, Operation Feasibility, Technical, and Schedule.

3.1.3 Design

In this synopsis, we must produce a documentary based on the client's

necessities, known as the requirement definition document (RSD). The whole
structure of the application we will plan, such as Architecture , Database ,
Frontend etc.

3.1.4 Coding

Coding is the next period. Begin their software development according to the
programming language discussed with the buyer. All developers should catch the
coding rules. Coding should be readable to any developer. This phase is said to
be the most important phase .

3.1.5 Testing

In this phase we have to deploy our application on a testing server to check the
whole functionality.But in our case we are using the local host server which is the
default server in Django.
3.1.6 Deployment

After completing all the errors and bugs in the testing phase, we can proceed
with the deployment phase.Select a suitable and upgradable web server with
good security and firewall protection.

Chapter-4

4.1 Conclusion

The project "community library system" is completed in Python programming

language, with the help of Django framework.We have solved the existing library
problems in our software. The main aim of this project is to reduce the human
cost and the paper writing work. In our system, we have implemented these
solutions. The problem which exists has been made a solution for all. Our
application will run long without any bugs.

4.2 Reference
JavaTpoint. (2021, 11 15). Django Tutorial. Retrieved from javatpoint:
https://www.javatpoint.com/django-tutorial

jazzband. (2021, 11 16). Django configuration. Retrieved from Github :

https://github.com/jazzband/django-configurations

Official, D. (2021, 11 16). Writing your first Django app, part 1. Retrieved
from djangoproject: https://docs.djangoproject.com/en/3.2/intro/tutorial01/