DATABASE: E-R DIAGRAM

1) Write down any important assumptions you make about the data (e.g. what is unique, what pertains to an individual or group, etc.) that will help the marker understand your diagram.

2) An E-R diagram for the data model satisfying the following requirements.

Here are the details. Musicians use "fake books" to play and improvise from. We want to create a database that will use the indexing information provided in assignment #1 an support the following The users (musicians) will upload their own copies of .pdf books to the application. The books supported will be those that appear with the indexing data (books in the bookcodes table from assignment #1). When a musician has uploaded a book they will have the right to be shown pages of that book using the indexing data in the database. The musicians will only be allowed to see the books they have uploaded, but they can search all of the indexing data. For copyright and legal reasons they will not be allowed to see contents from other user's books. If two musicians upload the same identical book in theory the app need only keep one copy but for legal reasons individual copies must be kept. Also even if musicians uploaded what is supposed to be the same book, some will include the cover page and foreword and some won't so the scans may not be identical The indexing information should provide the books and page numbers for the various songs in the books. Song information should include the song's title, composer(s), book page number, and length in pages. Each uploaded book should also have some kind of offset information to account for introductory pages, missing forewords etc. That is, if the song is indexed to be on page 1 but that is the 10th page of a particular user's scanned .pdf book then an offset should be stored in the database to account for this. The database should store information about the books which includes their book code (unique), title, publisher, and date of publication and the individual copies of that book uploaded by the various users The database should support a collection of users. Users have a name, email address, userid, password. The database must keep track of which books which users are allowed to access. The application will require users to login with user id and password and only let them see data once their userid and password is verified Design an E-R model for this database. You will have to make decisions about attributes and keys. If you don't think it is clear what your attributes mean then provide some notes and assumptions to go with your design. It is expected that this question will require classroom discussion to clarify what is required. Make sure to ask lots of questions. Here are the details. Musicians use "fake books" to play and improvise from. We want to create a database that will use the indexing information provided in assignment #1 an support the following The users (musicians) will upload their own copies of .pdf books to the application. The books supported will be those that appear with the indexing data (books in the bookcodes table from assignment #1). When a musician has uploaded a book they will have the right to be shown pages of that book using the indexing data in the database. The musicians will only be allowed to see the books they have uploaded, but they can search all of the indexing data. For copyright and legal reasons they will not be allowed to see contents from other user's books. If two musicians upload the same identical book in theory the app need only keep one copy but for legal reasons individual copies must be kept. Also even if musicians uploaded what is supposed to be the same book, some will include the cover page and foreword and some won't so the scans may not be identical The indexing information should provide the books and page numbers for the various songs in the books. Song information should include the song's title, composer(s), book page number, and length in pages. Each uploaded book should also have some kind of offset information to account for introductory pages, missing forewords etc. That is, if the song is indexed to be on page 1 but that is the 10th page of a particular user's scanned .pdf book then an offset should be stored in the database to account for this. The database should store information about the books which includes their book code (unique), title, publisher, and date of publication and the individual copies of that book uploaded by the various users The database should support a collection of users. Users have a name, email address, userid, password. The database must keep track of which books which users are allowed to access. The application will require users to login with user id and password and only let them see data once their userid and password is verified Design an E-R model for this database. You will have to make decisions about attributes and keys. If you don't think it is clear what your attributes mean then provide some notes and assumptions to go with your design. It is expected that this question will require classroom discussion to clarify what is required. Make sure to ask lots of questions