uva-dsi / 2017-doathon Goto Github PK

Some examples from London:

• Here is a remote project pitch for issue 36: R interface to anthropology database D-Place.
• Here is an in-the-room pitch for issue 35: Newbies guide to Wikidata.

Given that the space is limited (see #6), we will need some mechanism for on-site people to register. This should also help with planning food (#22).

For planning purposes, it would be useful to have an indication as to how many remote attendees we are to expect, so perhaps that registration mechanism should be aware of the options of on-site and remote participation (possibly separately for the two days).

Could e.g. be a Google form or an EventBrite page or something similar.

Could simply be #Doathon but something more specific might be useful.

to simplify schedule

Here's what we currently have in https://github.com/UVA-DSI/2017-doathon/blob/master/guide/on-the-day-instructions.md#arrivals :

Give people stick-on tags — in fact, give them many! To keep things visible at distance, have a tag each for:

• First name
• Contact (email / Twitter)
• Some words to spark conversation (aka metadata)

as per
http://www.opencon2017.org/satellite

Once you've entered the room or are joining remotely, let us know by posting a brief message in this ticket. For more detailed information about you, please use the Gdoc that we are using for collaborative notes.

The city of Charlottesville maintains its legal code here https://library.municode.com/va/charlottesville/codes/code_of_ordinances

https://library.municode.com/downloadarchive/12078 is where the updates are available
there is currently no API for this data

https://virginia.box.com/s/tlhle6y1fp8dphfop236da9lm5df932j

as per
http://sdg.iisd.org/events/world-toilet-day-2017/ .

We have GitHub and Twitter contact data for most of the attendees of the London event, so we could reach out to them to provide feedback once a stable structure is emerging here.

local agencies have multiple paper forms - we need a process for taking the forms and making them digital with front-end api and back end functionality

https://virginia.box.com/s/1r0htj3g95y94p7p7uwobrx4p5w19mdy is an example of a file

Mainly for the README but possibly for other purposes as well, especially when thinking about outreach for the event, as per #8.

Depends on numerous parameters, not the least of which is available space.

e.g. as per https://github.com/sparcopen/open-research-doathon/labels .

As per #1 (comment) , we have OpenGrounds from 8:00 - 5:00 on Saturday and 8:30 to 5:00 on Sunday.

otherwise might be difficult to find

Scholia is

• a website that displays bibliographic information from Wikidata: https://tools.wmflabs.org/scholia/
• a reference manager for BibTeX: https://github.com/fnielsen/scholia/blob/master/scholia/tex.py
• free and open source software: https://github.com/fnielsen/scholia

as per http://tasks.hotosm.org/

Depends on having defined them first, as discussed in #7.

Should be nearly effortless to share. Could just be a GitHub ticket — see example.

We're looking into https://opengrounds.virginia.edu .

as per sparcopen/open-research-doathon#23 .

should

• be fun
• be useful
• be short

Path of Exile items are sold on player driven market. The historical transaction data is available through an API in JSON format. I already wrote a tool that pulls the data, preprecesses it and puts it in a SQLlite database.

We could try applying different machine learning algorithms to predict prices on new items.

e.g. https://www.meetup.com/CharlottesvilleDataScience/
or http://www.opencon2017.org/satellite

ideally in a way that highlights some underlying or related data

https://labs.loc.gov/experiments/congressionalchallenge/

perhaps starting with pointers from
sparcopen/open-research-doathon#18 .

basically a reminder plus any updates, sent out to everyone registered via EventBrite

try to find some public records of such events that have been organized in C'ville over the past 2 years, and see what we could learn from them.

That is, beyond the name tags covered in #13.

Here's what we currently have in https://github.com/UVA-DSI/2017-doathon/blob/master/guide/on-the-day-instructions.md#getting-to-know-each-other--the-topic :

Break people out into groups (anywhere from 5 - 8 usually works well) to get to know one another & the topic. Suggested structure can include:

• Have introductions of people
  • What’s your name / Twitter
  • What have you come here to do?
• What type of data are you interested in
  • e.g. genomic data, MRI data, word frequency
• I know a bit about...
• What would you like to see happen today
• Introductions to the topic
  • Here just allow folks to discuss what's on their mind.
    Encourage new folks to speak up and ask the silly question.
    For these sessions, use a Google doc (or similar) to take notes on introductions & questions collaboratively. Later, these can be reviewed by everyone to get a deeper idea of who's attending in the room and online. Think about providing in-room references for people to indicate where they are (e.g. number the tables).

Tweet each introduction into your hashtag.

Should be healthy and affordable and provided in a way that blends in with the activities, rather than distracting from them.

https://data.worldbank.org/indicator

World Bank provides a variety of data on different topics, especially demographics and economics.

Not sure yet what's needed here, but seems useful to think about a bit.

https://github.com/sparcopen/Open-Research-doathon/issues?q=is%3Aissue+label%3Ameta+sort%3Acreated-asc

The "help wanted" label can only be used by people who are listed as collaborators on the repo. So we either need to get everyone registered as such or have another (possibly additional) mechanism.

as per #8 (comment) .

Mined from Daniel's previous ideas:

Earthquake Data:
Daniel-Mietchen/ideas#422

Annotate Eagle pages:
Daniel-Mietchen/ideas#422

Data model for drug dosage:
Daniel-Mietchen/ideas#403

Indexing hospitals:
Daniel-Mietchen/ideas#358

Index papers for 'follow up'
Daniel-Mietchen/ideas#567

Collections of datasets used for data science learning:
Daniel-Mietchen/ideas#409

e.g. as per https://twitter.com/codingdavinci/status/921661904250195968 .

as per http://www.charlottesville.org/drought

See also the 2017 Annual Water Quality Report

For inspiration, see https://github.com/sparcopen/open-research-doathon .

Apart from the obvious ones like

• software developers
• data scientists
• open data folks
• UX designers

there may be some less obvious ones, e.g. stats folks from Charlottesville or Albemarle County, or designers more broadly (i.e. not just UX) and possibly artists, journalists and others.

as per http://www.cvillepedia.org/