Draw an ER diagram for a music recommender system with the following properties. 1) Artist information For each artist, we keep the following information (suggested attribute names are in parentheses): Artist id number (artist_id), artist name (artist_name), and artist popularity (artist_pop). There can be artists with the same name. An artist must record at least one track. Each artist is uniquely identified by artist_id. 2) Album information For each album, we keep the following information: album id number (album_id), album name (album_name), album popularity (album_pop), and release date (release_date). Each album is uniquely identified by album_id. Each album must contain at least one track. 3) Track information • Each track represents one piece of music that could be listened by users. For each track, we keep the following information: track number (track_id), track name (track_name), duration (duration), and tempo (tempo). Each track is uniquely identified by track_id. • Each track must belong to exactly one album. • Each track can be recorded by one or more artists. 4) User information Anyone who registers in the music recommender system becomes a user of the system. It is assumed that for each user, we can keep the following information: user id (user_id), user name (user_name), age (age), nationality (nationality), and the number of tracks the user has listened to (num_track_listened). Each user is uniquely identified by user_id. Each user can listen to one or more tracks. 5) Follow information Each following behavior refers to a user following an artist in the music recommender system. For each following behavior, we can record the date when a user has started to follow an artist (follow_date). Users can follow as many (including 0) artists as s/he likes, but some artists may not be followed by any user.
Draw an ER diagram for a music recommender system with the following properties. 1) Artist information For each artist, we keep the following information (suggested attribute names are in parentheses): Artist id number (artist_id), artist name (artist_name), and artist popularity (artist_pop). There can be artists with the same name. An artist must record at least one track. Each artist is uniquely identified by artist_id. 2) Album information For each album, we keep the following information: album id number (album_id), album name (album_name), album popularity (album_pop), and release date (release_date). Each album is uniquely identified by album_id. Each album must contain at least one track. 3) Track information • Each track represents one piece of music that could be listened by users. For each track, we keep the following information: track number (track_id), track name (track_name), duration (duration), and tempo (tempo). Each track is uniquely identified by track_id. • Each track must belong to exactly one album. • Each track can be recorded by one or more artists. 4) User information Anyone who registers in the music recommender system becomes a user of the system. It is assumed that for each user, we can keep the following information: user id (user_id), user name (user_name), age (age), nationality (nationality), and the number of tracks the user has listened to (num_track_listened). Each user is uniquely identified by user_id. Each user can listen to one or more tracks. 5) Follow information Each following behavior refers to a user following an artist in the music recommender system. For each following behavior, we can record the date when a user has started to follow an artist (follow_date). Users can follow as many (including 0) artists as s/he likes, but some artists may not be followed by any user.
Database System Concepts
7th Edition
ISBN:9780078022159
Author:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan
Publisher:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan
Chapter1: Introduction
Section: Chapter Questions
Problem 1PE
Related questions
Question
Draw an ER diagram based on the following information:
Transcribed Image Text:Draw an ER diagram for a music recommender system with the following properties.
1) Artist information
• For each artist, we keep the following information (suggested attribute names
are in parentheses): Artist id number (artist_id), artist name (artist_name), and
artist popularity (artist_pop). There can be artists with the same name.
• An artist must record at least one track.
• Each artist is uniquely identified by artist_id.
2) Album information
For each album, we keep the following information: album id number
(album_id), album name (album_name), album popularity (album_pop), and
release date (release_date). Each album is uniquely identified by album_id.
Each album must contain at least one track.
3) Track information
Each track represents one piece of music that could be listened by users. For each
track, we keep the following information: track number (track_id), track name
(track_name), duration (duration), and tempo (tempo). Each track is uniquely
identified by track_id.
• Each track must belong to exactly one album.
Each track can be recorded by one or more artists.
4) User information
Anyone who registers in the music recommender system becomes a user of the
system. It is assumed that for each user, we can keep the following information:
user id (user_id), user name (user_name), age (age), nationality (nationality), and
the number of tracks the user has listened to (num_track_listened). Each user is
uniquely identified by user_id.
Each user can listen to one or more tracks.
5) Follow information
Each following behavior refers to a user following an artist in the music
recommender system. For each following behavior, we can record the date when a
user has started to follow an artist (follow_date).
Users can follow as many (including 0) artists as s/he likes, but some artists may not
be followed by any user.
Note: The popularity of an artist or an album is an integer from 0 to 100, and the
duration of a track refers to the track length in milliseconds (integer).
Expert Solution
This question has been solved!
Explore an expertly crafted, step-by-step solution for a thorough understanding of key concepts.
This is a popular solution!
Trending now
This is a popular solution!
Step by step
Solved in 2 steps with 1 images
Knowledge Booster
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.Recommended textbooks for you
Database System Concepts
Computer Science
ISBN:
9780078022159
Author:
Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan
Publisher:
McGraw-Hill Education
Starting Out with Python (4th Edition)
Computer Science
ISBN:
9780134444321
Author:
Tony Gaddis
Publisher:
PEARSON
Digital Fundamentals (11th Edition)
Computer Science
ISBN:
9780132737968
Author:
Thomas L. Floyd
Publisher:
PEARSON
Database System Concepts
Computer Science
ISBN:
9780078022159
Author:
Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan
Publisher:
McGraw-Hill Education
Starting Out with Python (4th Edition)
Computer Science
ISBN:
9780134444321
Author:
Tony Gaddis
Publisher:
PEARSON
Digital Fundamentals (11th Edition)
Computer Science
ISBN:
9780132737968
Author:
Thomas L. Floyd
Publisher:
PEARSON
C How to Program (8th Edition)
Computer Science
ISBN:
9780133976892
Author:
Paul J. Deitel, Harvey Deitel
Publisher:
PEARSON
Database Systems: Design, Implementation, & Manag…
Computer Science
ISBN:
9781337627900
Author:
Carlos Coronel, Steven Morris
Publisher:
Cengage Learning
Programmable Logic Controllers
Computer Science
ISBN:
9780073373843
Author:
Frank D. Petruzella
Publisher:
McGraw-Hill Education