https://github.com/hecatops/library-management-app
A library management application, made with Flask, Vue.js and SQLite that has a single librarian and multiple users who can borrow books, read and review them. The admin creates sections and books within these sections and can approve or reject the requests of the users.
https://github.com/hecatops/library-management-app
bootstrap celery flask jwt-security mailhog python redis sqlite vuejs
Last synced: 3 months ago
JSON representation
A library management application, made with Flask, Vue.js and SQLite that has a single librarian and multiple users who can borrow books, read and review them. The admin creates sections and books within these sections and can approve or reject the requests of the users.
- Host: GitHub
- URL: https://github.com/hecatops/library-management-app
- Owner: hecatops
- Created: 2024-05-23T15:22:37.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2024-09-20T10:14:13.000Z (about 1 year ago)
- Last Synced: 2024-12-27T19:48:46.552Z (9 months ago)
- Topics: bootstrap, celery, flask, jwt-security, mailhog, python, redis, sqlite, vuejs
- Language: Vue
- Homepage: https://aditi-manthri.github.io/library-management-app/
- Size: 564 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
Description:
The library management app allows users to read e-books. The librarian is the admin. They are
responsible for adding sections and books and for approving, rejecting or terminating user
requests. The users can see a list of all the books available, request them and if approved, can get
access to the PDF version of these books, online. Both user and librarian can use the search
function to see what is available in the library.
Technology Used:
1. Flask: For API
2. JWT Security: For authorization and authentication
3. CORS: Used to authorize resources shared with external third parties
4. VueJS: JavaScript library for building UIs
5. SQLite: Database for storing application data
6. Redis: Caching
7. Celery: Background jobs
8. Bootstrap: Framework for styling UIs
DB Schema Design:
1. User:
a. id (Primary Key, Integer)
b. username (String, max length 150, unique, not null)
c. password (String, max length 256, not null)
d. role (String, max length 100, not null)
e. email (String, max length 256, not null)
f. last_login (DateTime)
2. Sections:
a. id (Primary Key, Integer)
b. name (String, max length 256, unique, not null)
c. date_created (DateTime)
d. description (String, max length 256)
3. Book:
a. id (Primary Key, Integer)
b. name (String, max length 100)
c. author (String, max length 256)
d. section_id (Integer, Foreign key Sections id)
e. description (String, max length 256)
f. section (String, max length 256)
g. pdf (String, max length 512)
4. Requests:
a. id (Primary key, Integer)
b. requested_user (Integer, Foreign key User id)
c. requested_book (Integer, Foreign key Book id)
d. user (String, max length 256)
e. book (String, max length 256)
f. approved (Boolean)
5. Issued:
a. id (Primary Key, Integer)
b. requested_id (Integer, Foreign key Request id)
c. issued_user (Integer, Foreign key User id)
d. issued_book (Integer, Foreign key Book id)
e. date_returned (DateTime)
f. book (String, max length 256)
g. author (String, max length 256)
h. description (String, max length 256)
i. pdf (String, max length 512)
6. Feedback:
a. id (Primary Key, Integer)
b. user_id (Integer, Foreign key User id)
c. book_id (Integer, Foreign key Book id)
d. issue_id (Integer, Foreign key Issued id)
e. feedback (String, max length 256)
7. Read:
a. id (Integer, Primary key)
b. book_id (Integer, Foreign key Book id)
c. user_id (Integer, Foreign key User id)
d. timestamp (DateTime)
API Designs
1. CRUD for Sections
2. CRUD for Books
3. Validation of input fields
4. Backend validation
Architecture
There are 3 Python files;
1. app.py
2. celery_config.py
3. tasks.py
Screenshots:
Video Link: https://drive.google.com/file/d/1P3gvgEi1CBat7yFJ5LbVEsAe3cj3nOAt/view?usp=drive_link