FE_Design_Research: Mapping

[Alison Benjamin]

This is a neat resource, thanks Tona.

I quite liked the Victoria & Albert museum's Interactive Baroque /
google map. It gave a global perspective on the genre, in terms of
which pieces came from where. Also, listening to baroque music while
browsing through the images makes using the feature feel more
immersive although I wasn't sure how the music pieces chosen related
to the objects.

Each photography piece looks like it has a number associated with it
(accession no? ) e.g: "V&A Museum no. 58-1949". It's unclear as a
visitor what I would do with that number.. would it lead me to the
room in the museum where I could find the object? So one thing that I
thought could be improved would be some sort of connection between
each piece and the Victoria & Albert museum's floor plan... a way of
showing "this piece came from this location in the world.. and if you
come to our museum you can see it right here."

Alison

On Fri, May 29, 2009 at 2:28 PM, James William Yoon
<james.yoon at utoronto.ca> wrote:
> Great compilation of what other museums are doing in the mapping space. I
> especially like MASS MoCA, Musee de Lyon, Musee d'Orsay, and Making the
> Modern World examples.
>
> There are a lot of things we could learn, adapt, and build on from these
> real-world implementations.
>
> For instance, in the Musee d'Orsay's implementation, they have open text
> fields to the right of the map, allowing users to search by artist, title,
> and other terms--something Antranig and I had a chat about while thinking
> about what FE might do. But it occurs to me now that a plain text field for
> searching the way they have it (and the way I thought it might work) doesn't
> make sense a lot of the time: as someone unfamiliar with the specifics of
> their collections and what's presently in their exhibition space, I had no
> idea what I might search for that would give valuable/substantial results.
> da Vinci? Dali? Pollock?--the map gave me nothing, and I got a bit
> frustrated. (eventually, I found that Gogh and Monet gave results) This
> suggests to me that we need to: 1. Prime the user to what they might look
> for, 2. Provide pre-defined yet open exploratory paths to content, and/or 3.
> Emphasize multiple avenues of getting at the content (or, as Dale mentioned,
> a faceted UI).
>
> Thanks for putting this excellent resource together, Tona!
>
> James
>
> On Thu, May 28, 2009 at 4:24 PM, tona monjo <tonamonjo at gmail.com> wrote:
>>
>> Hello,
>>
>> I've just published a new page on the wiki that contains some examples on
>> mapping:
>>
>> http://wiki.fluidproject.org/display/fluid/Mapping
>>
>> Sure you know other cases, so please feel free to edit it.
>>
>> Thanks!
>>
>> Tona
>> _______________________________________________________
>> fluid-work mailing list - fluid-work at fluidproject.org
>> To unsubscribe, change settings or access archives,
>> see http://fluidproject.org/mailman/listinfo/fluid-work
>>
>
>
> _______________________________________________________
> fluid-work mailing list - fluid-work at fluidproject.org
> To unsubscribe, change settings or access archives,
> see http://fluidproject.org/mailman/listinfo/fluid-work
>
>