View Source

Space to plan our hack day.

h2. Plan/Activities:
|F|M|F|1475143637846| |pmay|Setup a google document|
|F|M|F|1475140022989| |pmay|Write blog post/email to publicize hack day|
|F|M|F|1475144396035| |pmay|Create google hangout|
|F|M|F|1475144257590| |pmay|Setup GitHub Issues Milestone & tag|
|F|M|F|1475074685394| |pmay|Setup JHOVE GitHub wiki with errors page for each module|
|F|M|F|1475074706668| |pmay|Create a DIG "errors team" on GitHub?|
|F|M|F|1475074350607| |pmay|Ensure Wiki error messages are complete against the full set (Carl's error message list)|
|F|M|F|1475143877369| |pmay|Document mechanism for adding error details to wiki|
|F|M|F|1475057275366| |becky mcguinness|Add more explanation / background information to errors (ML)|
|F|M|F|1474894948570| |yfriese|Add examples to the existing JHOVE error messages|
|F|M|F|1475140847910| |pmay|Determine impact of error messages and add to wiki|
|F|M|F|1475139853326| |pmay|Add less technical information about PDF elements to wiki - e.g. PDF Objects, Page Trees, etc.|
|F|M|F|1475139750015| |pmay|Translate information from German Wiki|
|F|M|F|1475144810716| |pmay|Review JHOVE website|
|F|M|F|1474275711727| |pmay|Improve JHOVE for beginners guide|
|F|M|F|1474275864776| |carlwilson-bl|Bring JHOVE beginners guide into official JHOVE fold|
|F|M|F|1474895120673| |yfriese|Add TIFF error messages to the wiki|
|F|M|F|1474895133109| |yfriese|Add JPEG error messages to the wiki|
|F|M|F|1475139920535| |pmay|Collate aggregate stats on incidence of errors seen across institutions|
|F|M|F|1475074550142| |pmay|Migrate wiki error messages from OPF wiki to JHOVE GitHub wiki|
|F|M|F|1475157377098| |becky mcguinness|Documenting and using JHOVE black box tester|

h2. Open Questions

# What about Carl's error messages list? Will it be somewhere / start somewhere before the 11th?
# Will the wiki cope with multiple people editing it? Or, how should people work to edit it?
# Someway to manage who's working on what error? Trello board??
## Should we have a fine grained list of actions, e.g. 1 action per error code so hack outcome can be quantified better?