veyepar: Open information: Documenting data and methods

Hi user

Admin Login:

Name: Open information: Documenting data and methods
--client lca --show lca2016 --room r4mix 10835 --force
Prev: 12 Open Data + Video Games = Win
Next: 12 Prying Open Government - An Introduction to Freedom of Information

show more...

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

final audio

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:	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 markdown
Comment:	production notes

2016-02-02/12_10_24.dv Apply: 12:14:36 - 13:20:21 ( 01:05:45 ) S: 12:10:24 - E: 13:20:21 D: 01:09:57 (Start: 252.0) show more...

vlc ~/Videos/veyepar/lca/lca2016/dv/r4mix/2016-02-02/12_10_24.dv :start-time=0252.0 --audio-desync=0

	Raw File	Cut List
	12:10:24		seconds: 252.0 Wall: 12:14:36
Duration	01:09:57
	13:20:21		seconds: 0.0 Wall: 12:10:24
Comments:
mp4 mp4.m3u	dv.m3u	Split: Sequence:: delete

audio viz

2016-02-02/13_20_19.dv Apply: 13:20:24 - 13:44:51 ( 00:24:26 ) S: 13:20:19 - E: 13:44:51 D: 00:24:32 (Start: 5.284267) show more...

vlc ~/Videos/veyepar/lca/lca2016/dv/r4mix/2016-02-02/13_20_19.dv :start-time=05.284267 --audio-desync=0

	Raw File	Cut List
	13:20:19		seconds: 5.284267 Wall: 13:20:24
Duration	00:24:32
	13:44:51		seconds: 0.0 Wall: 13:20:19
Comments:
mp4 mp4.m3u	dv.m3u	Split: Sequence:: delete

audio viz

2016-02-02/13_44_50.dv Apply: 13:44:50 - 13:44:54 ( 00:00:04 ) S: 13:44:50 - E: 13:45:13 D: 00:00:23 (End: 4.523288) show more...

vlc ~/Videos/veyepar/lca/lca2016/dv/r4mix/2016-02-02/13_44_50.dv :start-time=00.0 --audio-desync=0

	Raw File	Cut List
	13:44:50		seconds: 0.0 Wall: 13:44:50
Duration	00:00:23
	13:45:13		seconds: 4.523288 Wall: 13:44:54
Comments:
mp4 mp4.m3u	dv.m3u	Split: Sequence:: delete

audio viz

Rf filename:	root is .../show/dv/location/, example: 2013-03-13/13:13:30.dv
Sequence:
get this:	check and save to add this

2016-02-02/12_10_24.dv
audio viz

audio viz

2016-02-02/13_20_19.dv
audio viz

audio viz

2016-02-02/13_44_50.dv
audio viz

audio viz

Veyepar Video Eyeball Processor and Review