2013 AOCR Hackathon Wiki: Difference between revisions

From iDigBio
Jump to navigation Jump to search
Line 8: Line 8:


=== [https://www.dropbox.com/s/p8zjm0ajaj838tw/HackathonIconfAgendaFinal.docx Day-By-Day Schedule] ===
=== [https://www.dropbox.com/s/p8zjm0ajaj838tw/HackathonIconfAgendaFinal.docx Day-By-Day Schedule] ===


=== Group Notes ===
=== Group Notes ===

Revision as of 18:19, 7 February 2013

Welcome to the 2013 iDigBio AOCR Hackathon Wiki

Day-By-Day Schedule

Group Notes

  • Please use AOCRhackNotes to Capture your ideas, insights collaboratively at our hackathon.
    • We are excited to use this process and have found it extremely useful for collaborating effectively!

Meetings

Links to Logistics, Communication, and Participant Information

Remote Participation

  • Remote Participation via AdobeConnect
    • Join us on Wednesday morning 9 AM - Noon CST to hear our hackathon participants report back to the group and share their progress on parsing algorithms.
    • Please sign in 15 - 20 minutes early to learn how Adobe Connect works.
    • Help with AdobeConnect
    • Want to try your skills at parsing? Share your User Interface ideas? Got mad skills for developing image-analysis and image segmentation algorithms? Know where the great authority files (data dictionaries) are? Do tell, via remote participation or in our online group notes doc.

Overview of the Challenge

Frequently Asked Questions

Deliverables

  • report on progress beyond parsing, accomplishments, and in-the-works
  • summary report on progress, including metrics evaluation
  • Development of OCR SaaS for use by the entire community.
  • code from participants (at github)
  • all participant's talks posted to the hackathon wiki, including links to their code, comments.
  • Participants talks and summary reports added to the iDigBio Biblio.
  • collected conversation / feedback from whole group (report back summary)
  • Social Media
    • photographs
    • post to Facebook
    • blog post to iDigBio
  • white paper on the hackathon process.

Choosing Images and Parsing Decisions

Issues that need work

*Thank you NESCent, Hilmar Lapp and the HIP working group for this model.