design and implementation of library management system ORGINAL11
design and implementation of library management system ORGINAL11
1.0 INTRODUCTION
1
ra c ks in stacks as per the dewey decimal classificatio n
s c h eme.
iv. Periodical Section: To procure, maintain and arrange periodicals
services to library members. Periodical section provides reference
service with respect to the requirement of the reader. Reference
section is attached to periodical section for convenience of the library
users.
v. Databases: Databases like OPAC, CAB-CD ROM abstracting
databases, Delent online Network Service etc. are available for the library
members.
2
error there maybe loss and damages of records due to not using a
computerized system in the library.
The aim of this project is to develop a system that can handle and
3
The third subsystem is a borrower and return of books which is the
major area needed by the user. There are three end users for the Library
Management System. The end users are the admin, users and members.
1. Enhanced Efficiency:
o Automation: Automates routine library tasks such as
cataloging, check-outs, and returns, reducing manual effort
and minimizing errors.
o Speed: Speeds up various processes, such as searching for
books, managing inventory, and generating reports, which
improves overall library efficiency.
1. Project Planning:
o Define Objectives: Clearly outline the goals and objectives
of the LMS project.
o Scope: Determine the scope of the project, including features
and functionalities to be included.
o Resources: Identify required resources such as hardware,
software, and personnel.
o Timeline: Develop a project timeline with milestones and
deadlines.
2. Requirements Gathering:
o Stakeholder Analysis: Identify and consult with
stakeholders, including library staff, patrons, and
administrators, to gather their requirements.
o Functional Requirements: Document the features and
functionalities needed, such as cataloging, circulation, user
management, and reporting.
o Non-Functional Requirements: Define performance,
security, and usability requirements.
3. System Design:
6
o Architectural Design: Create an architectural plan for the
system, including hardware and software components.
o Database Design: Develop the database schema, including
tables, relationships, and indexing.
o User Interface Design: Design the user interface with a
focus on usability and accessibility.
o System Integration: Plan for integration with existing
systems or third-party tools if needed.
4. Development:
o Coding: Develop the system according to the design
specifications.
o Testing: Perform unit testing, integration testing, and system
testing to ensure the system functions correctly and meets
the requirements.
o Bug Fixing: Address any issues or bugs identified during
testing.
5. Implementation:
o Installation: Install the LMS software on the library’s
hardware or cloud platform.
o Data Migration: Migrate existing library data to the new
system.
o Training: Train library staff and users on how to use the new
system.
6. Deployment:
o Go-Live: Launch the system and make it available for use by
library staff and patrons.
o Monitoring: Monitor the system for performance issues and
user feedback during the initial phase.
CHAPTER TWO
LITERATURE REVIEW
2.0
2.1 Introduction
8
Library is regarded as the brain of any institutes, of course many
institute understand the importance of the library to the growth of the
institute and their esteem users which we categorically call the
students. Anintegrated library system, also known as a library
management system (Adamson et al., 2008) is an enterprise resource
planning system for a library, used to track items owned, orders made,
bills paid, and users who have borrowed. The Library Management
System is a Library Management software for monitoring and
controlling the transactions in a library (Ashutosh and Ashish., 2012).
Library Management System supports the general requirement of the
library such as the acquisition, cataloguing, circulation and other
sections. Before the advent of computer in modern age there are
different methods of keeping records in the library. Records are kept in
the library on shelves and each shelf are labelled in an alphabetical or
numerical order, in which the categories of books available are arranged
on different position on the shelves and as well are recorded on the
library manuscript and when any book is to be referenced the manuscript
is being referred to, to know the position of suchrequired book by the
person that requested for the book.After the invention of computer
different researchers have carried out various approach on an automated
capability of the system. With the 3.0 release in 2005, and the
viable, scalable solution for libraries of all kinds. LibLime KOHA is built on
this foundation. With its advanced feature set, LibLime KOHA is the most
9
functionally advanced open source Integrated Library System in the
hackers could have the database hacked and access or modify the
with that database, and two graphical user interfaces (one for users,
interfaces (one for users, one for staff). Most Library Management
10
modules, each of them integrated with a unified interface. Prior to
with the card cataloguing system (in which all bibliographic data was kept
on a single index card), and users signed books out manually, indicating
their name on cue cards which were then kept at the circulation desk.
using a punch card system to manage library circulation. While the punch
card system allowed for more efficient tracking of loans, library services
were far from being integrated, and no other library task was affected by
this change. The literature study in previous system could give more
and online resources. Foreign literatures will be mainly used and some
of these had been highlighted to peruse and emulate. The purpose of this
literature review is to establish the potential topics and suggest ideas for
included. As for this research, the main purpose of literature review will
11
be to grasp comprehensive ideas on the extent of library management
system initiatives and projects that had taken place worldwide and the
print and electronic sources were looked at, read and digested,
topic at hand.
now
A library management system is a system for a library resource
years ago, and it has grown into an almost synonym for integrated
mid to late 2000s, library management system vendors not only the
KOHA and Evergreen. Most reasons noted from these were to avoid
library system have found that vendors are more likely to provide quality
tying down libraries to strict contracts. This has been the case with
along with some local public libraries formed the SCl LENDS cibsirtuyn
needs.
maximize time and efficiency. Library system gives all the detailed
information about students, staffs and books, it will track the books
available in the library and the books that have been issued to the
will provide book lost in the library. It keeps records of the supplier and
14
i. Manage Book and Member Record with help of Barcode.
barcode scanner.
work even without Bar Codes seamlessly. The Bar-code generation and
vi. Facility for User to suggest items:User suggestion and request for
15
viii. Multiple Library Setup: Library management software can
setup at different locations.
ix. Export All Report into Excel, Word:Admin can take all the details
which are displayed in the reports into excel and word file.
xii. Maintain Any Media:one can define a number of things that one
wants to keep track of as well as can maintain different kinds of
media like Book, CD, File Documents, Video Cassette, and Audio
Cassette. Also one can maintain media with its own specifications
rather than common and define the specification you
want for that media, for book (pages, ISDN number, type, volume).
media can't be issued which falls under this criteria. One can in this way
media, get all the information related to the media and the number.
16
xvii. Easy Navigation and Updating: Selecting an option from the given
menu provides all the data related to that option in tabular format in a
user friendly manner.
xviii. Auto Filter & Auto Search: On each master form, Library Software
will search on the field where your cursor is and what you type is taken as
a search value.
xix. Customize:one can customize the system to feel easier for data
entry also while adding records user can keep form in ‘add’ mode. Define
holidays and set the criteria of issuing the book if member is requested for
media or not.
xx. Scrap-Type:Define their own scrap type for scraping the media.
2..1.4
Needs for library management system
analyses
manual processing
books due by a particular member and also the overdue charges. KOHA is
models for small to very large libraries (Neelakandan et al., 2010). The
collections that are in single database, it gives the full control over the
research scholars and faculty members can check the status of their
borrowed books, they can get the complete details about the books
18
for their further reading and research, data entry of the books can
library of congress and other catalogues and other catalogues and the
share their data with various library and other department in the libraries.
system which could be mainly used by member and staff of the library.
The system allows members search for books and reserve books through
website so that they can save their time and cost to travel from one place
to another to use the library as well as know what the book entails in the
library. In the system developed, staffs can also be able to add news
and also view reports with several criteria as well as add, edit and
19
ii. Member/staff module
The software used in the research entails the use of Microsoft products
like the Microsoft visual studio 2008 for the website development and
Microsoft SQL server 2008 as the database. Mainly the software and
v. Ram: 2 GB
The methodology used in the research was the waterfall model which
20
Ashutosh Tripathi, and Ashish
was Srivastaval, (2012) developed a system
and updating new information, searching books and members and facility
user can add members, add books, search members, search books,
The system they are developed has the following advantages. User
capacity, search facility, Look and Feel Environment. All the manual
maintain and organize library making the software very easy to use for
both beginners and advanced users. The system requirement for the
research entails how the library management system that was designed
Windows NT, supported for other platform such as Applet Macintosh and
21
ii. For Windows 98 based computers, a 500/88MHz or higher
which the admin can monitor the whole system etc. the objectives
22
The software and hardware requirement in the designing of the system
were:
to write the whole code and develop webpages with CSS, java
script for styling work and PHP for sever side scripting.
v. Ram 1 GB
and obtain necessary requirements data from the librarians, analyse the
obtain data, design and develop the system and conduct an assessment
order to achieve the lowest possible unit cost and develop close,
this. The system was developed using some instruments used for the
23
staff system of this university, microsoft SQL server for database
24
and receiving new items, as well as managing vendor relationships
and tracking expenditures.
Inventory Control: Inventory Control involves managing the
library’s collection to ensure that materials are accounted for and
properly maintained. This includes tracking the physical location of
items, monitoring their condition, and conducting regular inventory
checks.
OPAC (Online Public Access Catalog): An Online Public Access
Catalog (OPAC) is a user interface that allows library patrons to
search for and access information about library resources online. It
provides features such as keyword searching, filtering, and viewing
item details.
Reservation System: A Reservation System allows library users to
reserve or place holds on items that are currently checked out or
unavailable. It helps users secure access to materials they need by
notifying them when the items become available.
Barcode System: A Barcode System uses barcodes to uniquely
identify library materials and streamline the check-out and check-in
processes. Each item is tagged with a barcode that can be scanned
using a barcode reader to quickly access and update its status in
the LMS.
User Interface (UI): The User Interface (UI) refers to the visual and
interactive elements of the LMS that users interact with. This
includes screens, menus, buttons, and other design components
that facilitate user interaction with the system.
Backend System: The Backend System encompasses the server-
side components and processes that support the LMS. It includes
database management, server logic, and application programming
that handle data processing, storage, and retrieval.
Security Measures: Security Measures are protocols and practices
implemented to protect the LMS from unauthorized access, data
breaches, and other security threats. This includes data encryption,
25
access controls, and regular security audits to ensure the integrity
and confidentiality of library data.
CHAPTER THREE
The existing system of library management system involves lots and lots
of paper work. The system involves that all library user details will be
borrower information is being taken for every registered user and can
actually sign out for return of the book once he/she is completed.
Having have the overview knowledge of the existing system, the following
are its problem
I. Loss of Data: A lot of paper works are needed for the safe keeping
of the details of books borrowed by a registered user
II. Time Wasting: User time are wasted as a result of searching for a
book that has been borrowed by a user whose record cannot be
traced on the paper records.
vi. Processing Speed: The processing speed is very low resulting into
low output.
26
3.3 DESIGN OF THE NEW SYSTEM
of record keeping of the books stored in the library. It has the following
features.
ii. An applicant is allowed to log into the system with his name and
administrator goes into the report to view the details of a particular user.
The input specification outlines the types of data and user interactions the
system will accept. For a Library Management System, inputs can be
categorized into several key areas:
User Information:
o New User Registration:
User ID (automatically
generated or manually entered)
Name
Address
27
Phone Number
Email Address
Membership Type (e.g., Student, Faculty, Guest)
o User Login:
User ID
Password
o User Profile Update:
User ID
Updated fields (e.g., address, phone number, email)
b. Book Management
Book Entry:
o Book ID (automatically generated or manually entered)
o Title
o Author(s)
o ISBN
o Publisher
o Publication Year
o Genre
o Number of Copies
o Location (Shelf/Library section)
Book Update:
o Book ID
o Updated fields (e.g., number of copies, location)
Book Deletion:
o Book ID
c. Book Transactions
Check-Out:
o User ID
o Book ID
o Date of Check-Out
28
Check-In:
o User ID
o Book ID
o Date of Check-In
Renewal:
o User ID
o Book ID
o New Due Date
Reservation:
o User ID
o Book ID
o Reservation Date
Search Books:
o Search Criteria (e.g., title, author, ISBN, genre)
Search Users:
o Search Criteria (e.g., name, user ID)
Generate Reports:
o Report Type (e.g., overdue books, popular books, user
activity)
o Date Range
The output specification defines the information that the system will
provide in response to user interactions and system processes. For a
Library Management System, outputs are typically categorized as follows:
c. Transaction Outputs
Check-Out Confirmation:
o Success/Failure Message
o Due Date
Check-In Confirmation:
o Success/Failure Message
o Overdue Fees (if applicable)
Renewal Confirmation:
o Success/Failure Message
o New Due Date
Reservation Confirmation:
o Success/Failure Message
30
o Reservation Status
Search Results:
o List of books or users matching search criteria
o Details for each item found
Detailed Item View:
o Comprehensive information about a specific book or user
Generated Reports:
o Detailed report based on selected criteria
o Visual representations (charts/graphs) if applicable
Downloadable Reports:
Certain merits have been associated with the proposed system which
b eo w :
31
CHAPTER FOUR
This describes how the system works and how best computers together
with other resources may be applied to perform data storage,
management and retrieval for decision making. The requirement of this
research work demand a web programming language.
32
The software support for the design of the proposed system involves:
Unlike Unit and Integration Test Plans, system test plans are composed
application developed are met. The whole application is tested for its
1. Performance Metrics:
33
o Speed: The system should quickly handle tasks such as book
check-ins/outs, searches, and database queries.
o Scalability: The system should perform well even as the
number of users or amount of data increases.
o Resource Utilization: Efficient use of server and database
resources to minimize operational costs.
2. Usability:
o Ease of Use: The interface should be intuitive for both library
staff and patrons, reducing the time needed for training and
daily operations.
o Accessibility: The system should be accessible from various
devices (computers, tablets, smartphones) and be compliant with
accessibility standards.
3. Reliability:
o Uptime: The system should have minimal downtime and be
robust against failures.
o Error Handling: Proper error messages and recovery options
should be in place to handle unexpected issues gracefully.
4. Data Management:
o Accuracy: Ensure accurate cataloging of books and user data
with minimal errors.
o Security: Implement strong security measures to protect
sensitive data from unauthorized access or breaches.
1. Pre-Installation Preparation:
o System Requirements: Verify that the hardware and
software meet the system’s requirements.
o Backup: Ensure that existing data is backed up to prevent
loss during the transition.
34
2. Installation Steps:
o Software Installation: Follow the installation guide to set up
the LMS software on the server or cloud platform.
o Configuration: Configure the system settings, including
database connections, user roles, and library-specific
parameters.
o Data Migration: Import existing data (e.g., book catalog,
user records) into the new system.
3. Testing:
o Initial Testing: Conduct tests to ensure the system operates
correctly in a controlled environment.
o User Testing: Allow a small group of library staff and patrons
to use the system and provide feedback.
4. Training:
o Staff Training: Provide training sessions for library staff on
how to use the system.
o User Guides: Distribute user guides and manuals to assist
with common tasks.
5. Go-Live:
o Deployment: Move the system from a test environment to
live operation.
o Support: Provide technical support to address any issues that
arise during the initial period.
1. Regular Updates:
o Software Updates: Regularly check for and apply updates to
the LMS software to fix bugs and add new features.
35
o Database Maintenance: Perform routine database
maintenance tasks such as backups, indexing, and cleanup.
2. Monitoring:
o Performance Monitoring: Use monitoring tools to track
system performance and address any issues promptly.
o Error Logs: Regularly review error logs to identify and
resolve potential problems.
3. User Support:
o Help Desk: Provide ongoing support to users for
troubleshooting and resolving issues.
o Documentation: Maintain up-to-date documentation for
users and administrators.
4. Security:
o Regular Audits: Conduct regular security audits to identify
and address vulnerabilities.
o Data Protection: Ensure that data encryption and access
controls are enforced.
1. Scope Limitations:
o Functionality: The study may focus on certain functionalities
and may not address all possible features or customizations.
o Integration: Limited integration with other systems (e.g.,
external databases or third-party tools) may be considered.
36
2. Resource Constraints:
o Budget: Financial constraints may limit the extent of system
features and the quality of hardware and software used.
o Time: Time constraints may restrict the depth of testing and
the extent of user training provided.
3. Technological Limitations:
o Compatibility: The system may face compatibility issues
with older hardware or software.
o Scalability Issues: The system might encounter scalability
challenges as the library grows or as user demands increase.
CHAPTER FIVE
5.1 Summary
The quest to make life easier and processing faster has led to
5.2 Conclusion
adequately meets the minimum expectations that were for it initially. The
37
new system is expected to give benefits to the users and staff in terms of
5.3 Recommendation
For further research work to be carried out. I hereby suggest the following
others.
REFERENCES
August 2015.
& Pratice.
38
Adomi, E. E., & Anie, S. O. (2006). An Assessment of Computer Literacy
Skills of professionals in Nigerian University Libraries. Library Hi Tech
news, vol.23 (2) pp.10-14.
IFLA. Available:http://www.ifla.org/files/hq/papers/ifla75/126-dasgupta-
en.pdf.
developing countries.
The International Information & Library Review, Vol. 39, pp. 64-71.
39
Prabhakar kumar, Rahul Kumar,Rajat Singh and Vikram Singh. (2014).
Library Management System. Division of Computer Science School of
Engineering Cochin University of Science & Technology Kochi-682022.
Avaliable:
http://unllib.unl.edu/LPP/rahman-khatun-mezbahulislam.html .
computer science school of arts and science Tanku Abdul rahman college
kualla lampur.
APPENDIX: CODE
40
Index code
<?php include('header.php'); ?>
<div class="row">
<?php include('head.php'); ?>
<div class="span2">
<?php include('sidebar.php'); ?>
</div>
<div class="span10">
<?php include('slider.php'); ?>
</div>
<div class="span2">
<h4></h4>
</div>
<div class="span10">
<?php include('thumbnail.php'); ?>
<div class="text_content">
<div class="abc">
<hr>
<p>
41
acknowledged as a primary and engaged regioanl and global resource
for entreprenuerial education and best practise in mining and farming
technology.
</p>
<hr>
<h4>Mission</h4>
<hr>
<p>
<hr>
</div>
</div>
<!-- end content -->
</div>
</div>
</div>
</div>
<?php include('footer.php') ?>
Header
<!DOCTYPE html>
<html>
<head>
<title>Federal University Oye Ekiti</title>
42
<meta name="viewport" content="width=device-width, initial-
scale=1.0">
<!--js -->
<script src="js/jquery- 1.7.2.min.js"></script>
<script src="js/bootstrap.js"></script>
<script src="js/jquery.hoverdir.js"></script>
<script type="text/javascript" charset="utf-8"
language="javascript"
src="js/jquery.dataTables.js"></script>
<script type="text/javascript" charset="utf-8"
language="javascript"
src="js/DT_bootstrap.js"></script>
<script>
jQuery(document).ready(function() {
$(function(){
$('.pix_diapo').diapo();
43
});
});
</script>
<noscript>
<style>
.da-thumbs li a div {
top: 0px;
left: - 100%;
-webkit-transition: all 0.3s ease;
-moz-transition: all 0.3s ease-in-out;
left: 0px;
}
</style>
</noscript>
</head>
<body>
Navbar
<div class="navbar-inner">
<div class="container">
44
<a class="btn btn-navbar" data-toggle="collapse" data-target=".nav-
collapse">
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</a>
<li class="divider-vertical"></li><li
class=""><a rel="tooltip" data-placement="bottom" title="Home"
id="home" href="index.php"><i class="icon-home icon-
large"></i> Home</a></li>
<li class="divider-vertical"></li>
<li class="">
Here to About" id="login" large"></i> About</a>
<li class="divider-vertical"></li>
<li class="">
</li>
<li class="divider-vertical"></li>
<li class="">
45
</li>
<li class="divider-vertical"></li>
<li class="dropdown">
<a href="#"
class="dropdown-toggle"
data-toggle="dropdown">
<i class="icon-book icon-large"></i> Sections
<b class="caret"></b>
</a>
<ul class="dropdown-menu">
</li>
<li class="divider-vertical"></li>
46
<li class="signup"><span
class="sg"></span></li>
</ul>
</div>
</div>
</div>
</div>
Head
<div class="span12">
<div class="header">
<div class="pull-left">
<img class="stilogo" src="LMS/A1.jpg">
</div>
</div>
<div class="pull-right">
<i class="icon-calendar icon-
large"></i> <?php
$Today = date('y:m:d');
$new = date('l, F d, Y',
strtotime($Today));
echo $new;
?>
</div>
</div>
47
</div>
Sidebar
<div class="life-side-bar">
<div class="hero-container">
</div>
<ul class="nav nav-tabs nav-stacked">
<li class="">
<a href="#"><i class="icon-phone icon-
large"></i> Contact US</a>
</li>
</ul>
<strong>Address</strong>
<p>Federal University of Oye Ekiti</p>
<p>[email protected]</p>
</div>
<div class="modal-body">
48
</div>
<div class="modal-footer">
<button class="btn" data-dismiss="modal" aria-hidden="true"><i
class="icon-remove icon-large"></i> Close</button>
</div>
</div> <!-- mission student login -->
<div class="modal-body">
<p>
</div>
<div class="modal-footer">
<button class="btn" data-dismiss="modal" aria-hidden="true"><i
class="icon-remove icon-large"></i> Close</button>
</div>
</div>
Footer
<footer class="footer">
<div class="container">
<div class="foot-margin">
<p><a>2015 Federal University Oye Ekiti. All Rights Reserved. </a></p>
</div>
</div>
49
</footer>
<script type="text/javascript">
$(function() {
$('#da-thumbs > li').hoverdir();
});
</script>
<div id="logout" class="modal hide fade" tabindex="- 1"
role="dialog" aria-
labelledby="myModalLabel" aria-hidden="true">
<div class="modal-body">
<div class="alert alert-danger">Are you sure you want to Logout</div>
</div>
<div class="modal-footer">
<button class="btn" data-dismiss="modal" aria-
hidden="true">Close</button>
<a href="logout.php" class="btn btn-danger">Yes</a>
</div>
</div>
<script type='text/javascript' src='scripts/jquery.easing.1.3.js'></script>
<script type='text/javascript'
src='scripts/jquery.hoverIntent.minified.js'></script>
</html>
50
APPENDIX II
1 Admin login
choose the ADMIN LOGIN option where they are asked to enter
ADMIN
DATABASE
ADMIN ENTER
HOME USERSNAM CHECK
LOGIN
E AND VALIDITY
PASSWORD
ADMIN
DATABASE ADMIN
DATABASE
51
figure 3.4: Dataflow diagram for admin login
User login
USER
DATABASE
USER
ENTER
HOME USERSNAM CHECK
LOGIN
E AND VALIDITY
PASSWORD
USER
DATABASE USER LOGIN
PAGE
52
Library management
system
53
3. SCREENSHOT OF ADD BOOKS METHOD
54
6. SCREEN SHOT OF USER TABLE
55
9. SCREENSHOT OF MEMBER TABLE.
56