Reqs Features

##Reqs/Features For Sprint 1

• CRUD Books to/from the library
  • Books may be added to the library by entering an ISBN. Book metadata should be retrieved based on the ISBN and added to the system.
  • On book addition, the administrator should be notified if the book is a duplicate.
• An entry for a book will consist of the following data:
  • Title
  • One or more Authors
    • Have an authors table/object. Will allow for easier filtering, less data shoved into the db, and may allow for an auto-complete of sorts.
  • ISBN
  • Publisher
  • Publishing Date
  • Book Location (ex. SSE Lab)
  • Shelf Location (ex. Mentoring Cabinet, Third Row)
    • Note: This would require everything to stay neatly organized, so this may not be super useful. * May not be useful for us, but it should be nice for anyone using this for a more organized library.
  • Condition (ex. "Good", "Broken Spine", etc.)
  • Status (ex. "Checked Out", "Available for Checkout", "Missing", etc.)
  • Count
  • Required Text (this should be a flag)
  • Notes
• The following information must be tracked when a book is checked out:
  • The book which was checked out.
  • The user who checked out the book.
  • When the book is due back.
• In order to streamline the checkout process, only 1 book should be checked out at a time.
  • The user can have multiple books checked out at once, but they must check each one out individual.

##Reqs/Features for Sprint 2

• A User can check out a book from the library.
  • The user who checked out the book must be tied to the checkout
  • Book due date should be configurable
  • Restrict certain books from being checked out (eg. Required texts)
• A User can check a book into the library
  • This should require confirmation from an administrative user
• All users should be able to search for books.
  • The main search page should allow for search by Title or ISBN.
  • More advanced search functionality should be accessable via an "advanced search" page.

##Reqs/Features for Sprint 3

• View all books checked out by a user
  • Optionally, this should be able to be restricted to administrative users only.
• Administrative users should be able to mark a book as missing.
• Administrative users should be able to mark a missing book as found.
• View info about a book's previous transaction history.
• List books by checked out/missing/overdue/requested.
• An administrative user can ban users from checking out books

Possible Reqs/Features Spanning the entire project

• Detect multiples of a book (I believe that we have been trying to keep duplicates in the library to a minimum)
• Alert designated users when a book has not been returned on time
  • This should include an administrative user and the user who checked out the book
• Alert the user who checked out a book shortly before the book is due
• Allow a book to be put on hold (maybe)
• Users can request a book
• Avatars for users