On Arna's "Settings Manager", should devices be specifically designated public vs private? On private devices, individual items could be explicitly added to the workspace. "Everything" done on public devices would be potentially saved.
(mjr)
Also relating to the "Settings Manager" -- do devices need to be added manually, or does the infrastructure of iSpaces allow for automatic detection of which devices are present? Can some level of auto-detection be used to suggest default devices present, and more can be added/removed manually? Should there be something laptop users can click that says "add my device"?
(mjr)
Should mappings be manually specifed or automatically generated? Perhaps they can be automatically generated, but the convener gets to preview them and has the option of altering the mapping before accepting it. Potentially interesting topic to explore: what sort of visualizations of the mapping would be useful? How are mappings automatically generated?
(mjr)
What should be logged? Probably everything that can be logged... better to have the data and not use it than to need it and not have it.
(mjr)
What state should a file be in when it is saved -- the original, final, or some intermediate state? Perhaps we can compare the original and final state of a document during the course of a session, and have the saved version have the content of the final version, but with all modifications during that session hilighted.
(mjr)
What are all the possible applications, files, etc that we might want to save from a session? Merrie will work on a list of these things for next week.
(mjr)
What defines a distinct "session" -- the time it occurs? the people involved? the location? some combination? Two distinct sessions could occur simultaneously if person A and person B are each working from their homes adding things to the same workspace unaware of eachother. But one session could span two distinct locations as in the case of a joint mtg between Stanford and Sweden. So neither time nor place by itself distinguishes sessions...
(mjr)
Arna's "Workspace Navigator" concept for searching among all possible workspaces. Modification -- should be able to search for a workspace by date and time in addition to project name and people present.
(mjr)
Arna's "Meeting Manager" concept -- decided the capability of dragging a file to a spot to add it to the workspace was redudant with the ability to press the "save state" button.
(mjr)
Should people have to be identified somehow? Yes, because private logins or documents might be associated with them, and it might not be appropriate to bring them up if that person is not present. How? Ideally, in the somewhat-distant future things like automatic face recognition would do this, but for now scanning in (like w/ RedBoard) supplemented by the ability to manually add people to a session will have to suffice. Semi-related: maybe the system can automatically generate a summary/minutes and email them to associated members who were absent...
(mjr)
In addition to opening or closing the workspace "application", are specific start and end buttons needed? Probably the opening of the workspace app suffices to implicitly start a new or continued session, but an explicit End button might be nice to insure that people log out and can then use those surfaces for non-logged activities.
(mjr)
How much do we want things to be automatically logged versus things being explicitly added? Is our design focus more on something like a meeting where all details are auto-captured, or on something like an IDEO project room where things must be explicitly attached to the wall, or something in between?
(mjr)