DIGITAL MEDIA KIT DOSSIER

normalisation

is the process of organizing data in a database. It includes creating tables and establishing relationships between those tables according to rules designed both to protect the data and to make the database more flexible by eliminating redundancy and inconsistent dependency.

start

This is an index

1st Normal Form

Press releases / relevant launches

Product / Service

Media appearances

Relevant data

Awards and recognitions

Brand

Testimonials / relevant customers

Team

Social networks and press contact

1 NF ( 1st Normal Form )

+ info

Key Areas in 1NF

Select a primary key ( needs to be unqiue )

Remove any calculated fields

Make sure the data is atomic

Remove repeating group

Task 1NF

+ info

Next

2 NF ( 2nd Normal Form )

The second normal form (2NF) is the next level of normalization. It means that each non-key attribute should depend on the primary key and not on any other columns.

For the second normal form, you need to make sure that each non-key attribute depends on the primary key and not on any other columns. Normalization helps to reduce redundancy and make the database more efficient. It also helps to keep the data consistent and accurate.

1NF

The table must be already in 1 NF

The partial dependencies are removed and placed in a separate table

+ info

Task 1NF

+ info

Atomic Data

Single value data

Atomic data is another critical facet of 1NF, where each field within a table holds only singular, indivisible values.

Primary Key

Select a PK

Find and select a primary key within a table. This is crucial, as it uniquely identifies each record. If there not a vaue that uniquely identify a record then a composite key is created. Composite key ( combination of two or more columns in a table that can be used to uniquely identify each row in the table. )

Remove Repeating Groups

The removal of repeating groups streamlines the structure by eliminating redundant data sets, ensuring each attribute is stored only once.

Primary Key

Select a PK

Find and select a primary key within a table. This is crucial, as it uniquely identifies each record. If there not a vaue that uniquely identify a record then a composite key is created. Composite key ( combination of two or more columns in a table that can be used to uniquely identify each row in the table. )

Why is this not in 2NF

The composite primary key is StudentID and ProjectID. The non-prime keys i.e. StudentName and ProjectName need to be functionally dependent on the primary key. To be in 2NF. The StudentName can be determined by StudentID, which makes the relation Partial Dependent. The ProjectName can be determined by ProjectID, which makes the relation Partial Dependent. Therefore, the <StudentProject> table relation violates the 2NF in Normalization and is considered a bad database design.

Remove Calculated fields

Eliminating calculated fields is essential, as these fields derive their values based on other attributes within the same table. Here the Total col should be removed.

Student Info Table

Project Info Table

Course Table:

Instructor Table:

Now, 'Instructor Email' is solely dependent on the 'Instructor ID', satisfying the conditions of 2NF.