Applying data modeling with Postgres and build an ETL pipeline using Python. By defining fact and dimension tables for a star schema for a particular analytic focus, and writing an ETL pipeline that transfers data from files in two local directories into these tables in Postgres using Python and SQL.
test.ipynbdisplays the first few rows of each table to let you check your database.create_tables.pydrops and creates your tables. You run this file to reset your tables before each time you run your ETL scripts.etl.ipynbreads and processes a single file from song_data and log_data and loads the data into your tables. This notebook contains detailed instructions on the ETL process for each of the tables.etl.pyreads and processes files from song_data and log_data and loads them into your tables. You can fill this out based on your work in the ETL notebook.sql_queries.pycontains all your sql queries, and is imported into the last three files above.helpers.pysome python functions to be used on the other files.db_config.ymldata base configuration fields.
- Write CREATE statements in
sql_queries.pyto create each table. - Write DROP statements in
sql_queries.pyto drop each table if it exists. - Run
create_tables.pyto create database and tables. - Build ETL in
etl.ipynbandetl.py - Run
test.ipynbto conf after each step to run Sanity Checks.
Star schema
- songplays - records in log data associated with song plays i.e. records with page
NextSong- songplay_id, start_time, user_id, level, song_id, artist_id, session_id, location, user_agent
- users - users in the app
- user_id, first_name, last_name, gender, level
- songs - songs in music database
- song_id, title, artist_id, year, duration
- artists - artists in music database
- artist_id, name, location, latitude, longitude
- time - timestamps of records in songplays broken down into specific units
- start_time, hour, day, week, month, year, weekday
