FAQ
Brooklyn Museum Collection API
We are at the sixth month marker of our Collection going online and you may have noticed that we keep adding to the features as we go along. In the first month, we released our tagging game “Tag! You’re It.” In month two, our exhibitions database was redesigned and republished into the Collections area. In month five, we added records from our Library and Archives. As we stand at the six month marker, we are excited to tell you about the release of the Brooklyn Museum Collection API.
What is an API? Well…you can look at Wikipedia for a super-techy explanation of this, but for those of you who are not geeks a short translation: it’s basically a way outside programmers can query our Collections data and create their own applications using it.
Mike Ellis presenting in Amsterdam…this guy can really convince you if you give him a chance.
So, how did we get here? Recently, I was presenting at a conference in Amsterdam along with Nina Simon and Mike Ellis. Mike’s highly entertaining presentation was about encouraging the public sector to consider releasing their data so that the community of developers worldwide could take advantage and create wonderful things with it. In Mike’s own words “if you love something, set it free” and that idea was something that resonated with me. Mike is a practical guy and he talked a lot about the stresses of staffing at cultural organizations, that we can’t possibly do it all ourselves and he wanted to spread the news of the potential in allowing outside developers the chance to add their own talent and wealth to our data.
This presentation of Mike’s stayed with me as we’ve watched many developers in the Flickr community work with the materials at the Flickr Commons. Flickr’s API is very flexible and several very talented programmers are taking advantage of the materials at The Commons and doing interesting things with them. It’s been inspiring to watch and given that we are an institution with a community-minded mission, we recogonize that developers are a significant part of community on the web and one we’d like to work with moving forward.
So, you may be wondering what kinds of applications could benefit from our data. There’s a wonderful X factor to all this—that we just don’t know what interesting something that someone will come up with—so it is exciting to wait and see. One thing we do know is people within our own industry have been working to create various pan-institution collection databases. By releasing our API, Brooklyn Museum data can now be included in these endeavors without requiring more staff time from us (something that would have been impossible prior to the API). The API offers us a way to share our data in a very democratic way—the work we do on the API can benefit all developers working with our collection online—not just major projects coming out of the non-profit sector. Frankie Roberto: next time you are building something in your garage, please remember to get your Brooklyn Museum API Key and include us in the fun.
It should be said, that in looking for examples to guide us in the non-profit world, we didn’t find many, but there was one shining beacon of light coming from New Zealand. The National Library of New Zealand released an API recently (fabulous interview here) and we carefully looked at what they were doing, how they structured the Terms of Use. This was a terrific example to follow and we couldn’t have been happier to have it to consider as we moved forward with our own.
Tourist with ‘roo at the Taronga Zoo in Sydney!
Now, there’s a little bit of irony in all of this. Seb Chan at the Powerhouse Museum in Sydney has been asking me for three years to provide Brooklyn Museum data, so it could be integrated into D*Hub (awesome site run by the Powerhouse where designers can search many collections at once). For years I’ve been saying that getting the collection online was a higher priority—that we just couldn’t devote staff time to providing a data set for a specific project like this one. I think after three years, Seb got so darn tired of us putting him off that he just stopped asking, but as I write this, I’m in Australia and New Zealand for speaking engagements in both countries. Seb, I’m here to tell you come get that API key so we can finally do this and Courtney, I’ll be coming to thank you and your awesome forward-thinking team in person.
RSS 
Eastern Parkway/Brooklyn Museum
March 4th, 2009 at 3:03 pm
Well done, Brooklyn!! This is exciting on so many levels, I can’t wait to see what comes out of it and who you can get to follow suit on this… Hoping to find some time soon to apply for a key and start poking at your data!
March 4th, 2009 at 3:08 pm
OMG. You guys and gals did it again! Congrats on this innovation and I can’t wait to see the outcomes.
Cheers,
Jeffrey @ the MF
March 4th, 2009 at 3:10 pm
Oops you did it again. Well done.
March 4th, 2009 at 3:35 pm
[…] this is the shit. The Brooklyn Museum has released their online collections API. This follows a string of smart, with-it moves, such as the “Tag you’re it” […]
March 4th, 2009 at 3:52 pm
Congratulations Shelley & the rest of your team! We’re looking forward to seeing you over here.
March 4th, 2009 at 4:33 pm
Congratulations! That is really great news. Now lets see what we can do with this API . . . .
March 4th, 2009 at 4:53 pm
Curses! Can you please build a time machine now? Because you’re always 6-12 months in front of everyone, and it looks really cool there in the future.
March 4th, 2009 at 5:15 pm
Cool! We’re releasing one in a few months, I might bug you with questions about terms and conditions and other museum-type issues.
One question - did you have a design process for your API? Or are you just putting it out there as a v1 to see what gets used?
March 4th, 2009 at 5:48 pm
Agree with David Shelley keeps the BMA at least a year ahead of any curve you can draw. Just a regular genius…
March 4th, 2009 at 5:53 pm
Wow! Congrats and thank you!
March 4th, 2009 at 11:18 pm
Hello from Melbourne! Many thanks everyone for your kind words - if you’ve applied for a key we are a little slow to get those out in my absence, but will be in the next day (sorry, jetlage is a killer).
Mia! Ask away (shelley.bernstein@brooklynmuseum.org) to answer the quick question: this very much is v1. We actually are very excited to see a few friendly faces applying for keys - it’s going to help us get early feedback so we can make adjustments as they work with it - pretty darn exciting for us here!
March 5th, 2009 at 12:26 am
Congrats! But I’m pretty sure Mike didn’t coin the phrase, “if you love it, set it free…”
March 5th, 2009 at 2:32 am
congratulations to the BM team…again. i hope this inspires more of the same ’set it free’ behaviour from other cultural institutions. big thanks!
March 5th, 2009 at 6:48 am
Shelley, you have - genuinely - made my day. Thanks for the mention, but more to the point - nice one. I can’t wait to have a play
tfn
Mike
March 5th, 2009 at 8:48 am
Love it!
March 5th, 2009 at 10:09 am
Great news! You guys are amazing.
March 5th, 2009 at 9:00 pm
I made a few pipes to make quick mashups even easier.
Clone away.
http://pipes.yahoo.com/pdadamczyk/brooklynmuseumsearch
http://pipes.yahoo.com/pdadamczyk/brooklynmuseumgetitem
http://pipes.yahoo.com/pdadamczyk/brooklynmuseumgetimages
March 5th, 2009 at 9:03 pm
oh, sorry - all this data has me too excited - i meant to add…
Thank you so much!
March 6th, 2009 at 3:44 am
[…] Brooklyn Museum has its own API for its web collection! Read the museum’s announcement and visit the API site for more details. The National Library of New Zealand also has its own […]
March 7th, 2009 at 9:15 pm
[…] Brooklyn Museum released a collections API. That’s right, no more messy scraping and dealing with robots. Here’s a wrapper for the […]
March 8th, 2009 at 11:32 am
[…] in Wikipedia Loves Art, The Brooklyn Museum is an institution that simply “gets it.” On Tuesday, they launched an […]
March 9th, 2009 at 2:26 am
[…] week, the Brooklyn Museum released a public API, allowing outside programmers access to their extensive Collections Database. While the Flickr API […]
March 9th, 2009 at 7:45 am
[…] Museum Expansionism: Brooklyn Museum releases their Collection API into the wild. Soon, every museum will have an API. Save […]
March 17th, 2009 at 6:33 am
[…] Brooklyn Museum in New York heeft zijn catalogus geopend. Alle objecten in de catalogus zijn voorzien van een creative commons-licentie en mogen door […]
March 31st, 2009 at 11:53 am
[…] en catalogusgegevens) vrij te geven. Het Brooklyn Museum in New York heeft onlangs zijn catalogus geopend. Alle objecten in de catalogus zijn voorzien van een creative commons-licentie en mogen door […]
April 1st, 2009 at 2:49 am
[…] museum’s Chief of Technology Shelley Bernstein notes in the introduction that “we are an institution with a community-minded mission, we recognize that developers are […]
April 16th, 2009 at 9:24 am
[…] March 4th 2009, Brooklyn Museum announced the launch of their API, the latest in a series of developments around their online collection. Brooklyn […]
April 21st, 2009 at 10:44 am
[…] either, until I did a little poking around the Internet. Shelly Bernstein of the Brooklyn Museum wrote a very helpful explanation for all us non-programmers. Simply put, organizations can use APIs to open up their vast libraries […]
May 8th, 2009 at 3:44 am
[…] big museums like the Science Museum (London, UK), the Powerhouse Museum (Sydney, Australia) and the Brooklyn Museum (New York, US) releasing their […]
July 30th, 2009 at 2:29 pm
[…] in Wikipedia Loves Art, The Brooklyn Museum is an institution that simply “gets it.” On Tuesday, they launched an […]