As I’m currently in the final phase of my PhD, I have to dedicate more time to writing and less to doing. Even so I can’t let MoMA’s datasets go by unnoticed.
The above screenshot is from a timeline tool I developed for visually analysing large cultural collections. I imported the MoMA dataset and visualised the object records along their production dates. We can see the timeframe the collection spans, with earliest pieces from the late 1700s and – obviously – a focus on twentieth century and contemporary items.
The block shape around 1820 and the rectangular spike at 1900 represent large numbers of items that have the same, or very similar, production dates. Such anomalies can stand for series of items in the collection, they can be traces of curatorial decisions in cataloguing, they could be mistakes in dating, etc.
I inspected a few records in the 1900 spike and encountered a few photographs, which gave me the idea that the spike could represent a larger series of photographs – this would explain the high production output in a short timeframe. The tool allows me to colour records according to a field value, so I gave it a try and coloured all photographs in green:
In 2009, Walter Alvarez was looking for a way to communicate the enormous time frames that make up the history of the universe and conceived the idea of ChronoZoom, which was released as an early prototype in 2010. Since then, the visualisation evolved quite a bit and by now contains a rich collection of data. What I only found out recently, is that all of this data is also accessible separate from the visualisation through a dedicated API.
Recently, the makers of ChronoZoom launched a contest in collaboration with the platform Visualizing.org in order to, I’d guess, promote the use of this API and at the same time tackle some of the problems they encountered.
v0.1, v0.2, v0.3, v0.4, v0.5, v0.6, v0.7, v0.8, v0.9, v0.10, v0.11, v0.12, v0.13, v0.14, v0.15, v0.16, v0.17, v0.18, v0.19, v0.20, v0.21, v0.22, v0.23, v0.24, v0.25, v0.26, v0.27, v0.28, v0.29, v0.30, v0.31, v0.32, v1.0b, Final
Visualizing.org has partnered up with the people behind ChronoZoom. ChronoZoom is both a dataset containing curated timelines of the history of the cosmos and the world, as well as visual interface for exploring those timelines. Much in the same tradition as some of the earliest timelines, which aimed to map all of time – from the Creation to the last Judgement – ChronoZoom contains events since the Big Bang up to our current times. If you somehow haven’t come across it yet, you should give it a try here.
Why not Linked Data, asks a fellow Tweeter and Tate’s web architect Rich Barrett-Small justifies their move to GitHub with it being the most time- and cost-effective solution to get the data out there – for now.
Yes, SPARQL endpoints are the weapon of choice these days, but what’s wrong with using GitHub? It’s an incredibly versatile platform by far not limited to programmers, but equally useful for thesis writing or democracy.
What’s great about using GitHub, as opposed to APIs, is that it doesn’t only give you access to the data, it gives you the data. Maybe I’m old school, but I do like having real files on my hard drive, as opposed to it all being locked off in a cloud. And it’s still possible to keep the data updated, by syncing it with the original repository.
But enough about pros and cons of technical details, let’s have a look at what Tate offers.