New Work: A physical interactive table for The Postal Museum

We’re happy to announce our latest project, for the newly-opened Postal Museum in Clerkenwell! The new museum opened late July, and included a new Discovery Room, a brilliant public space where you can access archival objects directly, upon request. We were tasked with making the first instalment of an interactive table to help people browse around the collections, and hopefully be prompted to ask an archivist a question, or delve a little deeper.

Discovery Room

Part of the new building is this new public space you can visit, and ask to see original materials (as well as browse the digital collection and use our swanky new touch table). You need to allow a bit of time for things to be retrieved from the stores, but, why not give it a try? It’s upstairs on the first floor, and free!

Two Collections to Start

The Postal Museum has a huge trove of all sorts of visual materials, from the obvious philately collections, to letters, to maps, to posters, to photography. For this first stage, they wanted us to show the core collection of the museum, the R. M. Phillips Collection (which tracks the history of the UK postage stamp in unparalleled and thorough detail), and a selection of Post Office: Photograph Library, mostly around post and war, but with some vehicles and interiors too. We’ve tried to keep in mind that it would be nice to incorporate more collections over time too, once the new building has settled in a bit.

We used a metadata export from the museum’s CALM database, served up images using IIIF, served with Cantaloupe, through a Ruby app.

I’ve done a bad job of getting nice images of the actual UI, so will endeavour to update this post with some once I have my act together!

Seeing Things Big

We knew we wanted to take full advantage of the affordances of a lovely big screen and simple touch gestures. Rather than crowding the interface with lots of niggly controls, we wanted the brilliant imagery to take centre stage. Even as we were getting to know the R. M. Phillips Collection, we just kept zooming in all the time to see the lovely details, so wanted to help others do that too.

This is where we ended up, the view when you’re looking at a single thing, really zoomed in:

Collaborators

This was our first collaboration with Buckley Williams, and we sincerely hope it wasn’t the last! Thank you, Nat & Dan.

A favourite part of the collaboration (apart from the consistently snappy outfits and extreme talent) was our placeholder image, which we used on the table so we could proceed with the UI as we loaded all the whopper images… it’s one of those ones that you know won’t slip through.

DateRanger

As you may be aware, we try to always look for small utilities we think other people might be able to use, like the marcxml-to-postgres slurper, or the dimension-drawer, and we’ve found another one, called DateRanger. Nat has posted separately about this, so if you’re interested in why the heck dates are so hard in cultural collections, maybe head over there for a look.

Advertisements

DateRanger – a new tool to share

This is a post by Nat Buckley, of Buckley Williams, our recent collaborators on the new Postal Museum Touch Table project.

As humans we find it easy to quickly read a variety of date formats and almost instantly understand what they represent. We can glance at dates written as “23rd Jan 1894”, “Jan-Mar 1856”, “c. 1960” or “1945-1949” and we know how big the date range is and how accurate it might be. These are just a few examples of dates formats we found in the Postal Museum collections.

To work with those dates effectively in our software we needed to find a way to parse them and represent them in a single format. There are many software libraries designed for translating between standardised date formats (eg. ones used by different countries), but parsing formats commonly used in archives is a slightly less popular problem to solve. Archives tend not to have an enforced, fixed way of writing down dates, so there can be a surprising variety of notations. This isn’t a bad thing — it gives the archivists the flexibility they need to represent their knowledge about the objects under their care. Each collection might have its own quirks.

Some smaller software libraries do take on a challenge of parsing dates from more natural, human-readable formats, but we decided to devise our own way. We had a very specific set of formats and couldn’t find an existing solution that could deal with all of them easily.

I wrote DateRanger, a Ruby library which takes in those formats and translates them into a data structure which represents the start and end of the date range. It makes it straightforward to understand the accuracy of the date — the wider the range, the less accurate or specific the date was to begin with. We’d love to see contributions from anyone interested in expanding how many formats DateRanger can work with.

I used automated tests to build up the code in stages, starting from parsing really simple dates, and culminating at testing even obscure format combinations that we didn’t quite encounter in our data sample. The tests-first approach meant I managed to notice and catch some pretty confusing bugs really early on.

We used DateRanger on the Postal Museum touch table, to help us determine where on the timeline to place the collection records. We did, however, use the original date formats from the archive to display to the viewer. After all, those are already perfectly human-readable.

New Work: MoMA Exhibition Spelunker

Installation photograph from The Museum Collection of Painting and Sculpture exhibition, held 20 June 1945 to 13 February 1946

On September 7, 2016, The Museum of Modern Art (MoMA) in New York cracked open a new repository on the code repository service, Github. In addition to the release of their popular collection dataset, the museum also made the unprecedented decision to share the exhibition history of the museum (from 1929 to 1989), which also included a ton of archival material like press releases, installation photographs, and catalogues. You can see the official version on moma.org.

MoMA asked Good, Form & Spectacle to make a spelunker to showcase this data, and we were thrilled to oblige.

Voila!   http://spelunker.moma.org

First Steps

As with all our previous spelunkers, the first step we usually take is to map out a basic plan for the information and how you’ll move around in it. This is often a basic List -> Item pattern, where List can be made up from any of the main data elements. In the case of MoMA, that was Exhibitions, Roles, People/Orgs, and Departments. From each list view, you can move to a single instance of that type of thing, and from that single instance, back out into others, like from an exhibition to the year it happened, or to an artist in that exhibition. (We also get a Python project running on Heroku, and pop our own first commits on Github.)

The main reason we enjoyed making the MoMA Exhibition Spelunker so much was because the data was of a different nature to a collection dataset. As well as listing each exhibition over that period, the data also shows all the people who were involved, both the artists, but also, interestingly, museum staff and other collaborators. We’ve looked a little at how metadata can represent institutional dynamics with Week 1 of the What’s in the Library? project with Wellcome Library, but this was altogether more fine-grained. Who are the actors in this institution? Can  you see their influence?

First Impressions

So, once we have the basic List -> Item scaffold in place, it’s really a matter of trying to answer the questions that come up for us as we poke around all the corners of the data. One of the first simple visuals we added as the basic timeline, to show quickly and clearly what happened, and when.

Straight away, even a simple graphic like this asks questions. What’s that peak in World War II? Why the dip in the 50s? Why was 1978 such a full year?

It’s important to say at this point that a lot of what I’ll write next about what I discovered in the MoMA Spelunker is pure conjecture and presumption, based on looking at this data quite a lot. It may not be true, at all. (See Open Data, Assumptions and Naïvety below.) 

The Museum & People Dynamics

We don’t often get to see or know the dynamics and politics that go on within the walls of a museum. It can be such a designed space, all about the art or objects, that often the people who made an exhibition come true are almost entirely invisible. It was a real pleasure to work on this data from MoMA specifically because it isn’t about the art, but about the people. When we first began the project, I was keen to be able to show the art, but that desire was quickly supplanted by interest in, and display of, who was doing what.

One of the visualisations we made was about directors of departments, how long they were directors, and in some cases, showing where people went as they moved around the museum, in some cases in careers spanning 40 years. You can see in this screenshot what we can highlight a single individual as they move around too, so you can see who skipped where and when, like John Elderfield…

It was bordering on titillating to imagine who might have worked together and how such long term tenures really did shape the museum as it is today. But, it’s also crystal clear that a little map like this can reveal nothing about why people moved around. You’ll need to look in the Archives to learn those stories.

MoMA Characters Emerge

I was enjoying the way that showing this kind of data over time helps you spot blobs and trends and gaps in the data. I was interested to try to uncover whether we could show who the key staff were that really got MoMA off the ground in the early years. By taking a role – Curator – and drawing it over time, you can see quickly see who was kicking things off, in this case, the founding director, Alfred H. Barr, Jr., curated 36 exhibitions, and worked there for about 40 years.

Something interesting happens when you change how that list is sorted. We can show the same data, but order by who curated the most exhibitions, to get a really different picture that shows the curators who’ve worked on the most exhibitions, and how much they made in any given year. It’s there that you start to notice the effort of curators like William S. Lieberman, who led three different departments over his career, or Dorothy C. Miller, who worked at the museum for about 30 years, and was head of the Department of Painting and Sculpture for a relatively short time, too. Did they work together? Did they like each other?

We liked this “most appearances” view much more, so set that as the default.

This list view is cool too, when you’re looking at artists. There’s a lot of info squished into that single list view, and the overall impression is mostly that MoMA has an incredible collection full of heavyweights (and very good relationships with collectors and other museums), and shares it with the world a lot! Here are the most exhibited artists in the 1929-1989 data… could you infer Jasper Johns blasted on to the scene at some point there?

One small design thing I introduced was to show a small ♀ symbol in big lists of people, so you could spot women quickly. This revealed a little gap in the data, where gender isn’t always noted. Since perfect is the enemy of good, rather than remove the feature, I’m trying to help by slowly making additions/corrections to a copy of the data, which MoMA is welcome to. (Want to help?)

World War II and The Responsive Museum

Something that piqued my curiosity almost immediately was about how the museum operated in World War II, 1939-1945. They were exhibiting a lot, and browsing 1942 and 1943 in particular, there were clearly lots of exhibitions related to the war.

I first noticed the annual exhibitions called Useful Objects of American Design under $10.00 that opened in 1939, and repeated for a few years thereafter. I found myself wondering if this was austerity-related, but then realised I didn’t know the equivalent of $10 in today’s money! Nevertheless…

Useful Objects of American Design under $10.00

Then I noticed several others that were much more specific to war, starting to emerge in 1940 and many more in 1942/1943, and beyond, like War Comes to the People: A Story Written With The Lens, National Defense Poster Competition, Art in War: OEM Purchases from a National Competition, Wartime Housing, Road to Victory, Camouflage for Civilian Defense, United Hemisphere Poster Competition, The Museum and the War, National War Poster Competition, Art Education in Wartime, War Caricatures by Hoffmeister and Peel, Airways to Peace, Magazine Cover Competition: Women in Necessary Civilian Employment, and more.

Airways to Peace (and a cool interactive dymaxion globe!)

With a little further digging beyond our dataset, I quickly discovered that “numerous exhibitions at The Museum of Modern Art were produced in collaboration with the United States government,” as it continued to exhibit the very best in modern art, including Starry Night, which MoMA acquired in 1941, and exhibited soon after.

I simply don’t know how data like ours could possibly show that Victor D’Amico chaired the Committee on Art in American Education and Society, which established as “art education’s answer to Fascism and its contempt for creative art. We hope to mobilise the art educators and students of America, combining all their art efforts, large and small, throughout the nation to work for victory.” It’s just one or two steps away from his basic data, and you always have to stop making new columns in data at some point, don’t you?

The committee worked throughout the year to keep art on the educational agenda. There’s a lot more background about the museum and the war available in this archival finding aid online: The Museum and the War Effort: Artistic Freedom and Reporting for “The Cause”. (It’s worth a read.)

I have to say it makes me wonder how and if museums in the USA (and elsewhere) are mobilising to produce a “vast program of art activity” in this way to combat the 45th president. Ahem. In any case, I actually removed a bunch of other “this was interesting” and “I enjoyed this” links and stuff. You can find your own way!

What did the critics say?

NATURE and social satire are the themes of two current shows here. Both are important and well worth seeing.

Jacob Deschin, on Elliott Erwitt: Improbable Photographs

Remember mashups? When publicly accessible code-level interfaces (or APIs) became a thing back in the day, the fantasy was that all manner of mashups could be made to combine and recombine data from all over into compelling new presentations.

One of our early ideas for this spelunker was to try to bring in content from the fabulous New York Times archive, a treasure trove of history around New York City and its surrounds from 1851 to the present. We knew that The New York Times regularly reviews events and exhibitions at MoMA, so it was simple step to try to combine that with the MoMA exhibition data. Luckily, too, the MoMA team had already done a lot of the work to connect exhibitions to articles, which was hugely helpful.

Could we show what The New York Times critics said about MoMA through the twentieth century? Yes! Critics such as Edward Alden Jewell, who was watching from the start in 1929, or Jacob Deschin, who often wrote about photography exhibitions from the late 1940s to the late 1960s, also form part of the fabric of the exhibition history at MoMA.

(Note that you can’t see full articles unless you’re a subscriber. We can show first paragraphs, which is a start.)

Open Data, Assumptions & Naïvety

This work for MoMA has been interestingly different from previous spelunkers we’ve made. In other projects, we’ve made exploratory interfaces into object-level metadata, which is (arguably) simply factual, representing objects and their attributes. While there may be errors or omissions in this kind of metadata, each object is as well-described as possible. Sometimes, viewing this data in the aggregate can bring insights — like seeing instantly that prints form the largest group of things by type at the Victoria & Albert Museum — but there’s really not much ‘colour’ to it.

Part of the provocation of the spelunker concept is to challenge the notion that people know what they’re looking for when they encounter a new museum’s collection, and I’m wondering if that could be extended to museum datasets. It seems to me that “drawing” this data makes it easier  to hypothesise about and ask questions of than examining a big .CSV file. You follow your instincts or an image that appeals or a person you recognise or a theme you’re into, and, I think, start to form your own opinions pretty quickly. The challenge is that this metadata can be quite rich, but, at least in our experience so far, also pretty superficial, so the picture that’s drawn for you is just a surface view. Perhaps though, it’s like a physical exhibition where you don’t read any labels (or there aren’t any), and you’re left to make your own judgements, some of which may be wrong, but all are personal.

As we were fleshing out the interface to the MoMA spelunker, I found myself making all sorts of assumptions about the institutional dynamics at the museum related to who was working when, and why they might have moved around, their areas of interest or speciality, and things like that. I’d written about some of that sort of stuff on the About page, but the kind folk at MoMA archives were good enough to let me know that some of those assumptions were just plain wrong! Maybe it was more that the data we were able to display only gives you a tiny glimpse into the actual dynamics, and it’s simply a must to explore more deeply with experts or other source material. I don’t want to draw wrong conclusions, and experts in house, who live with this information day to day, surely don’t want to express things that are wrong. Of course not. I think what I’m coming around to is that these sorts of explorers help orient viewers towards questions they’d like to answer, once they’re acclimatised to the terrain. That seems good!

More broadly speaking, we’ve now made six spelunkers at G,F&S, and it’s probably about time I had a proper think about how well they’ve worked and whether they’re useful. More on that later…

The team for this project was George Oates (design, project lead), and Phil Gyford (engineering). Thanks, Phil!

New shelves!

We’re very pleased to have some lovely new shelves made and installed by Scott Stannard join us in our Bloomsbury studio. They’re fantastic, and now we can get all the crap off the floor and every other surface!

Here’s the pre-installation shot:

And the evening post-installation, with weird Charlie head, and Phil working hard on our new Explorer project (more on that later).

 

It’s like it’s a real office or something.

Museum Visits – a live web thingy

This is a blog post by Phil Gyford, who helped me make a thing. I’ve been curious about a tool called sheetsee.js for ages, and we made a site to show you the museums we visit, and it’s driven directly from a Google spreadsheet! I find myself wondering if small museums might be able to use this simple tech.

---

PHIL SAID:
George has been keeping track of the museums she’s been visiting in a Google spreadsheet and wanted to make it a little more visible, useful and attractive.

Sheetsee.js looked like it might be just the thing to help. It makes it relatively easy to use data from a Google Spreadsheet to make pages containing tables, maps and charts. One of the Sheetsee.js examples, Hack Spots, was along the lines of what we wanted, which was reassuring.

Within a day we’d got a quick single-page site up on Heroku, letting us list all the museums, clicking one to display a museum and its details, including a map. Pretty good! We spent a second day refining it, making nice URLs for each visit, and filtering the table to show only the museums built, founded or opened in a particular year.

The site has barely any back-end; there’s a single PHP file and a `.htaccess` file to make URLs like /visit/23 load that one file.

Sheetsee.js uses Tabletop.js to fetch the Google Spreadsheet’s data. We run through that data and tidy up each row a little: we make some fields more readable; and add fields to show (for example) whether or not that museum has any external URLs, which helps with displaying its details. Sheetsee.js then handles displayig the table, paging the data, making it sortable, and making the filter form work.

The JavaScript listens for clicks on the museum names and then displays its details. When the data includes latitude and longitude we use Leaflet to display a Mapbox map.

Making the page work more nicely — changing the URLs for each museum and keeping the browser back/forward buttons working — involved more custom coding, which got me in a bit of a tangle, given I’m not used to making single-page, solely-JavaScript-powered sites. It seems to work, thanks in part to History.js.

Displaying the museums that were only built, founded and opened in particular years also involved going round in circles a few times, and involved more URL-fixing shenanigans and manually filtering the data before handing it over to Sheetsee.js.

All-in-all Sheetsee.js was lovely to use and it would be a great tool for creating nice views of modest amounts of data held in a Google Spreadsheet, without the complication of a database. Going beyond what it can do by default can be trickier. For example, we wanted to have the table’s filter only filter based on the contents of a particular column, but that’s not easily possible. But, otherwise, two thumbs up!

Visiting Researcher Disappears for 8 Months

Hi there. My name is Eliza Gregory, and I came to visit George in London last December, to observe what she was doing with The Small Museum and Museum in a Box, in particular, but also to bask in her fabulousness more generally.

I’m a social practice artist, and so I think a lot about how interactions, conversations and relationships relate to art (and can even become art themselves). I tend to make art out of conversations, experiences, and relationships, and I sometimes layer social elements with other media like text, installation, photographs, or audio. My favorite projects that I’ve done have taken months or years to build, and unfold over time, with the goal of cultivating relationships across class and across culture in a given community. Sometimes I also do much simpler one-off events, like The Box Project, which I wrote about for George a while back.

Increasingly I’ve been working with museums in mutually beneficial collaborations. The museums commission me to create events and artworks that connect with specific audiences. Sometimes that results in some kind of physical object being made (a book, a photograph) and sometimes it’s a very process-focused activity that results in a new group of people feeling connected to the museum, or a new set of connections between people (those relationships across class, or across culture that I mentioned). And I’m experimenting with how museums can become engines of social change, by looking carefully at (and potentially changing) whose stories are represented, how they are told, and who gets to listen.

For example, this is a book I produced in conjunction with the Asian Art Museum, as part of a project about contemporary immigration in San Francisco.

I’ve been thinking through the potential for Museum in a Box and the Small Museum to increase interactivity in museums as a way to drive social change. A few different projects that are touchstones for me have challenged museums to acknowledge their interactivity in fundamental ways–challenged them to evaluate: who really is welcomed by the institution as a visitor or a staff person? What narrative is really being put forward about power, justice, race, gender, and equality? What does a visitor get out of each visit to the museum, and is that enough? When only a small subset of the population in a place visits the museum, can the society justify the amount of resources it takes to maintain the institution and the collection? How many resources devoted toward preserving stuff is too many? And who is getting to choose what is preserved?

The Box Project 2016 @ the Asian Art Museum in San Francisco. Photograph by Quincy Stamper.

These are all questions about values. Unsurprisingly, social values all over the world have gone through major changes in the last 60 years. But museums, which are inherently conservative–they actively conserve the past–have been slow to adapt to the new social contexts in which they find themselves. So the most interesting projects I’ve seen artists and creative administrators take on have challenged museums to evolve; to become agents of social justice, to become more truly public, to become relevant to the present and the future as well as the past.

I’m thinking of Thomas Hirschhorn’s 2004 Musee Precaire, where he convinced the Pompidou Center to loan a great many works out to a space in Aubervilliers. Quoting Alfred Pacquement, director of the Pompidou at the time, as published on the Tate’s website,

After doing several short internships – such as working on the installation of the Biennale de Lyon – a group of twelve young people had a two-month full immersion in the different departments of the Centre Pompidou, including security, art handling, framing, installing and public information and education. Since they were well prepared before the opening, there was a strong sense that this Musée Précaire belonged to them. The hands-on involvement of the residents of Aubervilliers was always at the heart of the plan, so we approached the training programme as we would any other professional internship. We made no special exceptions because of the size or the ‘precariousness’ of their future museum.

The result was a quite extraordinary atmosphere. On the one hand there was this incredibly relaxed environment. Under usual circumstances, people tend to act differently in a museum – such as lowering their voices as they walk around the space. Yet in Aubervilliers, the residents did not change their everyday behaviour. There was music playing. There were kids hanging out in the Musée Précaire’s café, playing and running around in front of the exhibition space. In stark contrast though, there was an air of utter dedication when it came to the young people employed by the museum. It was obvious that they took their jobs extremely seriously. One could sense that they felt the responsibility and trust confided in them by the Pompidou in lending them these artworks.

Hans Haacke’s Shapolsky Et Al. (described here by the Whitney) from 1971 exposed connections between slumlords in Manhattan and the Board of Trustees of the Solomon R. Guggenheim Museum, where the work was to be part of a solo show (which was canceled). Now owned by the Whitney and formally acknowledged as “institutional critique,” it has become part of the canon, although the subject of the work should be no less threatening today, and is no less radical. While not exactly interactive, this work exposes the interactions the museum is built on, calling out the conceit that museums are simply places of display that have somehow shed the messiness of social context.

And a third example: In 2013 Erica Thomas worked with the Portland Art Museum to put a small LED light next to each work in each gallery that was made by a woman.

Unsurprisingly, this turned out to be very few works–just one or two paintings in each European gallery, for example, was lit up.

But the Native American galleries glowed.

It was moving and astonishing to make something we know but don’t think about so intensely visible. (Images courtesy Erica Thomas.)

All three of these works make the structure of “museums” overt. Hirschhorn calls attention to the staff, the visitors, the culture of comportment, and the notion of security and permanence. Haacke looks at the power structures (and potentially dirty money) that fund museums. And Thomas shows us the cultural bias and prejudice reflected through curatorial decision making.

By making the institutional structures overt, these artists also expose the limits of each institution in a new way. Haacke’s piece could not be exhibited in the moment that it was made because the Guggenheim could not have continued to exist without the support of its trustees and their funding. It’s not that the institution was wrong to cancel the exhibition–what’s interesting is that the cancelation itself demonstrated the limits (and the architecture) of the institution. He found the way the whole place could be broken. Hirschhorn demonstrates that such an inversion of the power (and racial) dynamics of the Pompidou are possible, but not sustainable–they are inherently temporary and precarious; a gesture, an amusement, but not a permanent shift in power. What’s so effective is now we know they are possible, which means that we as a society make a choice not to sustain them. He shows us that the process by which societies tell stories about themselves depends upon consent and engagement from whoever has the power in that society. He has made the social conventions and the money surrounding the institution visible, just like Haacke, but through an entirely different avenue. Finally, on a smaller scale but no less poignant because of it, Thomas shows us that vague perceptions of contemporary institutions as equitable are not real. The museum may wish to be seen as a place that supports women and female artists generally, but the collection tells a different story.

The idea of a small museum gets around some of these issues by simply not being able to participate in them (lower security, less funding, a wider variety of neighborhood micro-contexts both physically and socially). To me, the more aware (and intentional) a small institution is about how and when they are reenacting the structure of a big museum, the more interesting they will be. They have lots of opportunities for explicitly inverting traditional rules or practices, often out of necessity, and I think that can be a real strength.

Museum in a Box, meanwhile, is playing with how to strip away MOST of the structures of the museum, while still being part of museums. How many elements of the museum can you remove and still have a museum? When it’s in a box, we simply have: objects (or pictures of them), information about them, relationships between them, and an audience. Most simply that’s objects, ideas, relationships and audience. Again, if you’re starting with the most basic incarnation of a museum, when you begin to add the layers back on, you can play with them. You can be MUCH more deliberate. And you can communicate new ideas–and enact new social relationships–through what you include, and what you leave behind. As a platform, rather than an institution or a program or an object, Museum in a Box offers museums the ability to use their collections (and their past) to participate in a democratized, contemporary conversation that allows for debate, for multiple histories, for nontraditional (and potentially disempowered) narratives. You might not be able to create an institution that doesn’t depend upon the powerful for its existence, but you can have a conversation that eschews power. So this platform represents an experiment where powerful institutions could condone and support radical conversations. That seems like a space for real social learning, and maybe even for compassion. That’s very exciting to me.

 

Building the Wellcome Library Alpha – people

In part one of this two-part series about how we went about building an Alpha website for Wellcome Library, we looked at how we turned ‘subject headings’ into webpages.

This post looks at the second major type of aggregation pages we settled on: people.

At first we were tempted to refer to these as ‘authors’, using the language of books, but of course the library isn’t just books, and so sometimes the people might be editors, collaborators, artists (the library has an art collection too), scientists credited on academic papers, and so on.

Within the MARC metadata we were given, people are referenced mostly in the 100 field (‘Main Entry–Personal Name’), but also in the 700 field (‘Added Entry-Personal Name’). As far as we could make out, there’s only ever one person in the 100 field (with only a couple of exceptions), but there could be many in the 700. It wasn’t clear to us what the semantic difference was, so we took the decision to merge them all together.

Each person field contains a bunch of sub-fields for the person’s name, title (Mr, Mrs, Sir, etc) and dates (normally just birth and/or death), as well as some other lesser-used sub-fields like ‘numeration’ (e.g. the ‘II’ in Pope John Paul II) and ‘attribution qualifier’ (used for describing someone as the ‘pupil of’ an artist, when the actual artist is unknown).

One awkward stumbling block was that the name of the person followed the library tradition of being in ‘surname-comma-firstnames’ format. This convention makes it easy for computer systems to sort by surname, which historically has probably been the most useful order for readers. But we felt strongly that it is the least user-friendly way of actually reading people’s names, as it inverts the natural order of the way we pronounce people’s full names (no-one talks about ‘Hawking Steven’, but ‘Steven Hawking’ is a household name). Switching the order back sounds like a simple task (split the string at the last comma, then reverse the order), and mostly is, but there are always exceptions – and where we encounter strings like “Peter, of Celle, Bishop of Chartres,ca”, it’s a bit harder to turn these back into more readable names.

With our goal being to make the library catalogue browsable (rather than just searchable), our next task was to find ways to enrich the information about the people in the database, helping readers to find out more about them (which may in turn shed some light on what the content of the book is likely to be).

Like with subjects, many of the 100 and 700 people fields contain an ID linking the person to an external authority file. Unlike with subjects though, we only encountered  a single authority file in use: the Library of Congress Name Authority.

Where they existed, we could use these IDs to make sure that multiple books by the same person would appear on the same single person page, even if their name was spelt out or punctuated differently on the different records.

It would have been tempting to use these Library of Congress IDs within the URL structure of the Alpha site. But because they weren’t always present (either because that person isn’t in the LOC authority file, or just because the record has been matched up), we couldn’t do that, and so minted our own IDs instead. For simplicity’s sake, these are simple numbers, but preceded by the letter ‘P’ (for person).

We discovered an existing project called VIAF, which aims to link together name authority files from many different institutions across the globe. By querying this database with the Library of Congress IDs, we collected up all the other IDs that were available. This means we can construct links from the people pages on the Wellcome Library website to the equivalent pages on other catalogues, such as the national libraries of France, Germany, Spain, Canada, and many more.

Pleasingly, VIAF has also collected IDs referencing Wikipedia pages. As Wikipedia allows others to uses its content under a Creative Commons licence, we could query the site (using its API) and display the content on our person pages. We decided to display the first two sentences (with a link to Wikipedia to read the full biography), on the basis that that’s usually enough information to get a sense of what the person is mostly known for. We also removed any text from Wikipedia in parentheses, as these are normally dates (which we show elsewhere), a pronunciation guide to their name, or other minor details that weren’t needed for a quick read.

As well as text, we also collected the images from the Wikipedia page, and use the first one (if there are any) within a circle to illustrate the person on both their person page and aggregation pages. This mostly works – where it’s a photo or drawing of the person, or even if it’s a scan of one of their works – but does sometimes show a slightly misleading image.

There was a small amount of concern over using Wikipedia as a source of content (although most were positive). One issue is what might happen if we pull the content from Wikipedia at a point in time when that page has been vandalised. We could mitigate that to some extent by regularly updating our content on a rolling schedule (and relying on the community to resolve) – but to allow for any major issues to be resolved more quickly than that, we added an admin feature to immediately refresh the content from Wikipedia. So if someone at Wellcome spots a page where the Wikipedia introduction is inaccurate or contains vandalised content, they can fix it on Wikipedia itself, and then have those changes reflected on the Wellcome Library page.

As well as the Wikipedia intro, we added a feature allowing Wellcome staff to add a separate intro to be displayed alongside it. Our rule of thumb here was that this intro should be specific to the Wellcome institution, rather than repeating the sort of general information that might be on a Wikipedia biography. So things like that person’s relationship to Wellcome (e.g. if it’s Henry Wellcome himself) or noting what sort of material from that person was available at the Wellcome Library (which could be quite a lot, if it’s one of the people whose personal archives are held there).

After these context-setting introductions and photo, we display some data about that person collected from the catalogue itself: things like the subjects their works are mostly about, a timeline of when their works were created/published and what format their works are mostly in. More experimentally, we tried displaying some links to other people who are the “contemporaries” of that person. This query changed a few times as we tried to refine it, and ended up being something along the lines of “people who have produced works about the some of same subjects and who were born within 10 years”. It sometimes works well, sometimes doesn’t.

Finally, we added the ability to highlight ‘interesting’ people to appear on the homepage.

Our last and most recent step was to go back and use an additional type of metadata that we originally missed: field 600 which contains people, but who are the subject of a work rather than its creator. Pleasingly for these ‘person-as-subject’ pages we could re-use the simple URL structure for subject pages (/subjects/S1234) but replacing the S-number for the person’s P-number. (One key benefit of differentiating your IDs for different types of things).