Meetings

GMT-0600 Today |        Week 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 2005 2006 2007 2008 2009 2010 2011 2012 2013 Mon, Apr 13 Tue, Apr 14 Wed, Apr 15 Thu, Apr 16 Fri, Apr 17 Sat, Apr 18 Sun, Apr 19

Calendars All Meetings and Teleconferences Data Cell Collaboration Cell Analytics Cell Meeting Add a calendar Please wait...

This Calendar is not being used

All-Hands Meetings (cell meetings are documented on the cell pages)

• Feb 23rd 2007 Meeting notes
• June 7th and 8th, 2007 (Urbana)  June 7-8 2007 Meeting notes

• December 14th and 15th, 2007 (Maryland)     Dec07-LOGISTICS

• July, 2008 (Finland)   CANCELLED (we decided to spend our money on smaller hackfests instead)

• PLANNED: December, 2008 (Northwestern)

Hackfests

• Kramer Pond Hackfest (August 2007)
• Feb. 7-10 Hackfest 2008 - Report: Chicago MONK Hackfest 2008 report v02.doc
• April 08 Mini Hackfest  2008 - in parallel at Montreal and Alberta
• May 19th-21st Mini Hackfest  2008 - in Lovely Urbana Champaign
• August 08 hackfest ??? FOR PICKING THE DATES  (this seem sto have fallen off the agenda????  What is happening)

Milestones:

Data Cell:

• Agree on preliminary data model for interoperability
• Agree on an API (or proxy, or whatever) for interfaces to address
• Agree on some ways of working across collections (where a collection is represented by an index)
• Assemble a collection of fiction from 1600 - 1920 (with some public domain texts included and identified)
• Reassess data model with early modern texts in mind
• Assemble a collection of early modern texts in various genres (with some public domain texts included and identified)

Uses and Users Cell:

• Three or four use cases documented, with actual users who are interested in doing them. At least one macro example, where the focus is at the collection level rather than on reading the individual texts.
• Have a users meeting with users who are within the project
• Generalize from these use-cases: what other like questions could be asked with this or other collections? What do these use cases have in common? How are they different from one another?
• Consider whether to recruit specific user communities (e.g., biblical scholars) and solicit their use cases, build tools for them
• Have a users meeting that snowballs from the project's users to larger communities

Interface Cell:

• Decide what functionality of the Nora and WordHoard interfaces we want to bring forward into MONK
• Decide what programming language or languages we will use to develop
• Specify affordances for user-supplied text
• Specify affordances for the extension or modification of the interface
• Define defaults and users for the interface (novice, advanced - others?) and specify the implications for the data-store
• Figure out how to navigate and browse large collections
• Figure out how to group and sort and select
• Integrate at least one macro (collection-level) visualization
• Integrate at least one collaborative tool

Analytics Cell:

• Inventory analytics that we already have in Nora and WordHoard
• Define some basic types of analysis, based on use cases
• Integrate those analytics in a common framework
• Expand the set of analytic tools and techniques (e.g., perhaps: Wordnet?)
• Investigate other types of analysis likely to be useful for literary study

Collaboration Cell:

• Public web presence for MONK
• Survey MONK's neighborhood: what other tools or environments are out there that MONK might want to integrate with?
• Propose specifications and use-cases for saving and sharing worksets, results, etc.
• Propose feed-formats for results (RSS?)
• Propose gate-keeping mechanisms for creating and managing sub-communities of users

SuperCell:

• Make sure it is clear to the chair of each cell who, within that cell, has responsibility for documentation, design, implementation, evaluation
• Order milestones and examine their contingencies, dates, etc.
• Identify and minimize contingencies and bottlenecks
• Define deliverables
• Decide how releases will be handled

Chicago MONK Hackfest 2008 report v02.doc (application/msword)