Monthly Archives: January 2013

Curatorial Poetry

Curatorial Poetry

I made a fun thing…yesterday. In my 20% time, downtime, er.. 2am time, I decided to build a simple tumblr blog called Curatorial Poetry. I was inspired by Aaron’s take on our collection data and how he chose to present objects in our collection that have no image, but have a “description.” In the office we often have fun reading these aloud, or better, with Apple’s screen reader.

But, I thought it would be fun to “reblog” these in another form. So, I built a simple python script to do just that. To do this, I forked our collection data and wrote a short tool to convert our JSON objects into an sqlite3 database. I chose sqlite3 because, well, it’s light, and doesn’t require me to set up a DB server or anything.

Next, I spent most of my time trying to learn how oAuth2 works. It took me a good bit of time googling around before I realized that the python-oath2 library includes oAuth1 ( which tumblr uses ). All I really needed to do with the tumblr API was to create the post. Once I had my keys worked out and authenticating, it was just one line of code.

Once the post is published, the script updates my sqlite3 db so it makes sure to not post the same thing twice. Thats all!

I’d like to expand the code for this a bit to add some error checking, build in connections to our own API ( instead of using the data dump ) and connect with Twitter. I’m also interested in adding other museum’s data. We have the IMA data available on GitHub, but they don’t include “description” text, so well see… In the meantime, follow it and you’ll receive a new “poem” in your tumblr feed every two hours, for the next 8 years!

Who's on first?

Houston Jet Shoes, 2013

photo by Martin Kalfatovic

We made a new thing. It is a nascent thing. It is an experimental thing. It is a thing we hope other people will help us “kick the tires” around.

It’s called “Who’s on first?” or, more accurately, “solr-whosonfirst“. solr-whosonfirst is an experimental Solr 4 core for mapping person names between institutions using a number of tokenizers and analyzers.

How does it work?

The core contains the minimum viable set of data fields for doing concordances between people from a variety of institutions: collection; collection_id; name and when available year_birth; year_death.

The value of name is then meant to copied (literally, using Solr copyField definitions) to a variety of specialized field definitions. For example the name field is copied to a name_phonetic so that you can query the entire corpus for names that sound alike.

Right now there are only two such fields, both of which are part of the default Solr schema: name_general and name_phonetic.

The idea is to compile a broad collection of specialized fields to offer a variety of ways to compare data sets. The point is not to presume that any one tokenizer / analyzer will be able to meet everyone’s needs but to provide a common playground in which we might try things out and share tricks and lessons learned.

Frankly, just comparing the people in our collections using Solr’s built-in spellchecker might work as well as anything else.

For example:

$> curl  'https://localhost:8983/solr/select?q=name_general:moggridge&wt=json&indent=on&fq=name_general:bill'

{"response":{"numFound":2, "start":0,"docs":[
        "collection_id":"18062553" ,
            "wikipedia:id= 1600591",
        "uri":"x-urn:ch:id=18062553" ,
        "collection":"cooperhewitt" ,
        "name":["Bill Moggridge"],
        "collection_id":"OL3253093A" ,
        "uri":"x-urn:ol:id=OL3253093A" ,
        "collection":"openlibrary" ,
        "name":["Bill Moggridge"],

Now, we’ve established a concordance between our record for Bill Moggridge and Bill’s author page at the Open Library. Yay!

Here’s another example:

$> https://localhost:8983/solr/whosonfirst/select?q=name_general:dreyfuss&wt=json&indent=on

        "name":["Dreyfuss, Henry"],
        "name":["Henry Dreyfuss"],
        "name":["Henry Dreyfuss Associates"],

See the way the two records for Henry Dreyfuss, from the Cooper-Hewitt, have the same concordance in Wikipedia? That’s an interesting wrinkle that we should probably take a look at. In the meantime, we’ve managed to glean some new information from the IMA (Henry Dreyfuss’ year of birth and death) and them from us (concordances with Wikipedia and Freebase and VIAF).

The goal is to start building out the some of the smarts around entity (that’s fancy-talk for people and things) disambiguation that we tend to gloss over.

None of what’s being proposed here is all that sophisticated or clever. It’s a little clever and my hunch tells me it will be a good general-purpose spelunking tool and something for sanity checking data more than it will be an all-knowing magic pony. The important part, for me, is that it’s an effort to stand something up in public and to share it and to invite comments and suggestions and improvements and gentle cluebats.

Concordances (and machine tags)

There are also some even-more experimental and very much optional hooks for allowing you to store known concordances as machine tags and to query them using the same wildcard syntax that Flickr uses, as well as generating hierarchical facets.

I put the machine tags reading list that I prepared for Museums and the Web in 2010, on Github. It’s a good place to start if you’re unfamiliar with the subject.


There are two separate repositories that you can download to get started. They are:

The first is the actual Solr core and config files. The second is a set of sample data files and import scripts that you can use to pre-seed your instance of Solr. Sample data files are available from the following sources:

The data in these files is not standardized. There are source specific tools for importing each dataset in the bin directory. In some cases the data here is a subset of the data that the source itself publishes. For example, the Open Library dataset only contains authors and IDs since there are so many of them (approxiamately 7M).

Additional datasets will be added as time and circumstances (and pull requests) permit.


Thumbnails First & General Visual Bendiness

Our Museum has a new digital-only book series coming out called DesignFile.

I designed the covers, and we want to show here how much thought we put into them, because it’s more than first meets the eye. Designing anything for a design museum is always very meta-meta-meta.

Design we liked: Strelka Press

There is a sort of prerequisite reading for this–Craig Mod’s essay called Hack the Cover. The essay introduces ways to re-think what book covers can and should do in digital format. (What if the cover had a little dashboard area for updates and related information? What if the cover imagery somehow dispersed itself throughout the body of the text? What if we designed separate graphics for pre and post-purchase?) We kept this essay in mind and shared it with everyone involved in the process as an intro to our mindset.

Design we liked: Sternberg Press

The essay also has basic tips on what works visually (large icons, large typography, boldness) when you shrink the cover down and look at it in its true natural habitats: Amazon, publishing websites, iBook shelf, Kindle library, etc.

How it looks on the iBook shelf should not be an afterthought.

DesignFile is cool because the books can be about ANYthing design-related (similar to our exhibitions and programs, which range from cutting edge interaction design to 16th century glassware). I love to find the connections among these diverse examples of design (i.e., the eternal human pursuit of creating and improving stuff) across times, nations, ideologies and peoples.

This is a lofty way to say that the DesignFile visual system had to be flexible: comfortably covering all sorts of content, whether historical, contemporary, popular, obscure, nerdy, or fancy.

They also had to be flexible technically– function on Kindle, iPad, iPhone, as a thumbnail on Amazon, etc.

How does it look in the Kindle library? We were inspired by how this Oliver Sacks series about Neuroscience created a giant image of a human head when ordered alphabetically in the Kindle library.

How to be graphically flexible and technologically all-encompassing without being a total visual snooze? And also somehow communicate that the single and beautiful unifying thread across all the different books is something as broad and polysemic as design?

Iteration was the key for us. Once we agreed on the above requirements, we played with a lot of different ideas.

A design we liked but decided against because it didn’t translate to greyscale.


Super plain! Inspired by Architecture Words, a print book series we saw at the Designers & Books fair and liked.

We also agreed to fight logo creep. The only logo on the cover would be the DesignFile logo. A collaborative publishing project like this had the potential for a cover swamped with fussy, tiny logos.

This design is still my favorite even though we didn’t choose it.


This very simple and elegant version was inspired by a German publisher, Reclam, whose schoolbooks and textbooks I really like.


We almost went with this as final, but when Pam came in as head of Cross-Platform Publishing, she thought it didn’t grab enough attention. At first I didn’t want to re-open the design process (oy!) but in retrospect I’m glad we did, I like the new ones better. And graphic design is pretty much always fun to do.

This one was well-liked. but still not the one.


Another idea that came very close…

You’ll have to peep the books on Amazon to see what the final design looks like.

I would love to hear your comments & thoughts on these ideas and iterations.

thinking / about dongles

So confused...

We launched the alpha version of the new collections website at the end of September. Then I spent a good chunk of the next two months, on the road, talking about it. Or talking around it, sometimes.

There’s the nerdy nerd version with walks through some of the technical architecture and statements of bias for those choices. This was one half of a talk that I did with Micah at the Museum and Computers Network conference (MCN) in November.

It’s nerdy but just as importantly it discusses the reasons why we chose to do things the way we have. Namely that: The speed with which the code running an application can be re-arranged in order to adapt to circumstances. This is not the only way of doing things. Other museums may have legitimate reasons for a slower more deliberate pace but given that we are in the middle of a ground-up renovation and re-imagining of the museum and given the nature of the squishy world of design we don’t.

The other talks bracket the one we did at MCN. There is a long talk and a very very long talk. They are the “think-y” talks. Both were funhouse-mirror keynotes delivered first at Access 2012, a libraries and technologies conference, in Montreal and then a month later at the New Zealand National Digital Forum (NDF) in Wellington.

Both talks are, ultimately, very much about the work we’re doing at the Cooper-Hewitt and the core of each keynote covers the same shifting ground that define our daily grind. Neither talk is a timeline of events or a 12-step songline for re-inventing your museum or the mother of all product demos. Those have their place but I don’t think that a keynote is one of them.

I chose instead to ask the question of why we bother collecting any of the stuff we keep hidden away in our storage facilities in the first place and to work through the claim that the distinction between museums and archives, and by extension libraries, is collapsing in most people’s minds. Assuming it every existed in the first place.

In between (or rather before) all this talking was even more talking. In October I attended To Be Designed (TBD), a three-day design fiction workshop held in Detroit. The goal of TBD was to produce, from scratch, a near-future product catalog and in the process the experience worked its way in to every other talk I did in 2012.

I also spoke with James Bridle and Joanne McNeil as part of Rhizome’s Stories from the New Aesthetic, at the New Museum. My talk doesn’t actually hold hands with any of the other “museum” talks but does sort of wink at them from across a crowded subway car. It was also the first time this slide, which has shown up in every subsequent talk, appeared.

self aware roomba

Because this is what 2012 looks like for museums.

It is most definitely not about Twitter but about the fact that some random person out there on the Internet is building a record of understanding about Roombas that may well rival anything we will ever do ourselves.

Beyond that, we are being forced to accept the fact that our collections are becoming “alive”. Or at least they are assuming the plausible illusion of being alive.

We are having to deal with the fact that someone else might be breathing life in to our collections for us or, frankly, despite us. We are having to deal with the fact that it might not even be a person doing it.

These earlier talks were the soundtrack music. They were soundtrack music in a busy room with lots of people talking. The reason I mention them here is because the place where I think they overlap with the three “museum” talks is at the intersection of motive and how we understand its consequences and how we measure it in a world where the means of production are no longer much of a proxy for anything.

Motive and desire. Desire and means.

The good news is that this is okay. This is better than okay. This presents an opportunity that we’ve never had before and we have proven, by the work that precedes us, that we are not complete morons so I believe we can make something of this.

The bad news is that we are competing with Tumblr. Not Tumblr the company but the ability to, more easily than ever before, collect and catalog and investigate a subject and to share — to publish and to distribute — that knowledge among a community of peers.

Which sounds an awful lot like classical scholarship to my ears. Even if the subject happens to be exercise treadmills. Or tyre swans.

Call me naive but I thought that we had decided that what was important was measuring people on the rigour and merit of their study and not so much on the subject themselves. We’ve been bitten by those blinders so many times already that maybe we could just get past them this time?

Because people are going to do this. They are going to build catalogs and registries and pointers to the things in their life and they are going to put them online so that they have… a center of mass around with the rest of their lives can orbit.

But most important of all is that people are going to do this because they have the means at their disposal. We no longer operate in a world where we have any kind of special access to the means of production and no one is ever going to go back to that world, at least not willingly.

Ask yourselves this: Why didn’t David Walsh give his collection to one of our museums? I am less concerned with the answer than with the question, in this case. MONA is the far end of the spectrum when we talk about what’s possible. David Walsh has, I’m told, more money than the sky but squint your eyes a bit and you see not money but means and desire.

Now look back at the internet.

So, what’s happened between then and now? Aside from just getting back to thinking about and sweating the details as we look towards 2014 the Labs team had a meeting, with a visiting museum nerd, a couple weeks ago.

We were sitting in one of the bigger conference rooms so there was a projector resting in the middle of the table surrounded by a small inanimate support staff of VGA dongles. At one point Seb picked up one of the dongles and asked: How do we (the Cooper-Hewitt) show something like this?

It seems like a throwaway question and in some ways it is. The simultaneous peril and opportunity of a design museum is that our mandate is to consider the entire universe of objects like this. Think of everything you’ve ever known about formal design and aesthetics multiplied by automated manufacturing and distributed openly available databases of designs (and gotchas) and then multiplied again by the steady, plodding march of technology.

And there’s the rub: The VGA dongle is made even more fascinating in that light. All VGA dongles are the same at one end. The end with the VGA adapter. The end with the weight of a black hole that the computer industry despite all their best efforts, and advances, can’t seem to escape.

In fairness we might just barely be starting to see a world beyond VGA in that fewer and fewer devices are using it as their default input standard but I suspect it will still be another five (probably ten) years before it will be unnecessary to ask whether there’s a VGA-to-whatever adapter.

And that’s the other end of the adapter. That whole other world of trying to improve or re-imagine video display. That whole other world of computers and other equally real and conceptual “devices”, at the end of those adapters, that we can use a way to understand the shadows of our history.


That would be an awesome show, wouldn’t it?

And if someone wanted to they could just set up a Tumblr (or whatever) account and grab all the press shots for each dongle from Amazon. There’s probably even a decent opportunity for corporate sponsorship in the form of affiliate/referral links or simply Google Ad Words ads.

A comprehensive cataloging of images of VGA dongles does not an archive, or an expert or a scholar, make but it is a pretty important piece of the puzzle. And what happens when that random person with a Tumblr account writes — and posts — the most comprehensive history of VGA dongles the world has ever seen? Everyone remembers the epic 9, 000 word Quora post on airplane cockpits, right?

I mentioned all this to Joanne one evening and she pointed out that you could probably do the entire show for free if you just ordered all the dongles from Amazon and sent them back before the return policy expired. It’s a genius idea.

You probably wouldn’t be able to remove the dongles from those overwrought and horrible plastic moulds that all electronics are packaged in but that might also be more interesting than not.

Piotr Adamczyk was one of the other keynote speakers at NDF this year and he spoke about the work he’s doing with the Google Art Project (GAP). He pointed out that GAP is really more like a Rachel Whiteread scuplture than anything else; that GAP can show you the shape of the inside of a museum. It’s a lovely way to think about what they’re doing whatever else you think about the project.


To likewise belabour injection-moulded packaging would be a mostly silly way to articulate and conceptualize how we might display a circus show of VGA dongles. But only a little. Given how difficult is it to remove anything from moulded packaging (without also destroying the packaging itself) putting the whole thing on a pedastal un-opened might be the only way we have to consider the formal qualities of the shells that house all the electronic barnacles that cover our lives.

So, yeah. Welcome to 2013.