• Smart Room Use Case Number One
Skip to end of metadata
Go to start of metadata

Researchers add some math problems to RoOLO, with metatags for:

  • Problem ID
  • Solution ID (more than one)
  • Subject area
  •  
  •  

Students add Solutions to RoOLO, with metatags for:

  • Problem ID
  • Contributor
  • Subject Area
  • Other Folksonomic tags (Grade level, sub-subject tags, etc.)
  • Connections to other problems (here I'm not sure if we make it explicit for students to connect problems... which I actually think would be good or if they are implicit and just form naturally from the tagging)

Agents/System adds to the above added objects (solution/problem)

  • Who created object
  • Who has edited object (commented, connected, or changed)
  • Who has viewed object (view count and names(question))
  • Which problems are connected to each other (see above... could also do an Amazon thing "Other students who have looked at this problem also looked at..."

3 distinct cases for the room itself:

Case 1: Single student uses the room for a massive embedded computational visual immersed experience - having all 8 displays to help them make sense of the world

  • Student walks up to one machine (the Mac server - which easily runs 8 displays)
  • The student clicks on an icon that is sitting on the desktop
  • That icon launches a Web application, called "UTS Smartroom Start Page"
  • The student logs in to the application, which is sitting on top of our ENCORE portal
  • The Smartroom Application loads into the Web, with things that the student has permission to see.
  • The student clicks on "Mr. Miskew's Math Misadventures" which loads up a Flash application that was authored by Mike and Michelle as a "starting place" for the smartroom math experience (note - they are still logged into the portal here).
    • the Math Flash app presents the student with several options, such as adding a new problem, adding a new solution, or viewing a problem or a solution.
    • When you're viewing a problem, it comes up as a separate window, and has some functions like "tag the problem" "add a solution" etc. (somewhere here there needs to be an area to add comments/dialogue to the question)
    • All these problems and solutions and tags, etc are saved in the RoOLO, as well as who added them
    • Student's can also select an option to view "other similar problems", which will grab problems with similar metatags and display them
      • either on the main screen using Michelle's visualization interface or pop them up on the other screens int he room - here I think it would be cool if it popped up first on the main screen using Michelle's and then students could either drag or just "click-to-pop" individual problems to each of the other screens in the room
    • Students can then look at each problem, and select either which one to take control of to edit/add to, or "save to my profile" as a favorite to bring up next time they log into the Portal (like a bookmarks feature)
      • Student can also also "follow" a problem, where they can be updated by e-mail on their HLD (Handled Learning Device) or when they log into the room if problems they've selected have been updated (someone has posted a solution, commented on, or connect to that problem/solution)

Agents get created - perhaps a good way of thinking about the definition an agent as services that are specific to the functions that are needed. like a "viewlog agent", which purposes to log all "view" events (maybe sort of attached to the "view" button.)

Case 2: (builds on Case 1)
Single group of 2 or 3 or 4 or ? students uses the room for a massive embedded computational visual immersed experience - having all 8 displays to help them make sense of the world. Basically, their being in a group makes the content of the room change, according to their overlapped or combined contents/interests/etc.

Case 2: Multiple students or student groups work in parallel in the room, possibly affecting each other, but generally trying to get the same kind of experience -where they are learning from visual displays and semantic relationships among math problems and solutions.

  • Students walk into room and pick up a laptop (or go to a workstation) - they log in and the system tells them to go to a specific screen (team1=screen1, team2=screen2, etc)
  • When students get to a screen it loads up their visualization (so here's something that depends on how we set up the room... if we use the projectors as the main display and the small screens as sub-displays then it affects how the interactions would occur... if we could do this it would be pretty cool but may be difficult to coordinate... would love some technical advice on this)

Questions and Concerns raised during the Fri March 27 '09 Meeting

TECHNOLOGY QUESTIONS

  • How many users can interact with the sandbox at the same time?
  • How do students claim a screen?
  • How do we separate/control output devices? (ideas: single sever with 8 different machine; One single server speaking to the application or instances of an application directly)
  • What type of DATA we want for input and what DEVICES do we use for input (math formula and PDAs, Wacom (tablet))
  • Developing an approach for collaborative groupware
    Collaborative Groupware: software designed for various members of a group receives a different view, does different tasks and creates different products from the others. Products from all members of the groups are synthesized in a single view. (S3 specifications page)
  • How do we allow students to seamlessly enter complex mathematical formulas?
    • There is a W3C standard XML language called MathML
    • There are some flash apps out there such as MathMLFormula

PEDAGOGICAL QUESTIONS

  • Mike and Carlos have to come up with these concerns

Agents

  • We need agents to be able to guide the student as the student does some work.
  • Agents to invoke collaborations between two or more students

Flash Tool

  • Connect to Roolo
  • Connect to agents
  • Refer to this document for the math-flash application's specifications

Assumptions

  • We will have 8 screens ONLY with the sandbox being multi-touchable.
  • No labels