veyepar: Open information: Documenting data and methods

Author(s):	Rhydwyn Mcguire
Location	D4.303 Costa Theatre
Date	feb Tue 02	Days Raw Files
Start	13:20	First Raw Start	12:10
Duration	0:25:00	Offset	1:09:36
End	13:45	Last Raw End	13:45
Chapters	00:00 0:24:26
Total cuts_time	24 min.

https://linux.conf.au/schedule/30352/view_talk
raw-playlist raw-mp4-playlist encoded-files-playlist host archive tweet mp4 svg png

assets release.pdf Open_information_Documenting_data_and_methods_2.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

Open data is great, Open data is amazing, but unless your users understand your data they can't use it.

Do you share or would like to share open data? Is your data adjusted in anyway? Have you cleaned it or removed outliers? Have you added a random spatial offset to anonymise it? Have you used age adjustment, or seasonal adjustment to reveal underlying patterns? Do your users know that you have done this? Do your users need an advanced degree to understand your documentation? Would a journalist picking up you data be reasonably expected to understand what it is telling them without talking to you?

Are there biases in your data? Are you catching every case or do you think that they are some cases that are not captured? Do your users understand how those missing cases and biases effect their use of your data?

Based on my work in medical statistics, I will talk about how to share data with methods and documentation to make data relevant and results reproducible and accessible. In open source we know a lot about documentation, UX design, technical debt and onboarding time. I want to ask how we can apply these ideas to developing open data

Comment:

production notes