'Reshaping the Art Museum'

I'm sneaking a moment from revision to point you to this thought-provoking article 'Reshaping the Art Museum' in Artnews:

To an unprecedented degree, market research about the needs, wants, fears, and anxieties of visitors is shaping how museums are designed. "We got a lot of comments that it's just overwhelming to come to museums," says Lori Fogarty, director of the Oakland Museum of California, which inaugurates a complete reinstallation of its art, natural history, and science collections this fall. So the new galleries will feature "loaded lounges" where visitors can relax, read catalogues, or do hands-on activities, along with open spaces that accommodate up to 25 people for concerts, storytelling, or other such programs.

But a bigger change in her plan is connecting people who might never have visited art museums with the people who curate them. Fogarty calls it transparency—"breaking the fourth wall"—having curators answer questions about how and why they choose works. Visitor feedback will be encouraged, and the exhibitions, in turn, will be based on the "wiki model," with curators representing only one voice in a mix that includes conservators, community members, and artists. "We can't count on the fact that potential visitors were brought to museums as kids," Fogarty says. "Many have no cultural or experiential reference; they don't think of the museum as a place that welcomes them or has anything of interest to them."

At the Walker Art Center in Minneapolis, director Olga Viso is also using a major reinstallation as an opportunity to remake the museum into a more civic space. "We want to be in dialogue with the audience instead of in the place of authority," as she puts it. Such efforts may mean involving the community in the organization of shows or asking people to vote on the selection of artworks. When the new installation opens in November, says chief curator Darsie Alexander, curators will hold in-gallery office hours—giving visitors insights into the way exhibitions happen, and giving the staff a chance to find out "how visitors encounter work in space—the kinds of questions they ask about art, what they find interesting, and how long they stay."

...

And for all the innovations in programming, marketing, and education, Campbell argues, the core mission remains the same. "We can make ourselves more user-friendly, but ultimately one of the key experiences of visiting a museum is that moment of standing in front of an object," he says. "Suddenly you're responding to something physical, real, that changes your own perspective. And great museums will always do that, as long we get people through the doors."

Final thoughts on open hack day (and an imaginary curatr)

I think hack days are great - sure, 24 hours in one space is an artificial constraint, but the sheer brilliance of the ideas and the ingenuity of the implementations is inspiring. They're a reminder that good projects don't need to take years and involve twenty circles of sign-off, even if that's the reality you face when you get back to the office.

I went because it tied in really well with some work projects (like the museum metadata mashup competition we're running later in the year or the attempt to get a critical mass of vaguely compatible museum data available for re-use) and stuff I'm interested in personally (like modern bluestocking, my project for this summer - let me know if you want to help, or just add inspiring women to freebase).

I'm also interested in creating something like a Dopplr for museums - you tell it what you're interested in, and when you go on a trip it makes you a map and list of stuff you could see while you're in that city.

Like: I like Picasso, Islamic miniatures, city museums, free wine at contemporary art gallery openings, [etc]; am inspired by early feminist history; love hearing about lived moments in local history of the area I'll be staying in; I'm going to Barcelona.

The 'list of cultural heritage stuff I like' could be drawn from stuff you've bookmarked, exhibitions you've attended (or reviewed) or stuff favourited in a meta-museum site.

(I don't know what you'd call this - it's like a personal butlr or concierge who knows both your interests and your destinations - curatr?)

The talks on RDFa (and the earlier talk on YQL at the National Maritime Museum) have inspired me to pick a 'good enough' protocol, implement it, and see if I can bring in links to similar objects in other museum collections. I need to think about the best way to document any mapping I do between taxonomies, ontologies, vocabularies (all the museumy 'ies') and different API functions or schemas, but I figure the museum API wiki is a good place to draft that. It's not going to happen instantly, but it's a good goal for 2009.

These are the last of my notes from the weekend's Open Hack London event, my notes from various talks are tagged openhacklondon.

Tom Morris, SPARQL and semweb stuff - tech talk at Open Hack London

Tom Morris gave a lightning talk on 'How to use Semantic Web data in your hack' (aka SPARQL and semantic web stuff).

He's since posted his links and queries - excellent links to endpoints you can test queries in.

Semantic web often thought of as long-promised magical elixir, he's here to say it can be used now by showing examples of queries that can be run against semantic web services. He'll demonstrate two different online datasets and one database that can be installed on your own machine.

First - dbpedia - scraped lots of wikipedia, put it into a database. dbpedia isn't like your averge database, you can't draw a UML diagram of wikipedia. It's done in RDF and Linked Data. Can be queried in a language that looks like SQL but isn't. SPARQL - is a w3c standard, they're currently working on SPARQL 2.

Go to dbpedia.org/sparql - submit query as post. [Really nice - I have a thing about APIs and platforms needing a really easy way to get you to 'hello world' and this does it pretty well.]

[Line by line comments on the syntax of the queries might be useful, though they're pretty readable as it is.]

'select thingy, wotsit where [the slightly more complicated stuff]'

Can get back results in xml, also HTML, 'spreadsheet', JSON. Ugly but readable. Typed.

[Trying a query challenge set by others could be fun way to get started learning it.]

One problem - fictional places are in Wikipedia e.g. Liberty City in Grand Theft Auto.

Libris - how library websites should be
[I never used to appreciate how much most library websites suck until I started back at uni and had to use one for more than one query every few years]

Has a query interface through SPARQL

Comment from the audience BBC - now have SPARQL endpoint [as of the day before? Go BBC guy!].

Playing with mulgara, open source java triple store. [mulgara looks like a kinda faceted search/browse thing] Has own query language called TQL which can do more intresting things than SPARQL. Why use it? Schemaless data storage. Is to SQL what dynamic typing is to static typing. [did he mean 'is to sparql'?]

Question from audence: how do you discover what you can query against?
Answer: dbpedia website should list the concepts they have in there. Also some documentation of categories you can look at. [Examples and documentation are so damn important for the update of your API/web service.]

Coming soon [?] SPARUL - update language, SPARQL2: new features

The end!

[These are more (very) rough notes from the weekend's Open Hack London event - please let me know of clarifications, questions, links or comments. My other notes from the event are tagged openhacklondon.

Quick plug: if you're a developer interested in using cultural heritage (museums, libraries, archives, galleries, archaeology, history, science, whatever) data - a bunch of cultural heritage geeks would like to know what's useful for you (more background here). You can comment on the #chAPI wiki, or tweet @miaridge (or @mia_out). Or if you work for a company that works with cultural heritage organisations, you can help us work better with you for better results for our users.]

There were other lightning talks on Pachube (pronounced 'patchbay', about trying to build the internet of things, making an API for gadgets because e.g. connecting hardware to the web is hard for small makers) and Homera (an open source 3d game engine).