Library management system version 2 using to CodeIgniter 4 Framework PPT
- 1. MINI PROJECT REVIEW GOVT. ARTS COLLEGE (A) . SALEM-7 DEPARTMENT OF COMPUTER APPLICATIONS
- 2. 2 TITLE 2
- 4. ABSTRACT A DEPARTMENT(CA) LIBRARY MANAGEMENT SYSTEM IS A PROJECT THAT MANAGES AND STORES BOOKS INFORMATION ELECTRONICALLY ACCORDING TO STUDENT AND STAFF NEEDS. THE SYSTEM HELPS ADMIN TO KEEP A CONSTANT TRACK OF ALL THE BOOKS AVAILABLE IN THE DEPARTMENT LIBRARY. IN THIS SYSTEM ALLOWS ADMIN, FACULTY AND STUDENT TO SEARCH THE DESIRED BOOK. IT BECOMES NECESSARY FOR DEPARTMENT TO KEEP A CONTINUOUS CHECK ON THE BOOKS ISSUED AND RETURNED AND EVEN CALCULATES THE FINE. 4
- 5. 5 THIS TASK IF CARRIED OUT MANUALLY WILL BE TEDIOUS AND INCLUDES CHANCES OF MISTAKES. THESE ERRORS ARE AVOIDED BY ALLOWING THE SYSTEM TO KEEP TRACK OF INFORMATION SUCH AS ISSUE DATE, LAST DATE TO RETURN AND EVEN FINE AMOUNT INFORMATION. THERE IS NO NEED TO KEEP MANUAL TRACK OF THIS INFORMATION AND ITS AUTOMATICALLY CALCULATE THE FINE AND REDUCES THE CHANCES OF MISTAKES. THIS SYSTEM REDUCES THE MANUAL WORK TO A GREAT EXTENT ALLOWS SMOOTH FLOW OF LIBRARY ACTIVITIES BY REMOVING CHANCES OF ERRORS IN THE DETAILS OF DEPARTMENT(CA) LIBRARY MANAGEMENT SYSTEM. ABSTRACT
- 6. REQUIREMENTS SOFTWARE SPECIFICATION : APPLICATION SERVER : APACHE HTTP SERVER OPERATING SYSTEM : LINUX, WINDOWS 7/8/8.1/10 FRONT END : HTML, CSS, BOOTSTRAP BACK END : PHP, MYSQL, JAVASCRIPT FRAMEWORK : CODEIGNITER 4 6
- 7. REQUIREMENTS 7 HARDWARE SPECIFICATION : PROCESSOR : PROCESSOR DUAL CORE STORAGE : HARD DISK 500GB RAM : MINIMUM MEMORY 4GB
- 8. MODULES Admin Purchase Books Borrow/Return Manage Books Manage Users 8
- 9. 9 ADMIN MODULES Login Dashboard Update Profile View Books Users Requests
- 11. 11 BORROW/RETURN MODULES Manage Book Borrow Manage Book Return Update Book Status
- 12. 12 BOOKS MODULES Add New Books Update Books
- 13. Manually search each book in the location where it is kept. Maintenance of ledger books for borrowing and returning the book. 13 EXISTING SYSTEM
- 14. 14 PROPOSED SYSTEM In this project, describe how to run a paperless library and keep track of books, users, and records.
- 15. 15 FLOW DIAGRAM
- 16. 16 FLOW DIAGRAM
- 17. INPUT DESIGN 17
- 18. INPUT DESIGN 18
- 19. INPUT DESIGN 19
- 20. OUTPUT DESIGN 20
- 22. DB REQUEST LIST FACULTY STUDENTS BORROW BOOKS MASTER BOOKS DATABASE DESIGN 22 ID(PRIMARY KEY) BOOK No. TITLE BAR CODE AUTHOR NAME PUBLICATION PRICE RACK STATUS
- 23. MASTER BOOKS DATABASE DESIGN 23 Unique identifier for each book record. ID (Primary Key): A unique identifier for the book within the library. BOOK No.: The title of the book. TITLE: A unique identifier in barcode format for easy scanning. BAR CODE: Name of the book's author. AUTHOR NAME: The publishing company or entity. PUBLICATION: The cost of the book. PRICE: The physical location of the book on library shelves. RACK: Current status of the book (e.g., available, checked out). STATUS:
- 24. DATABASE DESIGN 24 BID(PRIMARY KEY) STUDENT/FACULTY ID BOOK ID BARROW DATE RETURN DATE RETURNED DATE STATUS TABLES MASTER BOOKS REQUEST LIST FACULTY STUDENTS BORROW BOOKS
- 25. DATABASE DESIGN 25 BORROW BOOKS Unique identifier for each transaction. •BID (Primary Key): Identifier for the student or faculty member involved in the transaction. STUDENT/FACULTY ID: Identifier for the borrowed book. BOOK ID: Date when the book was borrowed. BARROW DATE: Expected return date for the book. RETURN DATE: Actual return date of the book. RETURNED DATE: Status of the transaction (e.g., pending, returned, overdue). STATUS:
- 26. DATABASE DESIGN 26 SID(PRIMARY KEY) REG. No. NAME PASSWORD(ENCRYP TED) GENDER EMAIL YEAR OF JOINING DB BORROW BOOKS MASTER BOOKS REQUEST LIST FACULTY STUDENTS
- 27. DATABASE DESIGN 27 STUDENTS Unique identifier for each student. •SID (Primary Key): Registration number or unique identifier for the student. REG. No.: Full name of the student. NAME: Encrypted password for secure authentication. PASSWORD (ENCRYPTED): Gender of the student. GENDER: Email address of the student. EMAIL: Year when the student joined the institution. YEAR OF JOINING: Shift in which the student is enrolled (e.g., morning, evening). SHIFT:
- 28. DATABASE DESIGN 28 CAFID(PRIMARY KEY) REG. No. NAME PASSWORD(ENCRYP TED) GENDER EMAIL DB STUDENTS BORROW BOOKS MASTER BOOKS REQUEST LISTS FACULTY
- 29. DATABASE DESIGN 29 FACULTY Unique identifier for each faculty member. •FACULTYID (Primary Key): Registration number or unique identifier for the faculty. REG. No.: Full name of the faculty member. NAME: Encrypted password for secure authentication. PASSWORD (ENCRYPTED): Gender of the faculty member. GENDER: Email address of the faculty member. EMAIL: Designation or position of the faculty member (e.g., Professor, Guest Lecturer). DESIGNATION:
- 30. DATABASE DESIGN 30 RID(PRIMARY KEY) REQUESTER ID RECEVIER ID MESSGAGE REQUESTER ROLE RECEVIER ROLE DB FACULTY STUDENTS BORROW BOOKS MASTER BOOKS REQUEST LIST
- 31. DATABASE DESIGN 31 REQUEST LIST Unique identifier for each request/notification. •RID (Primary Key): Identifier for the user making the request/notification. REQUESTER ID: Identifier for the user receiving the request/notification (e.g., borrower and admin). RECEIVER ID: The content of the request or notification message. MESSAGE: Role of the requester (student or faculty or admin). REQUESTER ROLE: Role of the receiver (borrower, admin). RECEIVER ROLE:
- 32. OUTPUT DESIGN 32
- 33. OUTPUT DESIGN 33
- 34. OUTPUT DESIGN 34
- 36. PITCH DECK 36