Project Report

On

ONLINE LIBRARY MANAGEMENT

SYSTEM

Submitted By:
Your Name

In partial fulfillment for the award of the degree of

Your Degree

In

Your College Name

 ACKNOWLEDGEMENT

We take this occasion to thank God, almighty for blessing us with his grace and

taking our endeavor to a successful culmination. We extend our sincere and

heartfelt thanks to our esteemed guide, ABC, for providing us with the right

guidance and advice at the crucial junctures and for showing me the right way. We

also take this opportunity to express a deep sense of gratitude to our class

coordinators, XYZ and XXX for their cordial support, valuable suggestions and

guidance. We extend our sincere thanks to our respected Head of the division

Name Here, for allowing us to use the facilities available. We would like to thank

the other faculty members also, at this occasion. Last but not the least, we would

like to thank our friends and family for the support and encouragement they have

given us during the course of our work.

 TABLE OF CONTENTS

ABSTRACT

1. INTRODUCTION
1.1 PROJECT AIMS AND OBJECTIVES
1.2 BACKGROUND OF PROJECT
1.3 OPERATION ENVIRONMENT

2. SYSTEM ANALYSIS
2.1 SOFTWARE REQUIREMENT SPECIFICATION
2.2 EXISTING VS PROPOSED
2.3 SOFTWARE TOOL USED

3. SYSTEM DESIGN
3.1 TABLE DESIGN
3.2 USE CASE DIGRAM & CLASS DIAGRAAM
3.3 DATA FLOW DIAGRAM’S
3.4 ER DIAGRAM

4. SYSTEM IMPLEMENTATION
4.1 SCREEN SHOTS

5. SYSTEM TESTING
5.1 UNIT TESTING
5.2 INTEGRATION TESTING
6. CONCLUSION & FUTURE SCOPE
7. REFERENCES
 ABSTRACT

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
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 student after logging in their accounts can see list of books issued and its
issue date and return date.

Overall, this project of ours is being developed to help the students as well as
staff of library to maintain the library in the best way possible and also reduce the
human efforts.
 CHAPTER 1
INTRODUCTION

This chapter gives an overview about the aim, objectives, background

and operation environment of the system.

1.1 PROJECT AIMS AND OBJECTIVES

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:

 Online book issue

 Request column for librarian for providing new books
 Student login page where student can find books issued by him/her and
date of return.
 A search column to search availability of books
1.2 BACKGROUND OF PROJECT

Library Management System is an application which refers to library systems

which are generally small or medium in size. It is used by 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
about the books a library contains. 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 in a more efficient way as compared to library systems which
are not computerized.
1.3 OPERATION ENVIRONMENT

PROCESSOR INTEL CORE PROCESSOR OR BETTER

PERFORMANCE

OPERATING
SYSTEM WINDOWS Or ANY EQUIVALENT OS

MEMORY 1GB RAM OR MORE

HARD DISK SPACE MINIMUM 3 GB FOR DATABASE USAGE FOR

FUTURE

DATABASE MY SQL
 CHAPTER 2

SYSTEM ANALYSIS

In this chapter, we will discuss and analyze about the developing process of Library

Management System including software requirement specification (SRS) and

comparison between existing and proposed system. The functional and

nonfunctional requirements are included in SRS part to provide complete description

and overview of system requirement before the developing process is carried out.

Besides that, existing vs proposed provides a view of how the proposed system will

be more efficient than the existing one.

2.1 SOFTWARE REQUIREMENT SPECIFICATION

2.1.1 GENERAL DESCRIPTION

PRODUCT DESCRIPTION:

Library Management System is a computerized system which helps user (librarian)

to manage the library daily activity in electronic format. It reduces the risk of paper
work such as file lost, file damaged and time consuming.

It can help user to manage the transaction or record more effectively and time-
saving.
PROBLEM STATEMENT:

The problem occurred before having computerized system includes:

 File lost
When computerized system is not implemented file is always lost
because of human environment. Sometimes due to some human error
there may be a loss of records.
 File damaged when a computerized system is not there file is always
lost due to some accident like spilling of water by some member on
file accidentally. Besides some natural disaster like floods or fires
may also damage the files.
 Difficult to search record
When there is no computerized system there is always a difficulty in
searching of records if the records are large in number.
 Space consuming
After the number of records become large the space for physical
storage of file and records also increases if no computerized system is
implemented.
 Cost consuming
As there is no computerized system to add each record paper will be
needed which will increase the cost for the management of library.
2.1.2 SYSTEM OBJECTIVES
 Improvement in control and performance
The system is developed to cope up with the current issues and problems
of library
.The system can add user, validate user and is also bug free.
 Save cost
After computerized system is implemented less human force will be
required to maintain the library thus reducing the overall cost.
 Save time
Librarian is able to search record by using few clicks of mouse and
few search keywords thus saving his valuable time.
  Option of online Notice board
Librarian will be able to provide a detailed description of workshops
going in the college as well as in nearby colleges
 Lecture Notes
Teacher have a facility to upload lectures notes in a pdf file having
size not more than 10mb

2.1.3 SYSTEM REQUIREMENTS

2.1.3.1 NON FUNCTIONAL REQUIREMENTS
 Product Requirements

EFFICIENCY REQUIREMENT
When a library management system will be implemented librarian and user will
easily access library as searching and book transaction will be very faster.

RELIABILITY REQUIREMENT
The system should accurately perform member registration, member, validation,
report generation, book transaction and search.

USABILITY REQUIREMENT
The system is designed for a user friendly environment so that student and staff
of library can perform the various tasks easily and in an effective way.

ORGANIZATIONAL REQUIREMENT
IMPLEMENTATION REQUIREMNTS
In implementing whole system it uses html in front end with python as server
side scripting language which will be used for database connectivity and the
backend i.e. the database part is developed using MySQL.

DELIVERY REQUIREMENTS
The whole system is expected to be delivered in six months of time with a
weekly evaluation by the project guide.
2.1.3.2 FUNCTIONAL REQUIREMENTS

1. NORMAL USER

1.1 USER LOGIN

Description of feature
This feature used by the user to login into system. They are required to enter user
id and password before they are allowed to enter the system .The user id and
password will be verified and if invalid id is there user is allowed to not enter the
system.

Functional requirements

-user id is provided when they register

-The system must only allow user with valid id and password to enter the system
-The system performs authorization process which decides what user level can
access to.
-The user must be able to logout after they finished using system.

1.2 REGISTER NEW USER

Description of feature
This feature can be performed by all users to register new user to create account.

Functional requirements

-System must be able to verify information

-System must be able to delete information if information is wrong
Admin Features

 Admin Dashboard
 Admin can add/update/ delete category
 Admin can add/update/ delete author
 Admin can add/update/ delete books
 Admin can issue a new book to student and also update the details when
student return book
 Admin can search student by using their student ID
 Admin can also view student details
 Admin can change own password

Students-

 Student can register yourself and after registration they will get studentid
 After login student can view own dashboard.
 Student can update own profile.
 Student can view issued book and book return date-time.
 Student can also view the available books in the library.
 Student can also change own password.
 Student can also recover own password.

2.1.4 SOFTWARE AND HARDWARE REQUIREMENTS

This section describes the software and hardware requirements of the system
2.1.4.1 SOFTWARE REQUIREMENTS

Operating system- Windows 7 is used as the operating system as it is stable and

supports more features and is more user friendly

Database MYSQL-MYSQL is used as database as it easy to maintain and retrieve

records by simple queries which are in English language which are easy to
understand and easy to write.
Development tools and Programming language- HTML is used to write the whole
code and develop webpages with css, java script for styling work and
python(Django framework) for sever side scripting.

2.1.4.2 HARDWARE REQUIREMENTS

Intel core i5 2nd generation is used as a processor because it is faster than other
processors and provide reliable and stable and we can run our pc for longtime. By
using this processor, we can keep on developing our project without any worries.

Ram 1 GB is used as it will provide fast reading and writing capabilities and will in
turn support in processing

2.2 EXISTING VS PROPOSED SYSTEM

i. Existing system does not have any facility of student login

whereas proposed system will have a facility of student login.
ii. If one is not very careful then there is a possibility of issuing more
than one book to a user whereas proposed system resolve this
issues.
iii. There is a possibility of issuing a book to a user, whose
membership is not but in proposed system it is not possible because
it provide unique student ID.
iv. When a user requests for the book, one has to physically check for
the presence of a book in the library whereas proposed system will
check the book availability in single click.
v. Daily keeping a manual record of changes taking place in the
library such as book being issued, book being returned etc. can
become cumbersome if the Library size is bigger but in proposed
system it easy to maintain and avoid manual work.
vi. Existing system does not has any facility for book request and
suggestions where as in proposed system after logging in to
 their accounts student can request books as well as provide
suggestions to improve library

2.3 SOFTWARE TOOLS USED

The whole Project is divided in two parts the front end and the back end.

2.3.1 Front end

The front end is designed using of html , Python, css, Java script, Django.
HTML- HTML or Hyper Text Markup Language is the main markup language
for creating web pages and other information that can be displayed in a web
browser.HTML is written in the form of HTML elements consisting of tags
enclosed in angle brackets (like <html>), within the web page content. HTML tags
most commonly come in pairs like <h1> and </h1>, although some tags represent
empty elements and so are unpaired, for example <img>. The first tag in a pair is
the start tag, and the second tag is the end tag (they are also called opening tags
and closing tags). In between these tags web designers can add text, further tags,
comments and other types of text-based content. The purpose of a web browser is
to read HTML documents and compose them into visible or audible web pages.
The browser does not display the HTML tags, but uses the tags to interpret the
content of the page.HTML elements form the building blocks of all websites.
HTML allows images and objects to be embedded and can be used to create
interactive forms. It provides a means to create structured documents by denoting
structural semantics for text such as headings, paragraphs, lists, links, quotes and
other items. It can embed scripts written in languages such as JavaScript which
affect the behavior of HTML web pages.
CSS- Cascading Style Sheets (CSS) is a style sheet language used for
describing the look and formatting of a document written in a markup language.
While most often used to style web pages and interfaces written in HTML and
XHTML, the language can be applied to any kind of XML document, including
plain XML, SVG and XUL. CSS is a cornerstone specification of the web and
almost all web pages use CSS style sheets to describe their presentation.CSS is
designed primarily to enable the separation of document content from document
presentation, including elements such as the layout, colors, and fonts. This
separation can improve content accessibility, provide more flexibility and
control in the specification
of presentation characteristics, enable multiple pages to share formatting, and
reduce complexity and repetition in the structural content (such as by allowing for
table less web design).CSS can also allow the same markup page to be presented in
different styles for different rendering methods, such as on-screen, in print, by
voice (when read out by a speech-based browser or screen reader) and on Braille-
based, tactile devices. It can also be used to allow the web page to display
differently depending on the screen size or device on which it is being viewed.
While the author of a document typically links that document to a CSS file, readers
can use a different style sheet, perhaps one on their own computer, to override the
one the author has specified. However if the author or the reader did not link the
document to a specific style sheet the default style of the browser will be
applied.CSS specifies a priority scheme to determine which style rules apply if
more than one rule matches against a particular element. In this so-called cascade,
priorities or weights are calculated and assigned to rules, so that the results are
predictable.

JAVA SCRIPT- JavaScript (JS) is a dynamic computer programming language. It

is most commonly used as part of web browsers, whose implementations allow
client-side scripts to interact with the user, control the browser, communicate
asynchronously, and alter the document content that is displayed. It is also being
used in server-side programming, game development and the creation of desktop
and mobile applications. JavaScript is a prototype-based scripting language with
dynamic typing and has first-class functions. Its syntax was influenced by C.
JavaScript copies many names and naming conventions from Java, but the two
languages are otherwise unrelated and have very different semantics. The key
design principles within JavaScript are taken from the Self and Scheme
programming languages. It is a multi-paradigm language, supporting object-
oriented, imperative, and functional programming styles. The application of
JavaScript to use outside of web pages—for example, in PDF documents, site-
specific browsers, and desktop widgets—is also significant. Newer and faster
JavaScript VMs and platforms built upon them (notably Node.js) have also
increased the popularity of JavaScript for server-side web applications. On the
client side, JavaScript was traditionally implemented as An interpreted language
but just-in-time compilation is now performed by recent (post-2012) browsers.

PYTHON- Python is an interpreted, object-oriented, high-level programming

language with dynamic semantics. Its high-level built in data structures,
combined with dynamic typing and dynamic binding, make it very attractive for
Rapid Application Development, as well as for use as a scripting or glue language
to connect existing components together. Python's simple, easy to learn syntax
emphasizes readability and therefore reduces the cost of program maintenance.
Python supports modules and packages, which encourages program modularity
and code reuse. The Python interpreter and the extensive standard library are
available in source or binary form without charge for all major platforms, and can
be freely distributed.
Often, programmers fall in love with Python because of the increased
productivity it provides. Since there is no compilation step, the edit-test-debug
cycle is incredibly fast. Debugging Python programs is easy: a bug or bad input
will never cause a segmentation fault. Instead, when the interpreter discovers an
error, it raises an exception. When the program doesn't catch the exception, the
interpreter prints a stack trace. A source level debugger allows inspection of local
and global variables, evaluation of arbitrary expressions, setting breakpoints,
stepping through the code a line at a time, and so on. The debugger is written in
Python itself, testifying to Python's introspective power. On the other hand, often
the quickest way to debug a program is to add a few print statements to the
source: the fast edit-test-debug cycle makes this simple approach very effective.

Django- Django is a Python framework that makes it easier to create web sites
using Python.

Django takes care of the difficult stuff so that you can concentrate on building your
web applications.

Django emphasizes reusability of components, also referred to as DRY (Don't

Repeat Yourself), and comes with ready-to-use features like login system, database
connection and CRUD operations (Create Read Update Delete).

Django is especially helpful for database driven websites.

How does Django Work?

Django follows the MVT design pattern (Model View Template).

 Model - The data you want to present, usually data from a database.
 View - A request handler that returns the relevant template and content -
based on the request from the user.
 Template - A text file (like an HTML file) containing the layout of the web
page, with logic on how to display the data.

Model

The model provides data from the database.

In Django, the data is delivered as an Object Relational Mapping (ORM), which is

a technique designed to make it easier to work with databases.

The most common way to extract data from a database is SQL. One problem with
SQL is that you have to have a pretty good understanding of the database structure
to be able to work with it.
Django, with ORM, makes it easier to communicate with the database, without
having to write complex SQL statements.

The models are usually located in a file called models.py.

View

A view is a function or method that takes http requests as arguments, imports the
relevant model(s), and finds out what data to send to the template, and returns the
final result.

The views are usually located in a file called views.py.

Template

A template is a file where you describe how the result should be represented.

Templates are often .html files, with HTML code describing the layout of a web
page, but it can also be in other file formats to present other results, but we will
concentrate on .html files.

2.3.2 BACK END- The back end is designed using MySQL which is used to
design the databases.

MYSQL- MySQL ("My S-Q-L", officially, but also called "My Sequel") is (as of
July 2013) the world's second most widely used open-source relational database
management system (RDBMS). It is named after co-founder Michael Widenius
daughter, My. The SQL phrase stands for Structured Query Language. The
MySQL development project has made its source code available under the terms of
the GNU General Public License, as well as under a variety of proprietary

agreements. MySQL was owned and sponsored by a single for-profit firm, the
Swedish company MySQL AB, now owned by Oracle Corporation. MySQL is a
popular choice of database for use in web applications, and is a central component
of the widely used LAMP open-source web application software stack (and other
'AMP' stacks). LAMP is an acronym for "Linux, Apache, MySQL,
Perl/PHP/Python." Free-software-open-source projects that require a full-featured
database management system often use MySQL. For commercial use, several paid
editions are available, and offer additional functionality. Applications which use
MySQL databases. include: TYPO3, MODx, Joomla, WordPress, phpBB, MyBB,
Drupal and other software. MySQL is also used in many high-profile, large-scale
websites, including Wikipedia, Google (though not for searches), Facebook,
Twitter, Flickr, and YouTube.
 CHAPTER 3
SYSTEM DESIGN

3.1 TABLE DESIGN

“Online Library Management System” contains 15 MySQL tables(In this MySQL

6 table is customized and 9 tables made by default in Django)
olmsapp_customuser: This table store personal and login details of admin and
students.

olmsapp_author: This table track the details of authors.

Online Library Management System

olmsapp_category: This table track the record of category

olmsapp_book: This table for books records.

olmsapp_student: This table store student details.

olmsapp_issuedbookdetails: This table for maintain issued book and returned

book record.
 Default Tables Details

authentication_customuser_groups table Structure : This table by default table.

authentication_customuser_user_permissions table Structure : This table by

default table.

auth_group table Structure : This table in Django is part of the Django

authentication system and is used to represent groups of users.

auth_group_permissions table Structure : This table in Django is a part of the

permission system and is used to manage the relationship between user groups and
permissions.

auth_permission table Structure : This table in Django is used to store

information about the permissions defined.
django_admin_log table Structure : This table is used to store records of actions
taken by administrators or users through the Django admin interface.

django_content_type table Structure : This table in Django is a system table that

is used to store information about each model (database table) in your Django
project.

django_migrations table Structure : This table table is part of the database

schema and is used to keep track of which migrations have been applied to the
database.
django_session table Structure : This table store the session data for user.

3.2 USECASE DIAGRAMS:

Use case diagrams model behavior within a system and helps the developers
understand of what the user require. The stick man represents what’s called an
actor.
Use case diagram can be useful for getting an overall view of the system and
clarifying who can do and more importantly what they can’t do.
Use case diagram consists of use cases and actors and shows the interaction
between the use case and actors.
 The purpose is to show the interactions between the use case and actor.
 To represent the system requirements from user’s perspective.
 An actor could be the end-user of the system or an external system.

USECASE DIAGRAM:A Use case is a description of set of sequence of actions.

Graphically it is rendered as an ellipse with solid line including only its name. Use
case diagram is a behavioral diagram that shows a set of use cases and actors and
their relationship. It is an association between the use cases and actors. An actor
represents a real-world object. Primary Actor – Sender, Secondary Actor
Receiver.
Use Case Diagrams:

Admin

Login

Dashboard

Manage Category

Manage Author

Manage Books

Manage Issued Books

Search Books and students

Update Profile

Change Password

Password Recovery
User

Signup

Login

Dashboard

View Books Details

View Issued Books

Update Profile

Change Password

Password Recovery

Relationship between tables (Class Diagram)

3.3 DATA FLOW DIAGRAMS
A DFD does not show a sequence of steps. A DFD only shows what the different
process in a system is and what data flows between them.

The following are some DFD symbols used in the project

External entities

Process: A transaction of information that resides within the

bounds of the system to be module.

DATAFLOWS

DATASTORE: A repository of data that is to be

stored for use by one or more processes, may be as
simple as buffer of queue or as a relational
database.
RULES FOR DFD:

 Fix the scope of the system by means of context diagrams.

 Organize the DFD so that the main sequence of the actions
reads left to right and top to bottom.
 Identify all inputs and outputs.
 Identify and label each process internal to the system with
rounded circles.
 A process is required for all the data transformation and
transfers. Therefore, never connect a data store to a data source
or the destinations or another data store with just a data flow
arrow.
 Do not indicate hardware and ignore control information.
  Make sure the names of the processes accurately convey
everything the process is done.
 There must not be unnamed process.
 Indicate external sources and destinations of the data, with
squares.
 Number each occurrence of repeated external entities.
 Identify all data flows for each process step, except simple
Record retrievals.
 Label data flow on each arrow.
 Use details flow on each arrow.
 Use the details flow arrow to indicate data movements.
 There can’t be unnamed data flow.
 A data flow can’t connect two external entities.
LEVELS OF DFD:

The complexity of the system means that it is a responsible to represent the

operations of any system of single data flow diagram. At the top level, an
Overview of the different systems in an organization is shown by the way of
context analysis diagram. When exploded into DFD
They are represented by:
 LEVEL-0 : SYSTEM INPUT/OUTPUT
 LEVEL-1:SUBSYSTEM LEVEL DATAFLOW
FUNCTIONAL
 LEVEL-2: FILE LEVEL DETAIL DATA FLOW.
The input and output data shown should be consistent from one level to the next.
LEVEL-0: SYSTEM INPUT/OUTPUT LEVEL
A level-0 DFD describes the system-wide boundaries, dealing inputs to and
outputs from the system and major processes. This diagram is similar to the
combined user-level context diagram.
LEVEL-1: SUBSYSTEM LEVEL DATA FLOW
A level-1 DFD describes the next level of details within the system,
detailing the data flows between subsystems, which makeup the whole.

LEVEL-2: FILE LEVEL DETAIL DATA FLOW

All the projects are feasible given unlimited resources and infinite time. It is both
necessary and prudent to evaluate the feasibility of the project at the earliest
possible time. Feasibility and the risk analysis are pertained in many ways. If
project risk is great.
3.4 ER Diagram

Entity Relationship Diagram

 Testing
Start

Take choice

Choice

Admin
Login Exit

Enter
password

Match

Take choice

choice

Book Manage Student Logout

Detail Book Detail
 CHAPTER 4
SYSTEM IMPLEMENTATION

Home Page
Student Signup
Student Login

Student Dashboard
Student Profile

Change Password
Listed Books

Issued Books
Admin Login

Admin Dashboard
Admin Profile

Add Category
Manage Category

Update Category
Add Author

Manage Author
Update Author

Add Books
Manage Books

Update Books
Issue New Books

Manage Issue Books

View Issue Books

Update Issued Book

Register Students

Book Issued Details to Students

Search Book

Search Student
 CHAPTER 5
SYSTEM TESTING

The aim of the system testing process was to determine all defects in our
project .The program was subjected to a set of test inputs and various
observations were made and based on these observations it will be decided
whether the program behaves as expected or not. Our Project went through two
levels of testing

1.Unit testing

2.integration testing

UNIT TESTING

Unit testing is undertaken when a module has been created and successfully
reviewed .In order to test a single module we need to provide a complete
environment i.e. besides the module we would require

 The procedures belonging to other modules that the module under test
calls

 Non local data structures that module accesses

 A procedure to call the functions of the module under test with

appropriate parameters
Test For the admin module
Testing admin login form-This form is used for log in of administrator of the
system. In this we enter the username and password if both are correct
administration page will open otherwise if any of data is wrong it will get
redirected back to the login page and again ask for username and password

Student account addition- In this section the admin can verify student details
from student academic info and then only add student details to main library
database it contains add and delete buttons if user click add button data will
be added to student database and if he clicks delete button the student data
will be deleted

Book Addition- Admin can enter details of book and can add the details to
the main book table also he can view the books requests.

Test for Student login module

 Test for Student login Form-This form is used for log in of Student. In this
we enter the username and password if all these are correct student login
page will open otherwise if any of data is wrong it will get redirected back
to the login page username and password.
 Test for account creation- This form is used for new account creation
when student does not fill the form completely it asks again to fill the
whole form when he fill the form fully it gets redirected to page which
show waiting for conformation message as his data will be only added by
administrator after verification.
 INTEGRATION TESTING

In this type of testing, we test various integration of the project module by

providing the input. The primary objective is to test the module interfaces in order
to ensure that no errors are occurring when one module invokes the other module.
 CHAPTER 6
CONCLUSION & FUTURE SCOPE

This websites mainly focuses on how we can improve the traditional method of
working of a library because the traditional method includes doing all the things
in manual mode which is slow, less efficient, less secure, and difficult to manage.
The solution to this is an online library management system which take care of all
the work by automating and digitizing the whole process. Our application is
based on Python and is linked to a relational database (MySQL). The frontend
part has been coded using Python and its framework Django. The backend is
supported and connected with database. With the increase in the workload of the
library, new features can be added to the existing application to make it relevant
in the future as well.
As we know with the increase in number of students, books, complexity other
workloads, there can be a need of shifting the library data from the local database
to the cloud.
 CHAPTER 7
REFERENCES

[1] Django homepage. http://www.djangoproject.com/.

[2] Python documentation. http://www.python.org/doc.
[3] Django(web framework). http://en.wikipedia.org/wiki/Django.
[4] Django documentation. http://docs.djangoproject.com.
[5] Python(programming language). http://en.wikipedia.org/wiki/Python.

[6]Books: Web Development with Django by Ben Shaw, Saurabh,

Django 4 By Example by Antonio Mele