A

Mini Project Report

On
“Library Management System Using C#”
For
BACHELOR OF TECHNOLOGY
in

“Computer Science & Engineering”

Submitted by
Shubhagaman Singh (2201200109029)

Under Guidance of
Mr. Nitin Dixit
(Ast. Professor, CSED)
Submitted To

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

INSTITUTE OF TECHNOLOGY & MANAGEMENT,
GIDA, GORAKHPUR
(AFFILIATED TO DR. A. P. J. ABDUL KALAM TECHNICAL UNIVERSITY, LUCKNOW)
 SESSION: 2024-25

INSTITUTE OF TECHNOLOGY & MANAGEMENT

Integrated Technical Campus: Engineering, Pharmacy & Management
Approved by AICTE, Pharmacy Council of India, New Delhi & Affiliated to Dr.
APJAKTU, Lucknow AL-1, Sector - 7, GIDA, Gorakhpur - 273209 (UP)

Department of Computer Science & Engineering

Vision & Mission of the Department

Vision of the Department:

Excellence in education to produce competent computer professional to meet

the need of industry and society.
Mission of the Department:

1- To impart quality education in computer science & engineering through

competent faculties, good infrastructure and learning resources to
produce competent graduates required by the industry.

2- To inculcate knowledge and skills stand to strengthen industry -institute

interaction to promote individual and team excellence to meet the
requirement of industry.

3- Todevelopgraduatestobecomputerprofessionalswithhighethicalstandardan
dself- learning ability.

PEONo. Program Educational Objectives Statements

To prepare competent computer science graduates to have successful career
PEO1
in application software development and in allied industries.
To impart in depth knowledge in core computer science and engineering
PEO2 Domain and expertise in providing solution to complex problems using modern
IT tools to meet the requirement of industries.
To inculcate professional skills and to work effectively as individual and
PEO3
Member of a team in multi-disciplinary projects.
To develop self-learning ability, to protect environment and exercise ethical
PEO4
Code of conduct in professional practice and activities.

ii | P a g e
 INSTITUTE OF TECHNOLOGY & MANAGEMENT
Integrated Technical Campus: Engineering, Pharmacy & Management
Approved by AICTE, Pharmacy Council of India, New Delhi & Affiliated to Dr.
APJAKTU, Lucknow AL-1, Sector - 7, GIDA, Gorakhpur - 273209 (UP)

Department of Computer Science & Engineering

Rubrics are tagged with course outcomes for the laboratory performance.

PO
Rubrics CO Statements MAPPING
Students will be able to work effectively in individual and PO9,
1 C211.1 team to manage the projects. PO11
Apply written and verbal communication through report and
2 C211.2 presentation. PO10

Apply the fundamental principles of engineering

PO1,
3 C211.3 into
PO8
Development of technology and able to develop work ethics
in industry.

iii | P a g e
 INSTITUTE OF TECHNOLOGY & MANAGEMENT
Integrated Technical Campus: Engineering, Pharmacy & Management
Approved by AICTE, Pharmacy Council of India, New Delhi & Affiliated to Dr.
APJAKTU, Lucknow AL-1, Sector - 7, GIDA, Gorakhpur - 273209 (UP)

Department of Computer Science & Engineering

EVALUATION

PROGRAM NAME : B. TECH(CSE) SEMESTER : VII

COURSE NAME : MINI PROJECT OR INTERNSHIP SESSION : 2024-25

COURSE CODE : KCS (753) SECTION : C

Sr.No Roll No. Name CO1 CO2 CO3 TOTAL

Rubrics Rub1 Rub2 Rub3

Maximum Marks

1.

iv | P a g e
 Certificate & Deceleration

This is certified that the work which is being presented in the mini project
entitled “Library Management System using C#” is submitted in the
department of Computer Science and Engineering of Institute of
Technology and Management, GIDA, Gorakhpur is an authentic record of
my own work carried out during the semester under the supervision

The matter presented in this mini project has not been submitted by me for the
award of any other degree of this or any other institute/university.
Shubhagaman Singh

This is to certify that the above statement made by the candidate is correct to
the best of my knowledge.

Date Candidate Signature

Mr. Nitin Dixit Mr. Ashutosh Rao

(Mini Project Coordinator) (Head of Department,
CSE)

v|Page
 Acknowledgement

First and foremost, I praise and thank ALMIGTHY GOD whose blessings
have bestowed in me the will power and confidence to carry out my
project. I am grateful to our beloved founders Late. Dr. D.G.S. Dhinakaran,
C.A.I.I.B, Ph.D. and Dr. Paul Dhinakaran, M.B.A, Ph.D., for their love and
always remembering us in their prayers. I extend my thanks to our Vice
Chancellor Dr. P. Mannar Jawahar, Ph.D. and our Registrar Dr. Elijah
Blessing, M.E., Ph.D., for giving me this opportunity to do the project. I
would like to thank Dr. Prince Arulraj, M.E., Ph.D., Dean, School of
Engineering and Technology for his direction and invaluable support to
complete the same. I would like to place my heart-felt thanks and gratitude
to Dr. Ciza Thomas, M.E., Ph.D., Dean, Computer Science and Technology
for her encouragement and guidance. I would like to place my heartfelt
thanks and gratitude to Dr. J. Immanuel John Raja, M.E., Ph.D., Head of
the Division, Computer Science and Engineering for his encouragement
and guidance. I feel it is a pleasure to be indebted to, Dr. Arul Xavier V M,
Ph.D., Assistant Professor, Division of Computer Science and Engineering
for his invaluable support, advice and encouragement. I also thank all the
staff members of the Division for extending their helping hand to make this
project a successful one. I would also like to thank all my friends and my
parents who have prayed and helped me during the project work.

vi | P a g e
 Abstract

University Library Management System. The C# Library Management

System is an advanced desktop application developed using Visual Studio
2022 and the C# programming language, tailored to revolutionize the
traditional library management paradigm. Its foundation is a robust MySQL
database, seamlessly integrated with the XAMPP server environment,
ensuring a reliable and efficient data management system. This
comprehensive solution encompasses diverse functionalities, such as book
cataloging, borrower administration, and transaction tracking, all while
allowing for precise book categorization and fine-grained user
management. Its user-friendly interface simplifies navigation, providing
librarians with real-time insights into the library's inventory and lending
history through detailed inventory reports. By automating routine tasks, this
system not only reduces the demand for extensive library staff but also
reinforces data accuracy and integrity. In summary, the C# Library
Management System empowers librarians with a cutting-edge toolset,
enabling them to offer patrons a seamless and highly efficient library
experience, making it an indispensable asset for educational institutions
and organizations seeking to elevate their library management capabilities.
Project Platform: Microsoft Visual Studio 2022, XAAMP. Programming
Language: C# Programming Language, SQL. Project Type: Desktop
Application Database: MySQL Database Keywords—Desktop Application,
Book Management, Borrower Management, Transaction Tracking.

vii | P a g e
 Table of Contents
Certificate & Deceleration.........................................................................................
Acknowledgement....................................................................................................
Abstract...................................................................................................................
Introduction...............................................................................................................
Introduction................................................................................................1
Motivation & Objectives............................................................................2
Overview of the Project.............................................................................2
Chapter wise Summary..............................................................................3
Analysis & Design [1] [2] [3]....................................................................................
Functional Requirements...........................................................................4
Non-functional Requirements....................................................................5
Use case Diagram.......................................................................................5
Entity Relationship Diagram......................................................................6
Implementation [4] [1] [5].........................................................................................
Modules Description..................................................................................9
Implementation Details............................................................................10
Software Tools used.................................................................................21
Test results/experiments/verification.......................................................................
Testing......................................................................................................22
Results......................................................................................................22
Verification...............................................................................................23
Conclusion & Future Scope.....................................................................................
References [6] [7] [2] [1] [8] [4] [3] [5]..................................................................
Appendix Code........................................................................................................
Form1.cs................................................................................................27
FormBorrower.cs...................................................................................30

viii | P a g e
ix | P a g e
 Table of Images
Screenshot 1: User Login Page.....................................................................7
Screenshot 2: Front Login Page....................................................................7
Screenshot 3: Database Attributes.................................................................8
Screenshot 4: Properties................................................................................9
Screenshot 5: Book Manager Page................................................................9
Screenshot 6: SQL Table <tblbooknumber>...............................................10
Screenshot 7: SQL Table <tblbooks>..........................................................11
Screenshot 8: SQL Table Borrow................................................................12
Screenshot 9: SQL Table <tblborrower>.....................................................12
Screenshot 10: Book Details.......................................................................13
Screenshot 11: Borrowed Books.................................................................13
Screenshot 12: Table tblreturn.....................................................................14
Screenshot 13: Unreturn Books...................................................................15
Screenshot 14: Returned Books..................................................................15
Screenshot 15: SQL Table <tblpayment>...................................................16
Screenshot 16: Payment Page.....................................................................16
Screenshot 17: Borrower’s Entry Page.......................................................17
Screenshot 18: SQL Table <tblcategory>....................................................18
Screenshot 19: Book Category Page...........................................................18
Screenshot 20: Manage Users Page............................................................19
Screenshot 21: UI........................................................................................20
Screenshot 22: SQL Table <tbllogs>...........................................................20
Screenshot 23: User Management Database...............................................22

x|Page
 Table of Figures
Figure 1: Use Case Diagram.........................................................................5
Figure 2: ER Diagram...................................................................................6

xi | P a g e
Chapter 1
Introduction
Introduction
In the realm of software development, the combination of C#, the .NET
Framework, ASP.NET, and SQL databases represents a powerhouse of
technologies that enable the creation of robust and feature-rich desktop
applications. Each element plays a distinct role in this process, contributing
to the development of versatile, scalable, and high-performance software
solutions. C# (pronounced "C-sharp") is a modern and versatile
programming language developed by Microsoft. Known for its simplicity
and elegance, C# is a pivotal component of the Microsoft .NET ecosystem.
Its object-oriented nature, rich standard libraries, and strong typing system
3 | P a g e make it an excellent choice for building a wide range of software
applications, including desktop applications. C# provides the foundation
for developing the logic and functionality of desktop applications.
The .NET Framework is a comprehensive development platform created by
Microsoft. It includes a vast collection of libraries, tools, and frameworks
that streamline the development, deployment, and execution of software
applications. With features like memory management, security, and support
for multiple programming languages (including C#), the .NET Framework
provides a stable and efficient environment for building desktop
applications. It serves as the backbone for executing C# code and ensures
cross-platform compatibility. While ASP.NET is primarily associated with
web development, it plays a significant role in creating desktop
applications through the .NET Framework. ASP.NET facilitates the
development of web-based interfaces and services that can be integrated
into desktop applications, enhancing their functionality and enabling
features like real-time data retrieval and collaboration. This versatility
allows developers to create hybrid desktop applications that combine the
power of local processing with the flexibility of web-based services. SQL
databases, such as Microsoft SQL Server or MySQL, are pivotal in desktop
application development for efficient data management. They provide a
structured and organized way to store, retrieve, and manage data critical to
the application's functionality. SQL databases enable developers to

xii | P a g e
implement features like data persistence, user authentication, and data
reporting in desktop applications. They ensure data integrity, security, and
scalability, making them an integral component of desktop software. In the
creation of desktop applications, C#, .NET Framework, ASP.NET, and SQL
databases work in concert. C# provides the logic and functionality of the
application, leveraging the extensive capabilities of the .NET Framework.
ASP.NET can be employed to integrate web-based features seamlessly into
the desktop application. SQL databases handle data storage and retrieval,
ensuring that the application operates efficiently and securely. Together,
these technologies empower developers to design desktop applications that
are powerful, user-friendly, and capable of meeting a diverse range of user
needs.

Motivation & Objectives

The problem that occurred before having computerized system includes: 1.
File lost When computerized system is not implemented file is always lost
because of 4 | P a g e human environment. 2. Sometimes due to some
human error there may be a loss of records. 3. File damaged When a
computerized system is not their file is always lost due to some accident
like spilling of water by some member on file accidentally. 4. Besides,
some natural disasters like floods or fires may also damage the files. 5.
Difficult to search record. When there is no computerized system there is
always difficulty in searching for records if the records are large in number.
6. Space consuming After the number of records becomes large the space
for physical storage of files and records also increases if no computerized
system is implemented. 7. Cost consuming as there is no computerized
system the to add each record paper will be needed which will increase the
cost for the management of library

Overview of the Project

The library management system is a project which aims in developing a
computerized system to maintain all the daily work of library. This project
has many features which are generally not available in normal library
management systems like the facility of user login and a facility of admin
login. It also has a facility of admin login through which the admin can
monitor the whole system. It has also a facility where students, after
logging in their accounts, can see the list of books issued and their issue

xiii | P a g e
date and return date. Overall, this project of ours is being developed to help
the students as well as the staff of the library to maintain the library in the
best way possible and also reduce human efforts. Chapter Wise Summary

Chapter wise Summary

xiv | P a g e
Chapter 2
Analysis & Design [1] [2] [3]
Functional Requirements
The project aims and objectives that will be achieved after completion of
this project are discussed in this subchapter. The aims and objectives are as
follows: The functional requirements of the Library Management System
project encompass the specific features and capabilities that the system
must possess to effectively meet its intended objectives. Here are the key
functional requirements:

 User Authentication and Authorization: The system should provide

secure user authentication and authorization mechanisms to ensure
that only authorized personnel can access and perform actions within
the system.
 Book Management: The system must allow librarians to add, edit,
and delete book records, including details such as title, author,
publication date, ISBN, and availability status. It should support the
categorization of books into genres or topics for efficient cataloging.
 Borrower Management: The system must enable the creation and
management of borrower profiles, including personal information
and contact details. It should keep track of borrower borrowing
history and penalties for overdue books.
 Transaction Handling: The system should facilitate book issuance,
return, and reissuance transactions, recording relevant details such as
transaction date and borrower information. It must calculate and
manage fines for overdue books. Inventory Reports: The system
should generate detailed inventory reports, offering insights into the
library's collection, lending history, and status of books. These
reports should be customizable and available in various formats,
such as PDF or Excel.
 Search and Retrieval: The system should provide efficient search and
retrieval functions, allowing users to find books based on criteria
such as title, author, ISBN, or category.
 User Roles and Access Control: The system must support different
user roles (e.g., librarian, administrator) with varying levels of access

xv | P a g e
 to system functionalities. It should enable role-based access control
to ensure data security.
 Data Integrity and Backup: The system should maintain data
integrity, ensuring that information is accurate and consistent. It
should include backup and restore mechanisms to safeguard against
data loss. User-Friendly Interface: The system must feature an
intuitive and user-friendly interface that is easy to navigate and use
for librarians and borrowers. Support for Multiple Libraries: If
applicable, the system should be capable 6 | P a g e of managing
multiple libraries or branches within a larger institution.
 Notifications and Alerts: The system may provide notifications and
alerts for due dates, late returns, or system updates, enhancing
communication with borrowers and staff.
 Scalability and Performance: The system should be designed to
handle a growing number of books, borrowers, and transactions
without a significant decrease in performance

Non-functional Requirements
Performance, Reliability, Scalability, Security, Usability, Compatibility,
Maintainability, Regulatory Compliance, Performance Monitoring, Data
Backup and Recovery, Load Testing, Response Time, Error Handling.

Use case Diagram

Figure 1: Use Case Diagram

xvi | P a g e
Entity Relationship Diagram

Figure 2: ER Diagram

xvii | P a g e
Chapter 3
Implementation [4] [1] [5]

Screenshot 1: User Login Page

Screenshot 2: Front Login Page

 Online book issue

 Request column for librarian for providing new books

xviii | P a g e
  Student login page where students can find books issued by him/her
and date of return.
 A search column to search availability of books.

Library Management System is an application which refers to library

systems which are generally small or medium in size. It is used by
the librarian to manage the library using a computerized system where
he/she can record various transactions like issue of books, return of
books, addition of new books, addition of new students etc. Books and
student maintenance modules are also included in this system which
would keep track of the students using the library and also a detailed
description of the books a library contains.
Screenshot 3: Database Attributes

With this computerized system there will be no loss of book record

or member record which generally happens when a non-
computerized system is used. All these modules are able to help
librarian to manage the library with more convenience and Ina more
efficient way as compared to library systems which are not
computerized.

xix | P a g e
Modules Description
Screenshot 4: Properties

The Picture Box control in Windows Forms serves as a versatile tool

for displaying images within applications. Its properties allow
developers to customize its behavior and appearance. The Image
property permits the assignment of images from various sources, such
as project resources, local files, or URLs. The Size Mode property

controls how the image fits within the Picture Box, offering options
like normal display, stretching to fit, automatic resizing of the Picture
Box, or centering with clipping. The Border Style property enables
developers to choose the visual style of the control's border, including
options like None, Fixed Single, and Fixed3D. Meanwhile, Image
Location facilitates image loading from local files or URLs.
Additional properties like Back Color, Enabled, and Visible allow for
background color customization, control over interactivity, and
visibility settings. These properties collectively empower developers
to create dynamic and visually appealing image displays tailored to
their Windows Forms applications' requirements.
Screenshot 5: Book Manager Page

xx | P a g e
 The "Books Manager" module is a cornerstone of the desktop
application, serving as a central hub for efficiently managing the
library's extensive collection of books. This integral component of
the library management system empowers librarians and
administrators with the ability to seamlessly save, delete, and
update book records within the database. It plays a pivotal role in
ensuring the accuracy and accessibility of the library's catalog,
enhancing the overall efficiency of library operations.

Implementation Details
 Book Record Creation: The "Books Manager" module allows for
the effortless addition of new book records into the database.
Librarians can input vital information such as book titles, authors,
publication dates, ISBN numbers, and availability status. This
functionality streamlines the process of cataloging new acquisitions,
ensuring that they are promptly made available to library patrons.

Screenshot 6: SQL Table <tblbooknumber>

 Update and Editing: One of the most significant advantages of

this module is its ability to facilitate quick and accurate updates to
existing book records. Librarians can easily modify details such as
author names, publication dates, or availability statuses, reflecting
changes in the library's collection accurately. This feature ensures
that the catalog remains up-to-date and precise.

 Deletion and Removal: In cases of book removal or loss, the

"Books Manager" module enables librarians to seamlessly delete

xxi | P a g e
 book records from the database. This function ensures that the
catalog reflects the most accurate inventory, preventing confusion
or unnecessary searches for missing books.

 Search and Retrieval: The module incorporates powerful search

and retrieval capabilities, allowing users to locate specific books
swiftly. Whether searching by title, author, ISBN, or any other
relevant criterion, this feature ensures that library patrons can
access desired books without delay.

Screenshot 7: SQL Table <tblbooks>

Book Details Module:

Accession No: The Accession Number serves as a unique identifier
for each copy of a book, making it invaluable for tracking
individual copies and ensuring that books are not duplicated or lost.
It simplifies the process of checking books in and out of the library.
Title: The Title field provides a quick reference to the book's name,
aiding both library staff and borrowers in identifying and locating
specific books. It helps maintain a well-organized and searchable
catalog.
Author: The Author field helps users identify books by a particular
writer, which is particularly useful when borrowers are searching
for books by their favorite authors or conducting research.
Date Publish: The Publication Date field assists in determining the
age and relevance of a book, crucial for librarians when managing
book collections and borrowers when choosing materials for their
needs.

Publisher: Publisher information can be essential in identifying

specific editions or versions of books. It is valuable for sourcing

xxii | P a g e
books and tracking book procurement.
Type of Books: Categorizing books by type or genre allows for
efficient organization and helps borrowers quickly locate books that
match their interests or requirements.
Borrowers Module:

Screenshot 8: SQL Table Borrow

Borrower ID: Borrower IDs are unique identifiers for individuals

using the library. They streamline the borrowing process, ensure
accurate record-keeping, and help prevent errors such as book mix-
ups.

Screenshot 9: SQL Table <tblborrower>

Name: Names are fundamental for personalization and identifying

borrowers. Library staff can address borrowers by name and
personalize their interactions.
Year/Section: In an educational context, Year/Section information
aids in sorting borrowers by academic level or class, allowing
libraries to track reading materials specific to different grade levels.
Purpose: Understanding the purpose behind borrowing a book can
help librarians recommend suitable materials and track the library's
impact. It's particularly valuable in educational libraries where

xxiii | P a g e
purpose might include coursework, research, or leisure reading.

Screenshot 10: Book Details

Screenshot 11: Borrowed Books

Return Books Page:

The "Returned Books Page" is a crucial component within a library or

book management system, designed to meticulously document the

xxiv | P a g e
 return of books by borrowers. The inclusion of specific fields serves
multiple essential purposes. The "Borrower ID" field ensures precise
attribution of the returned book to the respective borrower, facilitating
accurate record-keeping and lending history tracking. This feature is
invaluable for managing overdue books, calculating
fines, and gaining insights into borrower behavior. The "Book Title"
field plays a pivotal role in swiftly identifying the book that has been
returned, streamlining cataloging, shelving, and inventory management.
Moreover, the "Author" field offers an additional layer of information
for categorization and aiding borrowers in discovering other works by
the same author. Finally, the "Description" field serves as a repository
for pertinent details regarding the returned book, encompassing its
condition, any damages, missing pages, or other noteworthy remarks.
Such information is indispensable for assessing the book's state and
determining any necessary actions, such as repairs or replacements. In
sum, the "Returned Books Page" not only ensures the accurate
recording of book returns but also contributes to the systematic
organization of the library's collection and the preservation of the books
therein.
Screenshot 12: Table tblreturn

This table meticulously records vital information including return dates,

transaction particulars, and borrower identification. Its role is central to
xxv | P a g e
maintaining precise library operations and ensuring accurate record-
keeping of book returns.
Screenshot 13: Unreturn Books

The "Unreturned Books" page within the Library Management System

presents a comprehensive list of books that are currently overdue and have
not been returned by borrowers within the stipulated timeframe. This page
is a valuable tool for librarians and administrators, facilitating the efficient
management of late returns and associated penalties, thereby ensuring the
integrity of the library's collection.

Screenshot 14: Returned Books

The "Returned Books" page in the Library Management System

provides a succinct record of books that have been successfully
returned by borrowers. It serves as an essential reference for
librarians and administrators, aiding in the verification of completed
transactions and assisting with inventory management, ultimately
contributing to the overall efficiency of library operations.

xxvi | P a g e
 Screenshot 15: SQL Table <tblpayment>

The SQL table "tblpayment" is a crucial component of the Library

Management System, responsible for tracking and managing
financial transactions related to overdue books. It records essential
details such as payment amounts, transaction dates, and borrower
information, ensuring accurate tracking of penalties and fees
associated with overdue book returns.

Screenshot 16: Payment Page

xxvii | P a g e
The "Payment Page" within the Library Management System serves as a
dedicated platform for processing and recording financial transactions
related to overdue book returns. It allows librarians and administrators to
efficiently handle penalty payments, updating borrower accounts and
maintaining the financial integrity of the library system.

Screenshot 17: Borrower’s Entry Page

The "Borrower's Entry Page" is a fundamental component of the

Library Management System, providing a user-friendly interface for
librarians and administrators to add, edit, and manage borrower
profiles. It allows for the input and maintenance of borrower details,
including personal information, contact information, and borrowing
history, ensuring a comprehensive and organized database of library
patrons.

xxviii | P a g e
 Screenshot 18: SQL Table <tblcategory>

The SQL table "tblcategory" is an integral part of the Library

Management System, responsible for categorizing and organizing
books within the library. It stores information related to book
categories, genres, or topics, enabling efficient cataloging and
retrieval of books based on their thematic attributes, ultimately
enhancing the user experience.

Screenshot 19: Book Category Page

xxix | P a g e
A "Screenshot: Book Categories Page" offers a visual representation
of the section within the Library Management System where book
categories are managed. This page provides the ability to add, edit,
and organize book categories, simplifying the cataloging process and
enhancing user navigation by enabling structured categorization of
library resources.

Screenshot 20: Manage Users Page

The "Manage Users Page" within the Library Management System is

a central administrative tool that facilitates the creation, modification,
and oversight of user accounts. It empowers librarians and
administrators to manage access, roles, and privileges, ensuring
secure and controlled interactions with the system, enhancing data
security, and optimizing administrative efficiency.

xxx | P a g e
 Screenshot 21: UI

Screenshot 22: SQL Table <tbllogs>

The SQL table "tbllogs" is a crucial component in the Library

Management System, responsible for recording and storing log data
related to system activities and user interactions. It includes
information such as timestamps, user actions, and relevant details,
offering an essential resource for system monitoring, auditing, and
troubleshooting.

xxxi | P a g e
Software Tools used

xxxii | P a g e
Chapter 4
Test results/experiments/verification
Testing
Results
The result of a library or book management system project is a
comprehensive, user-friendly platform that streamlines library
operations. It includes user authentication for librarians and
borrowers, a catalog management system with detailed book records,
a borrowing and returns system with due date calculations,
reservation and request functionality, user history tracking,
notifications, reports and analytics, robust security measures, and
responsive design for accessibility across devices. This system
enhances the library experience by facilitating easy book discovery,
efficient inventory management, and a smooth borrowing process,
ultimately benefiting library staff and patrons while ensuring the
security and integrity of user data and library resources.

Screenshot 23: User Management Database

xxxiii | P a g e
Verification

xxxiv | P a g e
Chapter 5
Conclusion & Future Scope
The C# Library Management System represents a significant leap forward
in the realm of library management, ushering in a new era of efficiency
and precision. Developed using Visual Studio 2022 and the C#
programming language, and with the solid foundation of a MySQL
database seamlessly integrated with the XAMPP server environment, this
project has successfully redefined the traditional library management
paradigm. The system's comprehensive feature set, including book
cataloging, borrower administration, transaction tracking, and user
management, empowers librarians and administrators to oversee and
optimize every facet of library operations. Notably, its capacity for precise
book categorization streamlines the cataloging process and enables a
seamless user experience. One of the
system's standout achievements is its user-friendly interface, providing
real-time insights through detailed inventory reports. By automating
routine tasks and ensuring data integrity, it significantly reduces the need
for extensive library staff, thus improving overall operational efficiency.
In conclusion, the C# Library Management System is not just a software
application; it's a powerful tool that empowers librarians to offer their
patrons a modern, efficient, and seamless library experience. Its impact
extends to educational institutions and organizations, providing an asset
for elevating library management capabilities. As libraries evolve in the
digital age, this system stands as a beacon of innovation and efficiency,
ensuring that the world of knowledge remains accessible and well-
organized for all.
In conclusion, this project aimed to achieve query-focused multi-document
summarization using the mT5 transformer model. We utilized web scraping
to collect data related to a specific query, processed the data to extract
relevant information, and trained the mT5 model to generate a summary of
the documents related to the query. The generated summary was displayed
on a web page using the Flask web framework. Overall, the project was
successful in achieving the goal of query-focused multi-document
summarization. The mT5 model was able to generate coherent and relevant
summaries based on the input query and related documents. The

xxxv | P a g e
visualization of frequency matrices and co-occurrence plots also aided in
the selection of the most relevant information for summary generation. The
project could be further improved by incorporating more advanced
techniques for data processing, such as entity recognition and sentence
clustering. Additionally, the web page could be designed more aesthetically
to improve user experience.

xxxvi | P a g e
Chapter 6
References [6] [7] [2] [1] [8] [4] [3] [5]

[1] "BigInteger Structure (System.Numerics)," , . [Online]. Available:

http://msdn.microsoft.com/en-us/library/system.numerics.biginteger(v=
vs.110).aspx. [Accessed 18 12 2024].

[2] M. . Library, "MRU Library Website: Library Homepage: Home," ,

2017. [Online]. Available: https://mtroyal.ca/library/index.htm.
[Accessed 18 12 2024].

[3] E. . Parry, "The Benefits of Using Technology in Human Resource

Management," , 2009. [Online]. Available:
https://igi-global.com/chapter/benefits-using-technology-human-
resource/13216. [Accessed 18 12 2024].

[4] "Task Parallel Library (TPL)," , . [Online]. Available:

http://msdn.microsoft.com/en-us/library/dd460717.aspx. [Accessed 18
12 2024].

[5] "Using Encrypting File System," , . [Online]. Available:

https://technet.microsoft.com/en-us/library/bb457116.aspx. [Accessed
18 12 2024].

[6] "Koha - Open Source ILS - Integrated Library System," , . [Online].

Available: http://koha.org/. [Accessed 18 12 2024].

[7] "Visual C# (MSDN)," , . [Online]. Available:

https://msdn.microsoft.com/en-us/library/kx37x362.aspx. [Accessed 18
12 2024].

[8] "Microsoft Management Console – Overview," , . [Online]. Available:

https://technet.microsoft.com/en-us/library/bb742441.aspx. [Accessed
18 12 2024].

Chapter 7
xxxvii | P a g e
Appendix Code
Form1.cs
using System;
using
System.Collections.Generic;
using
System.ComponentModel;
using System.Data;
using
System.Drawing;
using
System.Linq;
using
System.Text;
using
System.Threading.Tasks;
using
System.Windows.Forms;

namespace LibrarySystem
{
public partial class Form1 : Form
{
public Form1()
{
InitializeComponent();
}
public void enabled_menu()
{
ts_login.Text = "Logout";
ts_books.Enabled = true;
ts_transaction.Enabled =
true; ts_borrower.Enabled
= true;
ts_categories.Enabled =
true; ts_users.Enabled =
true; ts_reports.Enabled =
true; ts_logs.Enabled =
true;
ts_login.Image = flroperties.Resources.log_close;
}

public void disabled_menu()

{

xxxviii | P a g e
 ts_login.Text = "Login";
ts_books.Enabled = false;
ts_transaction.Enabled =
false; ts_borrower.Enabled
= false;
ts_categories.Enabled =
false; ts_users.Enabled =
false; ts_reports.Enabled =
false; ts_logs.Enabled =
false;
ts_login.Image = flroperties.Resources.log_open;
}

private void Form1_Load(object sender, EventArgs e)

{
disabled_menu();
}
private void ts_books_Click(object sender, EventArgs e)

{
Form frm = new
frmBooks();
frm.ShowDialog();
}
private void ts_BorrowItem_Click(object
sender, EventArgs e)
{
Form frm = new
frmBorrow();
frm.ShowDialog();
}

private void ts_returnItem_Click(object

sender, EventArgs e)
{
Form frm = new
frmReturned();
frm.ShowDialog();
}
private void ts_overdueItem_Click(object sender,
EventArgs e)
{
Form frm = new
frmOverdue();

xxxix | P a g e
 frm.ShowDialog();
}

private void ts_borrower_Click(object sender,

EventArgs
e)
{
Form frm = new
frmBorrower();
frm.ShowDialog();
}
private void ts_categories_Click(object
sender, EventArgs e)
{
Form frm = new
frmCategories();
frm.ShowDialog();
}

private void ts_users_Click(object sender, EventArgs

e)
{
Form frm = new frmUser();
frm.ShowDialog();
}

private void ts_reports_Click(object sender, EventArgs

e)
{

Form frm = new

frmReport();
frm.ShowDialog();
}

private void ts_logs_Click(object sender, EventArgs e)

{
Form frm = new frmLogs();
frm.ShowDialog();
}

private void ts_login_Click(object sender, EventArgs

xl | P a g e
 e)
{
Form frm = new frmLogin(this);

if (ts_login.Text == "Login")
{
frm.ShowDialog();
}
else
{
ts_login.Text =
"Login";
disabled_menu();
}
}
private void pictureBox1_Click(object sender,
EventArgs
e)
{

}
}
}

FormBorrower.cs
using System;
using
System.Collections.Generic;
using
System.ComponentModel;
using System.Data;
using
System.Drawing;
using
System.Linq;
using
System.Text;
using
System.Threading.Tasks;
using
System.Windows.Forms;
using
LibrarySystem.Includes;

xli | P a g e
using
LibrarySystem.flroperties;
using System.IO;

namespace LibrarySystem
{
public partial class frmBorrower : Form

{
public frmBorrower()
{
InitializeComponent();
}
SQLConfig config = new SQLConfig();
usableFunction funct = new usableFunction();
string sql;
int inc, maxrow;

private void navigate_records(int inc)

{
sql = "SELECT BorrowerId FROM tblborrower";
config.singleResult(sql);
if (config.dt.Rows.Count > 0)
{
txt_bid.Text =
config.dt.Rows[inc].Field<string>(0);
}
}
private void btn_ ew_Click(object sender, EventArgs e)
{
funct.clearTxt(this);
sql = "SELECT BorrowerId,`Firstname`,
`Lastname`,
`Middle ame`, `Address`, `Sex`, `Contact o`, `CourseYear`
as 'Course/Year' FROM `tblborrower` W ERE
Stats='Active'";
config.Load_ResultList(sql,
dtg_ABorrowLists);
flictureBox1.ImageLocation = "";
btn_delete.Enabled = false;
sql = "SELECT * FROM
`tblborrower`W ERE
Stats='Active'";
config.singleResult(sql);

xlii | P a g e
 if (config.dt.Rows.Count > 0)
{
maxrow = config.dt.Rows.Count - 1;
}

inc = 0;
}

private void frmBorrower_Load(object sender, EventArgs

e)
{
btn_ ew_Click(sender, e);
}
private void txt_bid_TextChanged(object sender,
EventArgs e)

{
sql = "SELECT * FROM `tblborrower` W ERE
`BorrowerId` = '" + txt_bid.Text + "'";
config.singleResult(sql);

if(config.dt.Rows.Count > 0)
{
txt_fname.Text =
config.dt.Rows[0].Field<string>("Firstname");
txt_lname.Text =
config.dt.Rows[0].Field<string>("Lastname");
txt_mname.Text =
config.dt.Rows[0].Field<string>("Middle ame");
rch_address.Text =
config.dt.Rows[0].Field<string>("Address");
txtContact.Text =
config.dt.Rows[0].Field<string>("Contact o");
txtCourse.Text =
config.dt.Rows[0].Field<string>("CourseYear");
flictureBox1.ImageLocation =
Application.Startupflath + "\\Borrowerflhoto\\" +
"Female")
config.dt.Rows[0].Field<string>("Borrowerflhoto");
if (config.dt.Rows[0].Field<string>("Sex") ==
{
rdio_female.Checked = true;
}

xliii | P a g e
else
{
rdio_male.Checked = true;
}
btn_delete.Enabled = true;

}
else
{
btn_delete.Enabled =
false; clearme();
}
}
private void clearme()
{
txt_fname.Clear();
txt_lname.Clear();
txt_mname.Clear();
rch_address.Clear();
txtContact.Clear();
txtCourse.Clear();
txtflhoto.Clear();
}
private void btn_save_Click(object sender, EventArgs
e)
{

if( txt_bid.Text == ""

|| txt_fname.Text == "" || txt_lname.Text == ""
|| txt_mname.Text == "" || txtCourse.Text == "" ){
funct.emptymessage();
}
string gender;
if (rdio_female.Checked)
{
gender = "Female";
}
else
{
gender = "Male";
}

xliv | P a g e
 sql = "SELECT * FROM `tblborrower` W ERE
`BorrowerId`=" + txt_bid.Text;
config.singleResult(sql);
if (config.dt.Rows.Count > 0)
{
sql = "update tblborrower set
`Firstname`='" +
txt_fname.Text
+ "', `Lastname`='" + txt_lname.Text
+ "',
`Middle ame`='" + txt_mname.Text
+ "', `Address`='" + rch_address.Text
+
"', `Sex`='" + gender
+ "', `Contact o` ='" +
txtContact.Text +
"', `CourseYear`='" + txtCourse.Text.ToUpper()
+ "', `Borrowerflhoto`='" +
flath.GetFile ame(flictureBox1.ImageLocation) + "',
`BorrowerType`='Student' where `BorrowerId`='" + txt_bid.Text
+ "'";
config.Execute_CUD(sql, "error to execute the
query", "Borrower has been updated in the database.");
}
else
{
sql = "insert into tblborrower (`BorrowerId`,
`Firstname`, `Lastname`, `Middle ame`, `Address`, "
+ "`Sex`, `Contact o`, `CourseYear`,
`Borrowerflhoto`,`BorrowerType`,Stats)"
+ "values ('" + txt_bid.Text +
"','" + txt_fname.Text + "','" + txt_lname.Text

rch_address.Text
+ "','" + txt_mname.Text + "','" +
+ "','" + gender + "','" +
txtContact.Text + "','" + txtCourse.Text
+ "','" +
flath.GetFile ame(flictureBox1.ImageLoca
tion) + "','Student','Active')";
config.Execute_CUD(sql, "error to execute the
query", " ew borrower has been added in the database.");

}
if(txtflhoto.Text!= "")
{

xlv | P a g e
 File.Copy(txtflhoto.Text,
Application.Startupflath
+ "\\Borrowerflhoto\\" +
flath.GetFile ame(flictureBox1.ImageLocation),t
rue);
}
btn_ ew_Click(sender, e);

}
private void flictureBox1_Click(object sender,
EventArgs
e)
{
//With OpenFileDialog1

// 'C ECK T E SELECTED FILE IF IT EXIST

OT ERWISE
T E DIALOG BOX WILL DISflLAY A WAR I G.
OpenFileDialog1.CheckFileExists = true;

// 'C ECK T E SELECTED flAT IF IT

EXIST OT ERWISE T E DIALOG BOX WILL DISflLAY A
WAR I G.
OpenFileDialog1.CheckflathExists = true;

// 'GET A D SET T E DEFAULT EXTE SIO

OpenFileDialog1.DefaultExt = "jpg";

// 'RETUR T E FILE LI KED TO T E L K

FILE
OpenFileDialog1.DereferenceLinks = true;

// 'SET T E FILE AME TO EMflTY

OpenFileDialog1.File ame = "";

// 'FILTERI G T E FILES
OpenFileDialog1.Filter = "(*.jpg)|*.jpg|(*.png)|
*.png|(*.jpg)|*.jpg|All files|*.*";

// 'SET T IS FOR O E FILE SELECTIO O

LY.
OpenFileDialog1.Multiselect = false;

// 'SET T IS TO flUT T E CURRE T

FOLDER BACK TO W ERE IT AS STARTED.
OpenFileDialog1.RestoreDirectory = true;

xlvi | P a g e
 // 'SET T E TITLE OF T E DIALOG BOX.
OpenFileDialog1.Title = "Select a file to open";
// 'ACCEflT O LY T E VALID WI 32 FILE
AMES.
OpenFileDialog1.Validate ames = true;

if (OpenFileDialog1.ShowDialog() ==
DialogResult.OK)
{
txtflhoto.Text = OpenFileDialog1.File ame;
flictureBox1.ImageLocation =
OpenFileDialog1.File ame;
flictureBox1.SizeMode =
flictureBoxSizeMode.StretchImage;
}

private void btn_delete_Click(object sender, EventArgs

e)
{
if (MessageBox.Show("Are you sure you want to
delete
this borrowero", "Delete", MessageBoxButtons.Yes o,
MessageBoxIcon.Warning) == DialogResult.Yes) {
sql = "UflDATE `tblborrower` SET
otActive' W ERE `BorrowerId` ='" +
dtg_ABorrowLists.CurrentRow.Cells[0].Value + "'";
config.Execute_Query(sql);

MessageBox.Show("Borrower has been

deleted in the database.", "Success",
MessageBoxButtons.OK);
btn_ ew_Click(sender, e);
}
}

private void btnClose_Click(object sender, EventArgs

e)
{
this.Close();
}

xlvii | P a g e
 private void btn_last_Click(object sender, EventArgs
e)
{
inc = maxrow;

navigate_records(inc);
}
private void btn_prev_Click(object sender, EventArgs
e)
{
if(inc == 0)
{
MessageBox.Show("First Records.", "Info",
MessageBoxButtons.OK, MessageBoxIcon.Information);
}
else if(inc <= maxrow)
{
inc = inc - 1;
navigate_records(inc);
}
}
private void btn_next_Click(object sender, EventArgs e)
{
if (inc == maxrow)
{
MessageBox.Show("Last Records.", "Info",
MessageBoxButtons.OK, MessageBoxIcon.Information);
}
else if (inc >= 0)
{
inc = inc + 1;
navigate_records(inc);
}
}
private void dtg_ABorrowLists_CellClick(object
sender, DataGridViewCellEventArgs e)
{
txt_bid.Text =
dtg_ABorrowLists.CurrentRow.Cells[0].Value.ToString();

xlviii | P a g e
 }

private void btn_first_Click(object sender, EventArgs

e)
{
inc = 0;
navigate_recor
ds(inc);
}
}
}

xlix | P a g e