ATTENDING: Matt K., Greg, Catherine, Joe, Bill, Stan, James, Matt B., Martin

DISCUSSION

Discussion of the following from Matt K.:

Publication Models for MONK (Version 0.1)

0. Narrative description of MONK operations and narrative or tabular display of results.

1. Screenshot of MONK visualization or operation.

2. State-based "movie" of a MONK operation, allowing a reader to step backward or forward in the activity sequence. Will require a viewer for presentation. Viewer could be embedded in an arbitrary Web page--a refereed article in DHQ, say.

3. State-based access to MONK operations, allowing a reader to step into an activity sequence and take control of operations at an arbitrary point. Results exported to viewer for presentation.

4. State-based access to MONK operations, allowing a reader to step into an activity sequence and take control of operations at an arbitrary point, also altering or adding the dataset. Results exported to viewer for presentation.

5. Export of MONK analytics to a third party environment (for example, to ManyEyes).

Definition of a save-able point?

Every user action?

Mockups for publication models - viewer, etc.

Carlos in Alberta working on tutorial, similar

Embeddable viewer of MONK resource, allowing people to step through activities of MONK project, possibly with ability to edit results after re-entering MONK environment and signing in as a registered user

Do we want to make the "dynamic publication" a point of importance, or do we want to pass on that for reasons of time and/or resources?

o Experiment with a dataset, imagine how you would want to publish those findings - PowerPoint, video on YouTube, etc?
o If it's useful, we can imagine what would be the best way to publish results
o (YouTube would be very low-res, as in the Nora video - build a YouTube-like viewer with individual activities tied to state within the MONK environment)

Shift away from "demo" and "video" more toward "dynamic publication"

o publishable within electronic peer-reviewed journal
o ability to step backwards and forwards in sequence in this publication
o richer kinds of behaviors down the line
o offer to publish these publications on MONK site as a form of gallery

"Viewer" Scenario:

o user is reading a piece in a scholarly journal based on work done in MONK
o part of journal article is a sequence of MONK operations presented in viewer
o viewer offers opportunity to step inside MONK environment
o reader herself performs a sequence of operations on the same dataset or in a new dataset
o at some point, the reader wants to capture his or her publications to present on their own, as a response, on their blog, on the MONK gallery page
o to do that, the reader requires a platform to let their own sequence of operations to go back to the viewer

For the Data Cell:

o more precise about what a "saved state" is
o could be very complicated - everything a user is doing - or as simpler references to what a user is doing
o if a user would like to publish a state, there are going to be rights management issues involved
o fairly complicated and involving a fair amount of time

Fair use issues with viewer

o Viewer might allow a user some more hands-on experience in terms of their encounter with results derived from MONK, without necessarily letting a user back into MONK proper
o Could take a fairly aggressive use of what constitutes fair use material

o should plan early and often to provide research logging for ourselves

Distributed use (Martin):

o could we create a large enough and good enough library of public domain fiction so that we wouldn't have to worry about copyrights of any kind?
o OCR that is good enough for use within MONK - teamwork-oriented work
o For collaboration cell:
+ Not necessarily part of the collaboration cell
+ If MONK needs better archives, they should be built collaboratively, of interest to the collaboration cell
o system for this: possibly using Oxygen
o Wiki-like XML editing structure

Discussion of James' XML-editing system, features, etc.

o Six months to finish it and test it completely, generalize it
o Sounds like a good system for this kind of tagging project

ACTION ITEMS

o readings, posted by Matt B. (to be posted to Wiki)
o something the SuperCell should talk about at its next meeting, perhaps asking each cell to contribute to the discussion with its own articulation of what "state" means to them
o revise and elaborate on draft (Matt K.)