Loading presentation...

Present Remotely

Send the link below via email or IM


Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.


Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Music Library Database

No description

Joban Sidhu

on 14 November 2013

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Music Library Database

Music Library Database
The Idea
Database from everyday use

Unorganized music collection
Don't know where a particular song is located

Database - organize personal music collection
Step 2
Step 3 - Normalization Process
Identifying potential problems, called updating anomalies, in the design of a relational database

Normal form: Contains desirable properties
First normal form (1NF)
Second normal form (2NF)
Third normal form (3NF)

Functional Dependence
Column B is functionally dependent on column A
Each value for A is associated with exactly one value of B (A → B)
A functionally determines B
Step 4 - Entity Relationship Diagram
Achieved a simple working database
Music more organized
Not the most effective - but can build more effective system on top of this database
Presented By:
Bharath Rao
Nikitha Dhanekula
Preet Joban S. Sidhu
Step 1 - Data
Many artists - individual performers with no band - Database considers individual artists as band as well.

Some songs had more than one recording label - Database considers just one.

Some songs have multiple releases - Database designed to carry just one of them.
Some artists in database use different screen name and not their real name - Database considers their real name in the tables.

Some songs have multiple composers or artists (lead singer) - Database carries the name of just one of them.

All the different types of genre under Rock category are grouped under 1 genre.

Some songs are from different languages with varying spellings - Database uses Wikipedia as the source for song information.
Primary key: uniquely identifies each record in the table.
Either be a normal attribute that is unique
Generated by the DBMS
Primary key: of single attribute or multiple attributes in combination.

Candidate key: column(s) on which all columns are functionally dependent
Alternate keys: candidate keys not chosen as primary key
1NF - First Normalization
Data already in 1NF
Limited Data for the project
No Repeating groups
2NF - Second Normalization
Identify functional dependencies
Song --> Genre, Year, Language, Artist, Composer
Album --> Recording Label, Band

3NF - Third Normalization
Introduced few more elements for more informative Database

Identified Determinants and their dependent variables

Introduced Aritificial Keys as Primary Keys - autogenerated

SongID --> SongName, SongDescription, Genre, SongYear, Size, Language, ComposerID, Lyrics
ArtistID --> ArtistLastName, ArtistFirstName, ArtistDescription
ComposerID --> ComposerName, ComposerDescription
BandID --> BandName, BandDescription
AlbumID --> AlbumName, AlbumDescription, RecordingLabel, AlbumYear

Song Table
Band Table
Composer Table
Artist Table
Album Table
Final Tables
Thank you!!
Step 5 - Data Types
Song Data Types
Artist Data Types
Album Data Types
Band Data Types
Composer Data Types
Full transcript