Posted by Heather Hart

Tim Hart from Museum Victoria in New Zealand, described the successes and challenges of bringing three separate museums together online. They worked together with management to develop an online strategy that encouraged broad ownership and cooperation. One of their biggest problems had been that their IT staff had been, seemingly paradoxically, much too focused on the actual technology. Finally they realized that it was so hard to create excitement for new projects because the rest of the staff had trouble understanding what they were even talking about. Instead, it was much more successful to find measurable objectives and focus on what the technology would do and how it would help everyone do their jobs better. By engaging their coworkers through an “online planning group” and making the process completely transparent with an online schedule of progress that was available to all staff, they were able to create a sense of ownership for their project and, therefore, it was much more successful from everyone’s perspective.

Stephanie Pau from the San Francisco Museum of Modern Art talked about the interpretive goals process that has been implemented at SFMOMA with a large degree of success. Instead of curators, educators, and technologists segregating themselves in the exhibit development process and creating distinct areas for themselves (“Now you’re viewing the exhibition”, “now you’re using the technology kiosks”, “now you’re in the education department”), SFMOMA facilitated a collaborative process in which all interested parties came together to develop exhibitions. The most important lesson from SFMOMA: more technology is not always better. Instead of worrying about volume, we should be focusing on using what technology we have in the most effective way.

I come out of this session reminded that, when it comes to technology, the question should be “why?” instead of “why not?”

 
Posted by Site Administrator

Unconference sessions

MW2009 Afternoon Session

16 Apr 2009 15:30

 

Google Book Settlement / Copyright issues

 

Sessions will begin at 4:15 and end at 5:30.

 

 

#1 Inclusive design for Web 2.0 for users with disabilities

#2 Managing social media for institutions

#3 Multilingual sites HOWTO

#4 In-source vs. Out-source debate. When does it make sense?

#5 Using social media sites to learn how people use social media sites

#6 Open and Linked data and Semantic

#7 Open source for mobile development Concept B

#8 Sustainability -- how does what we do help the bottom line of our institutions [6, combine with economic downturn] Regency C

#9 How does the web respond to multicultural/multiethnic community?

#10 Why is it so hard to fund museum technology proposals? (Mellen Foundation) Theory B

#11 Strangers talking to strangers.

#12 How to include users in website design

#13 Emerging communities and emerging technologies

#14 Scenarios for telling stories to bring data alive Regency C

#15 Design and development conflict

#16 Bringing the social online network inside the museum space (eg Matress Factory)

#17 Museum strategies during economic downturns. Can tech let us work smarter?

#18 Agile methodologies for internal and external development Regency A

#19 Pilot programs to use OMEKA [2]

#20 Return to physicality. Film search engines.

#21 Cartography of politics.

#22 Permanent identifiers for works of arts (pearls). [fold with semantic web] Regency D

#23 Vocabularies which can be downloaded to CMS

#24 Collaboration between ALA

#25 Progress enhancement -- engage with users? How are people using the sites?

#26 Attracting audiences on the web

#27 Intersections between oral history, social media, mapping Concept A

#28 Small to medium size inst. with small or no IT staff yet with big ambitions?

#29 What is the future of the Web for museums.

#30 How do you get buy in from admin for web projects?

#31 Do collections institute IP (Intellectual Property)? [4]

#32 Convergence between archives, libraries, collections? Theory B

#33 Syndicating museum content in an automated way [4]

#34 How to feel about failure?

#35 Other developers using Java?

 
Posted by Site Administrator

Mapping Museum Content

MW2009 Afternoon Session

16 Apr 2009 14:00

 

Application of Geographic Information Systems

 

"If you don't know where you are, you don't know who you are." --Wendell Berry

 

Place is as important as who and when.

 

"Waverly from South 13th St facing East" poses problems for geocoding.

 

Name changes are also an issue. Historic Street Name Index.

 

Error reports contributed by users.

 

1926 -- Sesqui-Centennial International Exposition -- temporary streets for exposition.

 

Initially developed before Google Maps.

 

Users often type in addresses into keyword searches. Now they use: address, keywords, topics, time period, collections, advanced.

 

What about a radius (box) search around a given address? Year ranges as well?

 

Fulfillment of photos?

 

Experimenting with RSS and GeoRSS.

 

Each month 2,000 photos added to site.

 

Allows bookmarking.

 

Does it allow any sort of tagging or comments?

 

Mobile technologies. http://mobile.phillyhistory.org

 

Added historic maps of Philly.

 

Added photos of murals treating the location as an asset rather than an individual photo and tying the photos to the asset.

 

Google Street View. Have to move around a lot to get a good view of the mural and save it. New API forthcoming to allow one to specify particular locations and angle views.

 

Doesn't seem to support tabbed browsing very well.

 

_____

 

 

Interpretation of Bias and the Bias of Interpretation

 

Flickr

 

Naming places gets tricky.

 

3B photos. 110M geocoded.

 

Geocoding (string to lat/long)

 

Reverse geocoding. Take a lat/long and get the name of the location. What neighborhood would be nice. Not easy.

 

Project: nearby (radio geocoding).

 

WhereOnEarth -- lists administrative zones on Earth.

 

Corrections project. 100,000 in the first week.

 

Open Street Maps (Buenos Aires) can work with Flickr

 

Clustr tool is an open source project to work with arbitrary sets of points using Alpha Shapes (ie scoop out the ice cream, leaving the chips)

 

Donut holes

 

EC2 -- on-demand virtual server

 

ws-clustr client/server software

 

py-wsclustr

 

Placeography

 

The MN Hist Soc has the largest coll in the univ of MN

 

Psychosynthrography

 
Posted by Heather Hart

A rousing plenary this morning by Max Anderson of the Indianapolis Museum of Art set the tone for MW2009 (complete with live twitter commentary, for better or worse). The IMA has set themselves apart during the three years that Max has been at the helm, cultivating a robust technology department, implementing an innovative site design, and striving to set a new standard for transparency in the museum world. The greatest example of this transparency is the IMA dashboard, which informs visitors of everything from the size of their endowment and the value of deaccessioned items to the average daily energy usage and number of plants on the grounds, plus much more.

You can view the speech in its entirety on ArtBabble, a recently launched art video sharing site and another one of the IMA's recent projects.

I agree with Max that museums would be well served to allow their visitors “behind the velvet rope” on the web. The idea of museum-as-sacred-ground that I grew up with inspires a kind of awe and reverence, to be sure, but not the kind of free-wheeling exploration, innovation, and engagement that builds a community. Everyone here at MW2009 is now anxious for the reception at the IMA tomorrow night.

 
Posted by Site Administrator

Technology Strategies

MW2009 Morning Session

16 Apr 2009 11:00

Cool information about Amazon Web Services and how it was used for the IMA ArtBabble video site. Sever instances and storage (S3) allowed for very inexpensive deployment of video.

Hoard.it is a museum item screen scraping project. Neat idea if we could coalesce the information from all of the BP museums in one place and allow tagging, Wikipedia links to creators, etc. Mentioned date translation system.

The Jewish Women's Archive has used a collection management system called Fedora (not the Linux distro of the same name) and Drupal to track their items. They moved to AWS for better distributed storage, etc. and seemed very pleased with it.