Database Design
Some of the columns might not get used, but if there is time it would be cool to add them.
Database: librarysim
Table: Patron
- ID
- Name
- Phone Number
- Address
- Gender
- Date of Birth
Table: Books
- ID
- Patron ID
- Type
- Title
- Author
- Description
- Checked In
- Checked Out
- Reserved
Table: Media
- ID
- Patron ID
- Type
- Title
- Rating
- Description
- Checked In
- Checked Out
- Reserved
How do we differentiate between child patrons and adult patrons? We could derive it from the date of birth, but we would need to define how old an adult is. If we do it like that however, it's not obvious who is a child and who is an adult. Unless we were to show it on the interface along with the data, but that would just unnecessarily complicate things. I propose we add a type to the patron to tell which ones are children and adults more simply. We should also add a due date for the books and media for the same reasons.
In short: Add a type in patron for child and adult, and a due date for books and media.
I'm also wondering if we should combine books and media in the same UI area to save space.