User Mode (for Students):
- Register in the library portal
- Can search for the book from the book’s collection
- Submit a request to issue a book
- When a due date is about to come up, the student should be able to either reissue the book or deposit the book
- Should be able to view the dues on the library account.
Admin Mode (for Librarian):
- Manage details of students and books
- Able to add/remove books from the collection
Also, we have the following constraints:
- A student is limited to three book checkouts.
- A student can keep a book for at most 15 days.
- If a student returns a book after the deadline, the system should be able to calculate the charges and add it to the existing dues.
The following functionalities have been implemented for Student:
- Registration/ Sign-In
- Book Search by:
- Title
- Author
- ISBN
- Book Issue:
- Can issue at maximum 3 books
- Will have due date set to 15 days ahead of current date
- Book Re-Issue: Can't be re-issued again
- View total dues.
- Return book:
- Will show dues incurred for the returned book
- Will add this to the total dues
The following functionalities have been implemented for Librarian:
- Review all Books
- Review all students
- Add/Remove Books
- Set Fine(Default set to Rs 1.0/day delay)
This project uses MySQL database which is implemented in the Database_DAO.java, which requires a .jar file, which needs to be imported in order for MySQL Driver to work.
We have used multithreading to handle issue requests and reissue requests. There are two classes generated which implement the Runnable interface and override the run() method - BookIssuer and ReissuerBook.
These 2 classes each have a synchronized function - issueBook() in BookIssuer and reissuerBook() in ReissuerBook.
The reason why they are synchronized is that if two students are trying to access the same book at the same time, then error would get generated. So we want to only one thread to access the function at one time.