Firm TODOs

Please complete the two tasks in our Fundamentals review

Create a github.com account

Optional TODOs

Create a skills TODO list for yourself to tackle during week -1 and week 0

Background on version control and configuration management

To Prepare for git intro next week, explore the git book and git resources on linked in learning.

Idea: Explore Kaggle data competitions

Code from class on 4-SEP-2021

1. Consider the free ed license for pycharm via JetBrains
2. Implement the functions defined in class for computing a percent of redated EMS dispatch records in Allegheny county by year. A good faith effort means that you attempted each function and tried to get an overall working script, but if you hit walls, check your documentation, come to office hours at noon, but don't go nuts.
3. Ensure that you have the git tool installed on your local system. This is a free tool provided for ALL operating systems. Use git-scm.com. Most defaults on install are acceptable. You'll be given an option to install the Graphic Interface (i.e. GUI) and/or BASH. Be sure to install BASH. We don't use the GUI in this course!!!
4. Optional if you feel behind: Hack away at your skills refresher TODO list for weeks -1 and 0; prepare to share your artifacts, if any.

Notes:

Maintain your own logical flow chart that reflects how you actually implemented our project. If you change the method input/outputs, depict those changes in your diagram.

Finish EMS processing

get your file parsing of the EMS dispatch calls to display at least a tally of redactions by year, perhaps even a percentage

Make at least 4 commits from git BASH

As practice with git, preferably in a repo that you'll be comfortable sharing with the whole world next week

Choose a new CSV based data set

JSON next week: browse the WPRDC, data.gov, google source aggregate are good sources. Choose a csv based data set about which you have an interesting research question. Draft that question in a file and commit to your repo.

JSON Preview

1. Log your chosen CSV in our FA 21 master tracker JSON tab
2. Generate a coding plan for a program to use a JSON-encoded search criteria to select records from your chosen data set and output the matches, also in a JSON file
3. Begin coding your program, but it can be in process. Completion target for this project Sat, 2-OCT-2021
4. Use GIT every day!! Add, commit, push to your remote repo.

Fully bake & push JSON project to git

1. Write python code to the JSON project specs: read in a data set as a CSV file and a JSON file encoding a filter criteria for records in your data set. interpret the JSON file's contents to generate a JSON-encoded output file containing only the matching records
2. Document your project in a README.md file written in markdown that contains at least these sections: A) a written description of your project: what does it do, and why did you write it B) information regarding the data set you filtered, including links if the data are public C) user guide for creating a properly structured JSON file to encode your filter criteria (e.g. your JSON file should specify a list of key value pairs, including at least a key called "year" and a value as a single (scalar) year as an integer...)
3. Push your python and your README.md markdown file to your course git repository. If you are not publicly sharing your code, make sure Paula and Eric are given read rights on your code.
4. Submit your work by completely populating your row of the JSON sheet/tab of our master tracker which asks for links to your project code and a separate link to your JSON search criteria.

1. Create your very own 10x10 icon on a computer or on paper. Photograph/scan/save/export your icon. Save it in a directory inside your git repo called "personal_icon_manipulation". Push your changes to the public server.
2. Create a program plan for carrying out icon input and display. This should include your overall inputs and outputs, and how your internal functions are connected to transform inputs to the desired outputs. This can be a flow chart or well-written pseudocode/code comments
3. Begin coding your icon project and draft questions to discuss next week in class

Icon project target completion date: Saturday 16-OCT'21

Fully bake and push your code for your icon project by start of next week.

If you were absent this week, please call Eric 412.894.3020 to sign up for a topic.

Prepare peer tutorials

Upload peer topic reference

Continue Peer Challenges

Choose one of your peer topics to test on your own by baking in one of the peer topics into an existing python project you've made so far. Prepare to share your application of one of your peers' topics next week.

Choose (maybe test?) an API

Choose an API topic and even an inquiry question about data that can be sourced from an API avaiable on the internet. If you time, experiment with the Donors Choose API.

Implement peer topic in your API projecect and push to git

Choose a topic presented by one of your peers (not your own) and make use of niftiness in your API project. Log the topic you implemented, notes about how and why you did so, and a link to a git repo that contains a pushed version of your code whose commit message contains the text "peer topic". Log your work in the sky-blue sheet/tab of the tracker spreadsheet called "API_implement_peer_topic"

Chip away at your API project, attempting to pursue a particular inquiry question that is answerable with data from your API backing data set (i.e. the data). Next week will be a consultation time as well + an introduction to Scraping since we had a small crew this week in class.

1. Get working code that scrapes an HTML page
2. Optional: Add one embellishment to your code: database interaction, pandas vis, link-following
3. Describe your project in a readme.md file and include a screen shot of both your output and the HTML your BeautifulSoup scrapes. See this sample markdown file with an image; just include the image file in the same directory as your markdown file
4. Push your completed project to your github and insert link in our master tracker

Begin your final project

Make an entry in our master tracker spreadsheet

Fully bake final project and prepare for sharing

See sample git repo with screen shots and conclusions written in markdown

Use our master markdown tutorial to create a readme.md