![[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
Recommended
More Related Content
Viewers also liked
Viewers also liked (8)
Similar to Cosmic Collections: creating a big bang?
Similar to Cosmic Collections: creating a big bang? (20)
More from Mia
More from Mia (20)
Recently uploaded
Recently uploaded (20)
Cosmic Collections: creating a big bang?
Editor's Notes
- The Cosmic Collections project was based on a simple idea - what if we gave people the ability to make their own collection website? The Science Museum was planning an exhibition on astronomy and culture, to be called ‘Cosmos & Culture’. We had limited time and resources to produce a site to support the exhibition and we risked creating ‘just another exhibition microsite’. So what if we provided access to the machine-readable exhibition content that was already being gathered internally, and threw it open to the public to make websites with it? And what if we motivated them to enter by offering competition prizes? Competition participants could win a prize and kudos, and museum audiences might get a much more interesting, innovative site. The idea was a go od match for museum mission, exhibition content, technical context, hopefully audience - but was that enough?
- The project gave me a chance to investigate some specific questions. At the time, there were lots of calls from some quarters for museums to produce APIs for each project, but would anyone actually use a museum API? The competition might help us understand whether or how we should invest in APIs and machine-readable data. We can never build interfaces to meet the needs of every type of audience. One of the promises of machine-readable data is that anyone can make something with your data, allowing people with particular needs to create something that supports their own requirements or combines their data with ours - but would anyone actually do it?
- I’m going to get the geek stuff out of the way and quickly define mashups and APIs... Mashups are computer applications that take existing information from known sources and present it to the viewer in a new way. Here’s a mashup of content edits from Wikipedia with a map showing the location of the edit.
- APIs tell a computer, 'if you go here, you will get that information, presented like this, and you can do that with it'. A way of providing re-usable content to the public, other museums and other departments within our museum - we created a shared backend for web and gallery interactives. I think of APIs as user interfaces for developers and wanted to design a good experience for developers with the same care you would for end users*. I hoped that feedback from the competition could be used to improve the beta API * we didn’t succeed in the first go but it’s something to aim for post-beta
- And on the next slides, the results. If I was replicating the real experience, you’d have several nerve-biting months while you waited for the museum to lumber into gear, planned the launch event, publicised the project in the participant communities... Then waited for results to come in. But let’s skip that bit...
- The results - here’s the second prize winning entry. People came to the party. Yay! Our judges declared a winner and a runner-up, these are screenshots.
- This is a screenshot from the winning site - it made the best use of the API and was designed to lure the visitor in and keep drawing them through the site. (We didn’t get subject specialists scratching their own itch - maybe they don’t need to share their work, maybe we didn’t reach them. Would like to reach researchers, let them know we have resources to be used, also that they can help us/our audiences by sharing their work)
- I did a small survey to evaluate the project... Turns out the project was excellent outreach into the developer community. People were really excited about being invited to play with our data.
- Also positive coverage in technical press. So in conclusion?
- There are a lot of opportunities and excitement around putting machine-readable data online...
- But people won't find and use your APIs without some encouragement. You need to support your API users. People outside the museum bring new ideas but there's still a big role for people who really understand the data and audiences to help make it a quality experience...
- What next? Have been thinking about how to improve APIs - offer subject authorities with links to collections, embed markup in the collections pages to help search engines understand our data... I want more! The more of us with machine-readable data available for re-use, the better the cross-collections searches, the region or specialism-wide mashups... I'd love to be able to put together a mashup showing all the cultural heritage content about my suburb; all the Boucher self-portraits; all the inventions that helped make the Space Shuttle work... Also been thinking about role of APIs and linked data (image from SciM universe). API = data. Data + meaning (vocabularies) = linked data - APIs are not enough? And what about shared museum standards suitable for use online?
- If you're interested in possibilities of machine-readable data and access to your collections, join in the conversation on the museum API wiki or follow along on twitter or on blogs. Join in at http://museum-api.pbworks.com/ More at http://openobjects.blogspot.com/ or @mia_out Full paper online at http://www.archimuse.com/mw2010/papers/ridge/ridge.html