Continuing with the Vince's Vinyl scenario from Hands-On Database, create an updated ERD after Normalization ? The diagram could pass the first three levels of normalization. There are a couple of issues, though, that could lead to further normalization: Customers and Sellers can be the same people. This could lead to update anomalies as the same person could have their information in two places. The solution is to create a Person entity that contains all names, phone numbers and email addresses. The person key could represent them in either role in Sale, Request, or Purchase. Another subtle issue relates to the entity Album. If Vince were to remove an album, and it was the only copy of that album, he would lose the album information. Also, there is potential redundancy in Album, since each physical vinyl is treated as an individual item in the table. Multiple copies of the same album would result in multiple entries identical except for purchase date and perhaps condition. To solve this would require separating Album from Inventory and having it contain the title, studio, and date.

Principles of Information Systems (MindTap Course List)
12th Edition
ISBN:9781285867168
Author:Ralph Stair, George Reynolds
Publisher:Ralph Stair, George Reynolds
Chapter5: Database Systems And Applications
Section5.7: Information Systems @ Work: Brandwatch: Applying Business Intelligence To Social Media Data To Make Advertising Decisions
Problem 1CTQ
icon
Related questions
Question

Continuing with the Vince's Vinyl scenario from Hands-On Database, create an updated ERD after Normalization ?

The diagram could pass the first three levels of normalization. There are a couple of issues, though, that could lead to further normalization:

Customers and Sellers can be the same people. This could lead to update anomalies as the same person could have their information in two places. The solution is to create a Person entity that contains all names, phone numbers and email addresses. The person key could represent them in either role in Sale, Request, or Purchase.

Another subtle issue relates to the entity Album. If Vince were to remove an album, and it was the only copy of that album, he would lose the album information. Also, there is potential redundancy in Album, since each physical vinyl is treated as an individual item in the table. Multiple copies of the same album would result in multiple entries identical except for purchase date and perhaps condition. To solve this would require separating Album from Inventory and having it contain the title, studio, and date.

 

Expert Solution
trending now

Trending now

This is a popular solution!

steps

Step by step

Solved in 3 steps with 1 images

Blurred answer
Knowledge Booster
Enhanced ER Model
Learn more about
Need a deep-dive on the concept behind this application? Look no further. Learn more about this topic, computer-science and related others by exploring similar questions and additional content below.
Similar questions
  • SEE MORE QUESTIONS
Recommended textbooks for you
Principles of Information Systems (MindTap Course…
Principles of Information Systems (MindTap Course…
Computer Science
ISBN:
9781285867168
Author:
Ralph Stair, George Reynolds
Publisher:
Cengage Learning