World Happiness Data

Note: this project was created for educational purposes as a student of Code Institute.

World Happiness Data is a tool to provide requested happiness scores from the World Happiness datasets from 2005 to 2020. It is a command line application and runs in a mock terminal provided by Code Institute. Users can select a country, get the happiness score for a specified year or all recorded years, view a graph of the happiness scores over time, and get the maximum, minimum, average and median happiness scores for the particular country.

View the live application here.

Purpose

The World Happiness Reports are annual publications which interpret and draw conclusions from data collected from people in over 150 countries.

The World Happiness Data tool is a command-line application allowing users to look up a dataset containing the happiness scores from the World Happiness Reports over the years 2005 to 2020 inclusive. The focus of this tool/application is to allow the user view happiness scores for particular countries, and get some basic information on these scores.

A user can choose a country and then:

request the happiness score for a particular year for that country
request the happiness score for all the available years for that country, and then, if selected, see a graph of these scores over time
request the maximum, minimum, average or mean happiness score for that country, or request all of these scores.

The user can choose a different country while in the application, after they have viewed the data they wanted for the previous country.

The application provides the requested data, and the graph if selected, to the user by printing it to the terminal.

The target market is relatively broad. In general, it would be people with a passing interest in the Happiness Reports, perhaps piqued when the results are announced each year in the general news. It is not aimed at people with in depth knowledge of the Happiness Reports nor those who want to do in depth data visualisations. The usefulness of the tool lies in the ability to quickly extract information from the large dataset.

User’s goals:

the users of the tool want to access the happiness scores for a country or countries, within the years 2005 - 2020
the user may want to view the score from a particular year, or for all years available for the chosen country
the user may also want to view a graph representing the happiness scores over time for a country, or get more information on that country such as maximium, minimum, average scores for that country.

Site owner’s goal:

the goal of this tool is to provide an easy way for users to get different information relating to the happiness scores from the World Happiness historical scores dataset, by requesting and viewing the results in the terminal.

Notes on the dataset:

the originating dataset contains other measures such as "Social support", "Freedom to make life choices", etc. which are used by the World Happiness Reports to draw conclusions on a country's happiness score. However this application does not use this information as the focus is solely the happiness scores.
the dataset spans the years 2005 to 2020 inclusive, however it does not hold a happiness score for every year for every country - this is dependant on the data available at the time. Therefore the application shows the users the years available to choose from.
there are five countries for which a score is only recorded for a single year. The application handles these by providing the score and year to the user once they select one of these countries (they are not given a choice of years in this case, as no choice exists). The user can then select to view a different country or simply exit the application.
the country names in the dataset are generally in the informal English name. The application holds some alternative names for countries, where applicable, so that if a user enters these names it will retrieve the correct country and not generate an error.
further information on the dataset can be found it the Content Requirements section.

User Experience (UX)

User stories

Note: there is no login or registered users for this application, so each user story is from the point of view of a visiting user using the application.

As a visiting user, I want to understand what data I can access from the application so that I know what information I can get from it
As a visiting user, I want to be able to choose a country so that I can view the data related to that country
As a visiting user, I want to see the happiness score for a particular year (from those available) for my selected country
As a visiting user, I want to be able to see the happiness score over time for a particular country, so that I can see the scores and trends over time for that country
As a visiting user, I want to be able to see a graph of the happiness score over time for a particular country so that I can visualise the data more easily
As a visiting user, I want to be able to see the maximum, minimum, average and median happiness score for my selected country.
As a visting user, I want to be able to select one option at a time from: maximum, minimum, average and median happiness score for my selected country
As a visiting user, I want to see the list of available countries so that I can ensure to choose a country from the list.

Design

Note: Since the application runs in the terminal, there is no design of the user interface as such.

The deployed application runs in a mock terminal on Heroku in order to demonstrate the project, the design of the mock terminal is built into the template provided by Code Institute.

The font 'ogre' is used to print the banner message on starting and exiting the application, using pyfiglet. pyfiglet uses fonts created from ASCII characters, the 'ogre' font generates a readable banner message.

Limited use of colour for the text pritned to the terminal is possible, using termcolor. Error messages are printed in red text, while outputs of information are printed in yellow so that they stand out to the user amongst the other text in the terminal.

Flow Chart

View the flowchart here, showing the steps that run in the application, how the user can move through the application and the user options at each stage.

The application is split into different 'paths' or sections. Each section is a path that the user can link into from a different section of the application, when they are presented with options. (Except for the one_score_path() which is not selected by the user, but determined by their choice of country - there are five countries in the dataset where the happiness score is only recorded for one year.) At the end of each section the user is presented with options, and put onto the new relevant path (or exit the application), based on their choice.

Features

Existing Features

Welcome message with short note on the purpose of the application
Option for user to input the country name they want
Option for user to view a list of the available countries within the dataset, before inputting their choice of country
Exception handling for the country choice, so that relevant error messages are shown if the user inputs an invalid input
When a valid country is entered (that is not a one score country), show the years for which the happiness score is available for that country, since the dataset does not have a score recorded for every year for some countries. User can then choose from these years.
Option for user to choose the year they want to view for that country, or all years
Exception handling for the years choice input, so that relevant error messages are shown if the user inputs an invalid input
Option for user, if they have chosen to view all years, to choose if they want to view a graph of the data. This will be the happiness score for that country over time
Exception handling for the user input to the Y/N choice input, so that relevant error messages are shown if the input is invalid
Option for user, if they originally chose a single year, to then view all years for the selected country
Option for the user to choose a different year for the selected country, after viewing a single year's score or viewing all years' scores (this option is not applicable when a country only has one score for one year)
Option for user to view min, max, median, average, or all of these values, for the selected country - this option can be chosen after selecting a single year's score to view, or after selecting all years, but is not available when a country only has one score
Option for user to go back and select another option from min, max, median, average, or all options (e.g. they chose max first time, can go back and chose min or all, etc.)
Option for user to choose a different country, or to exit programme when they have viewed their data
There are five countries in the dataset that only have a score recorded for one year. If the user chooses these countries, show the score and year along with a note confirming this is the only year available, and the option to choose a different country/exit
Exception handling for the user inputs when selecting an option from the list of numbered options, so that relevant error messages are shown if the input is invalid
Exit message confirming to user that they are exiting the application, and how to re-run the application
For the country choice user input, accept different alternative/alias names for the countries as far as practical, for example 'britain' will retrieve data for United Kingdom. Even though the application instructs the user to enter the common English name, this handling of alternative names is an extra help to the user to avoid frustration.
For user inputs requiring text, accept lowercase, uppercase, capitalised and combinations of same, for example iReLanD will retrieve data for Ireland.

Future Features

option for user to choose to look up the happiness scores by year, as an alternative to by country. To view, for example, the maximum, minimum, average and median scores from that year and the countries that had these scores, or top 10 scores and countries from that year, etc. The application could be extended to do this, by following the same approach for the country choice: create a dictionary by year, and create a Years class with methods to retrieve the maximum score etc. for the particular 'Year' instance.
option for user to view information on the other metrics included in the dataset, for example correlation between the metrics for a country/for all countries.
add new scores for 2020 (and 2021 and later years, when available)
option for a user to update the 'alternative country names' dictionary from the terminal. This option could be for specified users, when they become aware of a new valid alternative country name.
username/password functionality so that users can register
option for user to choose more than one country at a time, to view comparisons on the scores for these countries

Content Requirements

Th content required to create the project was the dataset with which the user will interact. It contains the happiness score for each country over the years 2005 - 2020 inclusive. Not every country has a score in every year, due to the way the data is collected, and as noted previously there are five countries that only have one score recorded in the dataset. The dataset was sourced from Kaggle.

Explanation of Happiness score:

It is referred to as "Life Ladder" in the dataset. This is the metric used to rate happiness and is based on a "Cantril life ladder" or subjective life evaluation. Survey respondents are asked to think of a ladder, with the best possible life for them being a 10, and the worst possible life being a 0. They are then asked to state which step of the ladder they feel they are at currently. The score for each country is the national average of each respondent's answer. The other metrics such as GDP, Social Support etc. are used by the Happiness Reports to explain the Life Ladder or Happiness score for the particular country. These metrics are not used in this application since the focus is purely on the happiness scores themselves.

Technology

Languages

Python

Note: HTML, CSS and Javascript exist in the template provided by Code Institute for this project but these are to run the mock terminal. The programme itself is built purely using Python.

Frameworks, Libraries, Programmes and Tools

diagrams.net to create the flowchart showing the user paths through the application
Git for version control, using the Gitpod terminal to commit to Git and push to GitHub
GitHub to store the project code
Heroku to host the live application
pyfiglet for the fonts used in the banner messages on entering and exiting the application
termcolor to apply colours to the text printed to the terminal
uniplot to create the graphs that can be displayed in the terminal (uniplot uses numpy)
PEP8 checker to validate the Python code
Code Institute template for creating the GitHub repository, it includes the files required for creating the mock terminal in which the application runs.

Data Model

The data for the application is contained in a csv file. The csv file contains the following headings that are used in the application: "Country name", "year", and "Life Ladder". (There are further headings in the csv file however these are not used in the application since the focus of the appplication is the happiness score only - referred to as "Life Ladder" in the csv file.) The csv file contains a line for each year and it's associated score - so for example, a country with scores recorded for 12 years will have 12 lines in the csv file.

Within the application, the relevant data from csv file is first used to create a dictionary, country_dict, containing key value pairs as follows:

key = country name,
value = list of tuples each containing year and score pairs for that country (or if country has only one score, this is a single tuple containing year and score)

Following on from this, the Country class is used as the data model. The Country class stores the following information:

name: country name
scores: a list of tuples containing the year and associated score, this is the value from the countries dictionary mentioned above.

If the country has more than one score recorded (this is the case for the majority of the countries) then the following information is also stored in the Class:

dictionary with years as the key and happiness score for that year as the value
list of the happiness scores, converted to floats so that they can be used for plotting the graph, getting maximum, minimum, average, median.
list of the years converted to int so that they can be used for plotting the graph, getting maximum, minimum, average, median.

An instance of Country class is created by the make_country function, each time the user selects a country that they want to view the scores/data for, in the get_country function(the instance is created after the country input has been validated). The class instance is created using the country name, and the list of year and scores tuples retrieved from the countries dictionary.

The methods in the Country class are used throughout the application, to get the information for the relevant country, which is presented to the user in the terminal:

show_scores: prints the requested score(s) to the terminal for the requested year or years, along with a relevant message if the country is a single score country
yrs_span: returns an f-string stating the span of years for the country, i.e.e. the first and last years in the available years. This is used by other methods when printing results to the terminal
show_graph: uses plot function from uniplot to plot a graph in the terminal showing all available happiness scores over time
print_yr_for_min_max: gets the year(s) corresponding to the relevant score (min score or max score) and returns an f-string stating the year(s). Used by other methods when printing the max or min score to the terminal
show_min_or_max_score: this method prints the min or max score for the country to the terminal, along with the corresponding year for that score
show_median_score, show_average_score: these methods print the median or average score for the country to the terminal
show_min_max_ave_med: prints the max, min, average and median scores for the country to the terminal, with associated text

Testing

Due to length, the testing section is contained in a separate file which you can read here: TESTING.md.

Deployment

Gitpod - during development

The application was developed on Gitpod, using GitHub for version control and hosting the repository. The repository for this project, and the associated workspace, was created from the Code Institute Python Project tempate, which enables the final application to be displayed in a mock terminal once deployed to Heroku.

During development, code was written in the Gitpod workspace and the application was previewed in the Terminal in Gitpod, using the command python3 -run.py (with run.py being the name of the python file containing the application code).
Libraries used in the application (which are then imported in the .py file) were installed by typing the relevant install command (as per library documentation) in the terminal, e.g. pip3 install termcolor, where termcolor is the name of the library being installed
Files and code were added to the staging area in Gitpod using the command git add . and commited using git commit -m "commit message".
Commited changes were then pushed to GitHub using the git push command.

Deployment to Heroku

The following steps show how to deploy the application to Heroku so that the application can be run in the mock terminal:

Do the following in the Gitpod workspace:

Go through the .py file(s) and check that every input has \n, for new line, at the end of the text inside the input, adding \n if not already there. This needs to be added due to a quirk in the software that creates the mock terminal: if the new line isn't added then the input will not appear in the mock terminal.
In the terminal type in the command: pip3 freeze > requirements.txt. This updates the requirements.txt file with the dependencies that were installed during development. Heroku will use this file to install the requirements when creating the application on Heroku.
Then add, commit and push these changes to GitHub using git add <filename> then git commit -m "message" then git push. Make sure all changes are added and commited in GitPod and pushed to GitHub before going to the next step.

Do the following in Heroku:

In Heroku:
- if you don't have an account, then set one up: Click the Sign up button in the header, fill out the form and Click Create Free Account when done. You will receive an email, click the link to confirm. Then you will be brought to page called SET YOUR PASSWORD. Enter password, click SET PASSWORD AND LOG IN. Will then show welcome page, click on CLICK HERE TO PROCEED, then click Accept to accept the terms of service. Then click on "Create new app"
- if you do have an account then Sign In to your account and go to the Dashboard. Click on "New" on the top right of the screen and then "Create new app"
Under App name, enter the name of the application. Note: the name must be unique, so you would not be able to name it the same as the already deployed version
Then choose the Region and click "Create app"
In the list of tabs at the top of the page underneath Personal, click on the Settings tab
If there was a creds.json file in the application then you would update the details under the Config Vars. This is not explained here, since there is no creds.json file in the World Happiness Data application
Scroll down to the section called Buildpacks. This is where you indicate the dependencies needed, outside of thos in the requirements.txt file.
- Click "Add buildpack" button
- Select Python from the list and press "Save changes"
- Click "Add buildpack" again, select nodejs and save. This is needed for the mock terminal code
- Make sure they are in that order with Python on top. If not, drag to change the order
Now go to the Deploy section. Scroll to top of page with tabs. Click Deploy
- Go to Deployment method and click GitHub
- If have not connected to GitHub previously:
  - Underneath, it will show a section called Connect to GitHub, with a button at the bottom called “Connect to GitHub”. Press this button.
  - A pop up will ask you to Authorize Heroku’s access to your GitHub – click to Authorize, then enter your password and Confirm Password
  - The pop up will close and in the Connect to GitHub section it will show your GitHub username and a box to search for the repository to connect to.
- If have already connected to GitHub you do not need to do the above and it should show your GitHub username and a box to search for the repo name as above
- Enter the repo-name in the box and press Search
- Underneath, it will display the repo: yourGitHubUsername/your-github-repo-name, then press "Connect"
- Once connected it will then show: Connected to yourGitHubUsername/your-github-repo-name by yourGitHubUsername
Underneath the Connect section, there are two options "Automatic deploys" or "Manual deploy"
- Automatic – future pushes to GitHub will mean Heroku automatically builds a new version of the app with the pushed changes
- Manual – the app is not automatically updated with future pushes to GitHub but these can be manually made if needed.
- click Deploy Branch. I deployed using Manual. The logs will show the buildpacks, dependencies and requirements being installed. When done, the page will refresh and say “Your app was successfully deployed” with a View button.
Click the View button to view the app – it opens in a new window
The Python program automatically runs, you no longer need to type python3 run.py in the terminal once the application is deployed
To re-start the programme from the beginning, press the RUN PROGRAM orange button at top of page

There is no difference between the deployed version and the development version of the application.

Forking the GitHub Repository

The repository can be forked on GitHub, this creates a copy of the repository that can be viewed or amended without affecting the original repository. This can be done using the following steps:

Login to GitHub
Locate the relevant repository on GitHub. This is the repository for World Happiness Data tool.
At the top right of the repository (under your avatar) locate the Fork button and click this button
You should now have a copy of the repository in your own GitHub account, to which you can make changes

Cloning the GitHub Repository

You can make a clone of the repository which will create a local copy on your own computer. Again you can make changes to this local copy that will not affect the original repository. Follow these steps to clone the World Happiness Data tool repository.

Login to GitHub and locate the repository as before
Click the button called Code, located to the left of the green Gitpod button
Under HTTPS copy the link provided (in this case https://github.com/Fiona-T/world-happiness-data.git)
Go to Gitpod or whichever IDE you are using and open the Terminal
Change the current working directory to the location where you want the cloned directory to be made
Type git clone followed by the url you copied in step 3: git clone https://github.com/Fiona-T/world-happiness-data.git
Press Enter to create the local clone

You can refer to the GitHub documentation for more detailed information on the above process.

Credits

Code

I used the guidance in this article from kite.com to use a list of exception words in the convert_to_titlecase function so that words such as 'Of', 'And' are not capitalised when converting country names back to their capitalised name. I extended this to included further functionality.
Used the guidance in this article from Programiz to create the custom Exception Classes
Used the method shown in this article from thispointer.com when creating the countries dictionary, to check the data-type of the existing key value and convert it to a list before adding the new value to the list.

Content

The dataset containing the happiness scores was sourced from Kaggle.
Most of the alternative country names for the "countries_alt_names" dictionary were sourced from this page on Wikipedia.

Media

the smiley face that prints when user exits the application was created by the developer, but based on examples shown at Love ASCII Art

Acknowledgements

I would like to thank the following:

my mentor Rohit Sharma for feedback and guidance throughout this project.
the Code Institute Slack community for advice and support along the way

Name		Name	Last commit message	Last commit date
Latest commit History 172 Commits
.vscode		.vscode
data		data
docs		docs
static		static
.gitignore		.gitignore
.gitpod.dockerfile		.gitpod.dockerfile
.gitpod.yml		.gitpod.yml
Procfile		Procfile
README.md		README.md
TESTING.md		TESTING.md
constants.py		constants.py
index.js		index.js
package.json		package.json
requirements.txt		requirements.txt
run.py		run.py

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Repository files navigation

World Happiness Data

Table of Contents

Purpose

User’s goals:

Site owner’s goal:

User Experience (UX)

User stories

Design

Flow Chart

Features

Existing Features

Future Features

Content Requirements

Technology

Languages

Frameworks, Libraries, Programmes and Tools

Data Model

Testing

Deployment

Gitpod - during development

Deployment to Heroku

Forking the GitHub Repository

Cloning the GitHub Repository

Credits

Code

Content

Media

Acknowledgements

About

Releases

Packages

Languages

Fiona-T/world-happiness-data

Folders and files

Latest commit

History

Repository files navigation

World Happiness Data

Table of Contents

Purpose

User’s goals:

Site owner’s goal:

User Experience (UX)

User stories

Design

Flow Chart

Features

Existing Features

Future Features

Content Requirements

Technology

Languages

Frameworks, Libraries, Programmes and Tools

Data Model

Testing

Deployment

Gitpod - during development

Deployment to Heroku

Forking the GitHub Repository

Cloning the GitHub Repository

Credits

Code

Content

Media

Acknowledgements

About

Resources

Stars

Watchers

Forks

Releases

Packages 0

Languages

Packages