Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

DIA Feedback Synopsis

Present: FE: James, Colin, Alison, Leah, Vicki, DIA: Jennifer, David and Amy

...

The context of the wireframe is based on the scenario found on the Spatial Mapping page: See 2.2 In-museum kiosk: Printable Brochure.

The walkthrough of the Inin-museum kiosk wireframes can be downloaded here (in the Spatial Mapping section under the title Wireframes): http://wiki.fluidproject.org/display/fluid/Fluid+Engage+Designfound here: Kiosk UI design, draft 2

Clarity around semantical issues was made clear by the DIA and more concerns were expressed around the viability of tagging objects and mapping the museum space. Issues stated in the previous teleconference around scalability, usability and sustainability remain, and further research is needed in the following areas:

...

  • Who will be using the kiosk? Will people be assisted by a docent?
  • What information are visitors looking for related to the actual collections? (ie: Artists, Activities, Objects, etc)
  • Do visitors want to combine collections or particular objects from different collections in a single tour?
  • How can the kiosk provide a way for visitors to give feedback?
  • Can the visitors rate a tour?

Spatial Mapping

  • How will the mapping feature work given the massive scale of objects in the museum?
  • What will the map look like? (3D, photo-realistic, schematic, etc)
  • What are its affordances? 
  • How does the map update itself once objects move around?

Information

  • On the kiosk, what/how much information should be given about each collection? Artifact? How will this compel people to see an object?
  • Do we provide images? Collages? Music? Video?
  • How do we facilitate visitors' need to 'discover' and 'explore' without giving out too much information about the collections?

Recommendations (by Vicki):

  • We could start developing the project in two phases: 
    • Phase one would focus only on the "Featured Gallery Tours" and the "Museum Staff" backend (how they input information) sections only. 
    • Phase two would look at developing the "keyword search" feature.
  • More work needs to be done in regards to understanding how the backend would function (i.e. FE - couch DB, with the DIA's TMS) and workflow with between the interpretive and curatorial staff in producing gallery content.
  • It may be necessary to conduct a feasibility study to see how much it would cost the museum to maintain the system and printers, etc?.

Detailed Notes (Transcript in Coles notes)

Introduction: [James]
Design goals: this kiosk is a combination of the 'Family Fitting Room' and the museum brochures

...

  • The preview on the left is going to be very tricky. [David]
  • How are you going to represent this map? It would be great if there was some kind of an animation that showed them how to go through the gallery. [DIA]
  • How do you properly define the path of the tour? Location? Time efficiency? [ALL]
  • I'm trying to see the benefit of coupling multiple tours? [David]
  • Maybe take objects of different tours and culminate these into one tour? [DIA]
  • Maybe a thematic tour and a collection tour together may be feasible. [DIA]
  • Need provision of different maps and tours and other provisions in the space. Maybe we could offer several maps of different touring options? [DIA]

Map features that could be helpful: [David]

...