Database for storing book information, for use within an App [closed]
I'm looking for a better way to deal with the design I have here, I'm not confident it's really suitable. To give this some context, this will be an App for indexing books (from an API, including title, author, etc). Users than can index each book by chapter (which will need page ranges), to include key theme and characters and that feature within that chapter. In time, users could even review/add notes to each chapter if they wanted. So, for this App to work, I'll need to organise the database into tables. Am I on the right lines? (to record registered users of the app, as users may log the same book/chapter). Users - user_id username (once searched, this table will be populated from a popular book database API) Books - book_id - title - author - keywords (this is the manual index, from user generated information via the app) BooksExtraDetail - chapter_id - book_id - title - page (once the chapters have been recorded, information about each chapter will be indexed. This will improve the search function by character or theme). ChapterInfo - chapter_id - character - theme (this is to track which users have which books and chapters logged in their bookshelf). BookShelf - user_id - book_id - chapter_id - rating Is this the corret use of a database/table in app development? What else should I consider between the relationship of these apps?
![Database for storing book information, for use within an App [closed]](https://cdn.sstatic.net/Sites/softwareengineering/Img/apple-touch-icon@2.png?v=1ef7363febba)
I'm looking for a better way to deal with the design I have here, I'm not confident it's really suitable.
To give this some context, this will be an App for indexing books (from an API, including title, author, etc). Users than can index each book by chapter (which will need page ranges), to include key theme and characters and that feature within that chapter.
In time, users could even review/add notes to each chapter if they wanted.
So, for this App to work, I'll need to organise the database into tables. Am I on the right lines?
(to record registered users of the app, as users may log the same book/chapter). Users
- user_id username
(once searched, this table will be populated from a popular book database API) Books
- book_id
- title
- author
- keywords
(this is the manual index, from user generated information via the app) BooksExtraDetail
- chapter_id
- book_id
- title
- page
(once the chapters have been recorded, information about each chapter will be indexed. This will improve the search function by character or theme). ChapterInfo
- chapter_id
- character
- theme
(this is to track which users have which books and chapters logged in their bookshelf). BookShelf
- user_id
- book_id
- chapter_id
- rating
Is this the corret use of a database/table in app development? What else should I consider between the relationship of these apps?
What's Your Reaction?
