Skip to content

09.16.21

Jump to bottom
Nic edited this page Sep 16, 2021 · 1 revision

The first quarter we are going to split time each week into 75/25

  • 25 is yours - to do whatever you want that gets us towards research valuable to PIT
  • 75 is explicitly about research design, execution, analysis, and writing

My goal for for the first quarter is to help build up your publication record. Reading, analyzing data, designing research etc will be much more enjoyable by doing and reflecting, rather than only reading and planning (which is most of what your coursework will include)

Each week we should meet twice:

  1. To plan for the week and go over interim work
  2. To review the weeks work and plan for next week

We should, in our second meeting of the week, always have a paper to read and discuss.

Some other things to get started

Week 1

  1. Write: JOSS paper on V3

5 hour limit on first draft

Send to Nic for review after ~5 hours of writing.

Goal - Jackson fist author software publication Outlet - JOSS

  1. Research Design: Version Control for Data: A not so great idea whose time has come https://github.com/BITS-Research/Ideas/issues/1

6 hour limit:

  • 2 hours - develop a table of different applications that SVC or some diff-ing of data - include key features, notes on differences etc
  • 1 hour - find three openly accessible datasets to use in each application
  • 3 hours -

Goal - Jackson first author comparative analysis (soup to nuts research) Outlet - PeerJ-CS

  1. Scheme: RFP for Github research https://github.blog/2021-08-31-request-for-proposals-defining-standardized-github-metrics/

3 hour limit:

  • 1 hour - read proposal and brainstorm metrics that may be interesting to collect and report
  • 1 hour - see CHAOSS https://chaoss.community/metrics/ - think about how these build upon, differ from, or relate to your brainstorm
  • 1 hour - write up a proposal - what would you do, why would it be useful, etc - pay attention to what the RFP is asking

Goal - Come up with fun, interesting, and useful proposal Outlet - submit proposal by 10.04

  1. Help: 2021 Mayoral Elections Accessibility Project

No hour limit (ongoing)

  • Look at repo - Help Anay with logging where violations occur, and identifying localization info

  • Prototype a way to fit data into candidate emails (or a document we can cut and paste into an email)

  • Brainstorm analysis of violations - Violation frequency, frequency per race, per party, per position, etc

  • Investigate how we might do some analysis of candidate translations

    • At very least we language spoken in jurisdiction (American Community Survey)

Here is the design (in broad strokes):

  • ID candidates running in 2021 elections

  • Analyze websites

    • Accessibility violations
    • Language localization / translation

  • Send notice about violations - offer help

  • Re-run accessibility violation checker:

    • 2 weeks from first notice
    • 1 week before election

Report

  • descriptive stats and relationships observed
  • inferential stats on effect of intervention (e.g. tests like - potential outcomes, Difference in Difference, latent factor models)

Goal: Fodder for 2022 midterm elections Outlet: Journal of Information Technology and Politics or Government Information Quarterly or JASIST

Clone this wiki locally