bodleian

QR Codes of the Bodleian

The Treasures of the Bodleian exhibition opened today, showcasing some of the Bodleian Libraries‘ most awe-inspiring artefacts: fragments of original lyrics by Sappho, charred papyrus from Herculaneum prior to the eruption of Mt. Vesuvius in 79 CE, and Conversation with Smaug, a watercolour by J. R. R. Tolkien to illustrate The Hobbit are three of my favourites. Over the last few weeks, I’ve been helping out with the launch of this exhibition and its website.

Photograph showing a laptop running Ubuntu, in front of a partially-constructed exhibition hall in which museum artefacts are being laid-out in glass cases. — From an elevated position in the exhibition room, I run a few tests of the technical infrastructure whilst other staff set up, below.

In particular, something I’ve been working on are the QR codes. This experiment – very progressive for a sometimes old-fashioned establishment like the Bodleian – involves small two-dimensional barcodes being placed with the exhibits. The barcodes are embedded with web addresses for each exhibit’s page on the exhibition website. Visitors who scan them – using a tablet computer, smartphone, or whatever – are directed to a web page where they can learn more about the item in front of them and can there discuss it with other visitors or can “vote” on it: another exciting new feature in this exhibition is that we’re trying quite hard to engage academics and the public in debate about the nature of “treasures”: what is a treasure?

Close-up photograph showing a small plaque with a QR code alongside interprative text, in an exhibition case. — A QR code in place at the Treasures of the Bodleian exhibition.

In order to improve the perceived “connection” between the QR code and the objects, to try to encourage visitors to scan the codes despite perhaps having little or no instruction, we opted to embed images in the QR codes relating to the objects they related to. By cranking up the error-correction level of a QR code, it’s possible to “damage” them quite significantly and still have them scan perfectly well.

One of my "damaged" QR codes. This one corresponds to The Laxton Map, a 17th Century map of common farming land near Newark on Trent. — One of my “damaged” QR codes. This one corresponds to The Laxton Map, a 17th Century map of common farming land near Newark on Trent.

We hope that the visual association between each artefact and its QR code will help to make it clear that the code is related to the item (and isn’t, for example, some kind of asset tag for the display case or something). We’re going to be monitoring usage of the codes, so hopefully we’ll get some meaningful results that could be valuable for future exhibitions: or for other libraries and museums.

Rolling Your Own

If you’re interested in making your own QR codes with artistic embellishment (and I’m sure a graphic designer could do a far better job than I did!), here’s my approach:

I used Google Infographics (part of Chart Tools) to produce my QR codes. It’s fast, free, simple, and – crucially – allows control over the level of error correction used in the resulting code. Here’s a sample URL to generate the QR code above:

https://chart.googleapis.com/chart?chs=500×500&cht=qr&chld=H|0&chl=HTTP://TREASURES.BODLEIAN.OX.AC.UK/T7

500×500 is the size of the QR code. I was ultimately producing 5cm codes because our experiments showed that this was about the right size for our exhibition cabinets, the distance from which people would be scanning them, etc. For laziness, then, I produced codes 500 pixels square at a resolution of 100 pixels per centimetre.
H specifies that we want to have an error-correction level of 30%, the maximum possible. In theory, at least, this allows us to do the maximum amount of “damage” to our QR code, by manipulating it, and still have it work; you could try lower levels if you wanted, and possibly get less-complex-looking codes.
0 is the width of the border around the QR code. I didn’t want a border (as I was going to manipulate the code in Photoshop anyway), so I use a width of 0.
The URL – HTTP://TREASURES.BODLEIAN.OX.AC.UK/T7 – is presented entirely in capitals. This is because capital letters use fewer bits when encoded as QR codes. “http” and domain names are case-insensitive anyway, and we selected our QR code path names to be in capitals. We also shortened the URL as far as possible: owing to some complicated technical and political limitations, we weren’t able to lean on URL-shortening services like bit.ly, so we had to roll our own. In hindsight, it’d have been nice to have set up the subdomain “t.bodleian.ox.ac.uk”, but this wasn’t possible within the time available. Remember: the shorter the web address, the simpler the code, and simpler codes are easier and faster to read.
Our short URLs redirect to the actual web pages of each exhibit, along with an identifying token that gets picked up by Google Analytics to track how widely the QR codes are being used (and which ones are most-popular amongst visitors).

By now, you'll have a QR code that looks a little like this. — By now, you’ll have a QR code that looks a little like this.

Load that code up in Photoshop, along with the image you’d like to superimpose into it. Many of the images I’ve had to work with are disturbingly “square”, so I’ve simply taken them, given them a white or black border (depending on whether they’re dark or light-coloured). With others, though, I’ve been able to cut around some of the more-attractive parts of the image in order to produce something with a nicer shape to it. In any case, put your image in as a layer on top of your QR code.
Move the image around until you have something that’s aesthetically-appealing. With most of my square images, I’ve just plonked them in the middle and resized them to cover a whole number of “squares” of the QR code. With the unusually-shaped ones, I’ve positioned them such that they fit in with the pattern of the QR code, somewhat, then I’ve inserted another layer in-between the two and used it to “white out” the QR codes squares that intersect with my image, giving a jagged, “cut out” feel.
Test! Scan the QR code from your screen, and again later from paper, to make sure that it’s intact and functional. If it’s not, adjust your overlay so that it covers less of the QR code. Test in a variety of devices. In theory, it should be possible to calculate how much damage you can cause to a QR code before it stops working (and where it’s safe to cause the damage), but in practice it’s faster to use trial-and-error. After a while, you get a knack for it, and you almost feel as though you can see where you need to put the images so that they just-barely don’t break the codes. Good luck!

Another of my "damaged" QR codes. I'm reasonably pleased with this one. — Another of my “damaged” QR codes. I’m reasonably pleased with this one.

Give it a go! Make some QR codes that represent your content (web addresses, text, vCards, or whatever) and embed your own images into them to make them stand out with a style of their own.

Time

My name is Dan, and I am a chronogoldfish.

Is this a chronogoldfish? I don't know. And neither do you. I just made them up.

You see: the thing that goldfish are famous for – except for their allegedly very short memory, which is actually a myth – is that they grow to fill the available space. That is: if you keep a goldfish in a smaller tank, it’ll grow to a full-size that is smaller than if you kept it in a larger tank or even a pond. I’m not certain that’s actually true either, and I’m sure that Kit will correct me pretty soon if it’s not, but it’s part of my analogy and I’m sticking with it.

A chronogoldfish, then, is somebody who grows to fill the available time. That is: the more free time you give them, the more they’ll work at filling it up. This is a mixed blessing, which is a euphemism for “usually pretty bad.” You’ll almost never catch me bored, for example – I’ve no idea how I’d find time to be bored! – but conversely it’s reasonably rare to find me with free time in which I don’t have something scheduled (or, at least: in which I don’t have something I ought to be doing).

Earlier this year, I started working for the Bodleian, and this – along with a couple of other changes going on in my life, suddenly thrust upon me several hours extra in each week than I’d had previously. It was like being transplanted from a tank… into a pond and – once I’d stopped checking for herons – I found myself sitting around, wondering what to do with my sudden surge of extra free time. But then, because I’m a chronogoldfish, I grew.

The activities that I already did became bigger – I took on more responsibilities in my voluntary work, took more opportunities to socialise with people I spend time with, and expanded my efforts to develop a variety of “side project” software projects. I’ve even lined myself up for a return to (part-time) education, later this year (more on that in another blog post, little doubt). And so, only a few months later, I’m a big, fat chronogoldfish, and I’ve once again got just about as little “free” time – unplanned time – as I had before.

But that’s not a bad thing. As Seth Godin says, wasting time (properly) is a good thing. And there’s little doubt that my growth into “new” timesinks is productive (education, voluntary work), experimental (side-projects, education), and joyful (socialising, everything else). I’d like to think I use time well, even if I do sometimes wonder: where did it all go?

I suppose the opposite of a chronogoldfish might be a chronomidget: somebody who doesn’t grow to consume any more time than they have to. The test, I suppose, would be to ask yourself: what would you do if there was an extra half-hour in the day? If your brain immediately rushes to fill that space with an answer (a genuine answer: something you’d actually do – there’s no point lying to yourself and saying you’d spend it at the gym if you wouldn’t!), you’re probably a goldfish. If not, you’re probably a midget.

I think I can name people among my friends who are goldfish, and people who are midgets. But I do wonder what type they would say that they are…

Work Calendar [NSFW?]

In my office at the Bodleian, we’ve got a calendar on which employees mark their annual leave. The theme of the calendar is supposed to be paintings inspired by flowers… but – and maybe it’s just my dirty mind – this month’s image seems just a little bit saucy:

Our calendar this month. That's supposed to be a flower, is it? — Our calendar this month. That’s supposed to be a flower, is it?

Click to embiggen. It can’t be just me that sees… it… right?

Instead Of Blogging…

Things I’ve been doing instead of blogging, this last month, include:

Code Week: hacking Three Rings code in a converted hay loft of a Derbyshire farm, as mentioned on the Three Rings blog.
Hoghton Tower: as is traditional at this time of year (see blog posts from 2010, 2009, 2005, 2003, for example), went to Preston for the Hoghton Tower concert and fireworks display, accompanied by Ruth, and my sister’s 22nd birthday. My other sister has more to say about it.
Family Picnic: Joining Ruth and JTA at Ruth’s annual family picnic, among her billions of second-cousins and third-aunts.
New Earthwarming: Having a mini housewarming on New Earth, where I live with Ruth, JTA, and Paul. A surprising number of people came from surprisingly far away, and it was fascinating to see some really interesting networking being done by a mixture of local people (from our various different “circles” down here) and distant guests.
Bodleian Staff Summer Party: Yet another reason to love my new employer! The drinks and the hog roast (well, roast vegetable sandwiches and falafel wraps for me, but still delicious) would have won me over by themselves. The band was just a bonus. The ice cream van that turned up and started dispensing free 99s: that was all just icing on the already-fabulous cake.
TeachMeet: Giving a 2-minute nanopresentation at the first Oxford Libraries TeachMeet, entitled Your Password Sucks. A copy of my presentation (now with annotations to make up for the fact that you can’t hear me talking over it) has been uploaded to the website.
New Earth Games Night: Like Geek Night, but with folks local to us, here, some of whom might have been put off by being called “Geeks”, in that strange way that people sometimes do. Also, hanging out with the Oxford On Board folks, who do similar things on Monday nights in the pub nearest my office.
Meeting Oxford Nightline: Oxford University’s Nightline is just about the only Nightline in the British Isles to not be using Three Rings, and they’re right on my doorstep, so I’ve been meeting up with some of their folks in order to try to work out why. Maybe, some day, I’ll actually understand the answer to that question.
Alton Towers & Camping: Ruth and I decided to celebrate the 4th anniversary of us getting together with a trip to Alton Towers, where their new ride, Thirteen, is really quite good (but don’t read up on it: it’s best enjoyed spoiler-free!), and a camping trip in the Lake District, with an exhausting but fulfilling trek to the summit of Glaramara.

That’s quite a lot of stuff, even aside from the usual work/volunteering/etc. stuff that goes on in my life, so it’s little wonder that I’ve neglected to blog about it all. Of course, there’s a guilt-inspired downside to this approach, and that’s that one feels compelled to not blog about anything else until finishing writing about the first neglected thing, and so the problem snowballs.

So this quick summary, above? That’s sort-of a declaration of blogger-bankruptcy on these topics, so I can finally stop thinking “Hmm, can’t blog about X until I’ve written about Code Week!”

First Class Film

Last week, I saw X-Men: First Class at the cinema with Ruth. The film was… pretty mediocre, I’m afraid… but another part of the cinemagoing experience was quite remarkable:

There’s a bit in the film where Xavier, then writing his thesis at Oxford University, and a CIA agent are talking. As they talk, they walk right through the middle of the Bodleian Library, right past my office. It’s not just Morse and Lewis and the Harry Potter films that make use of the Library (at great expense, I gather) for filming purposes! “That’s my office!” I squee’d, pointing excitedly at the screen.

Needless to say, the student-heavy audience cheered loudly at the presence of parts of Oxford that they recognised, too. It’s been a while since I was in a cinema where people actually cheered at what was going on. In fact, the last time will have been in the Commodore Cinema in Aberystwyth. But cinema-culture in Aberystwyth’s strange anyway.

Fonts of the Ancients

“Thanks to these changes,” I said, “The Bodleian Libraries websites CMS can now support the use of Unicode characters. That means that the editors can now write web content in Arabic, Japanese, Russian… or even Ancient Egyptian!”

Man standing on two giraffes. — The well-known "man standing on two giraffes" hieroglyph.

It sounded like a good soundbite for the internal newsletter, although of course I meant that last suggestion as a joke. While I’m aware of libraries within the Bodleian who’d benefit from being able to provide some of their content in non-Latin characters – and Arabic, Japanese, and Russian were obvious candidate languages – I didn’t actually anticipate that mentioning Ancient Egyptian would attract much attention. Everybody knows that’s meant as a joke, right?

A slug and a streetlight. — Streetlights of the 2nd century BC were powered by enormous slugs.

“Is that just Demotic symbols, then? Or can we use all hieroglyphics?” came back the reply. My heart stopped. Somebody actually wanted to use a four thousand plus year old alphabet to write their web pages?

It turns out that there’s only one font in existence that supports the parts of the Unicode font set corresponding to Egyptian hieroglyphics: Aegyptus. So you need to ensure that your readers have that installed or they’ll just see lots of boxes. And you’ll need to be able to type the characters in the first place – if you don’t have an Ancient Egyptian Keyboard (and who does, these days), you’re going to spend a lot of time clicking on characters from a table or memorising five-digit hex-codes.

Crazy golf course. — Papyrus was important, but the Egyptians' greatest achievement was the invention of crazy golf.

But yes, it’s doable. With a properly set-up web server, database, CMS, and templates, and sufficient motivation, it’s possible to type in Ancient Egyptian. And now, thanks to me, the Bodleian has all of those things.

Well: except perhaps the motivation. The chap who asked about Ancient Egyptian was, in fact, having a laugh. In the strange academic environment of Oxford University, it’s hard to be certain, sometimes.

Crocodile in a sleeping bag. — Crocodiles can easily be caught using sleeping bags.

I do find myself wondering what scribes of the Old Kingdom would have made of this whole exercise. To a scribe, for example, it will have been clear that to express his meaning he needed to draw a flock of three herons facing left. Millenia later, we treat “three herons facing left” as a distinct separate glyph from “one heron facing left”, perhaps in a similar way to the way that we treat the Æ ligature as being separate from the letters A and E from which it is derived. He couldn’t draw just one heron, because… well, that just wouldn’t make any sense, would it? So this symbol – no: more importantly, it’s meaning – is encoded as U+13163, the 78,180th character in an attempted “univeral alphabet”.

Vulture and asp, in bowls. — Starting step in the creation of "vulture and asp soup".

To what purpose? So that we can continue to pass messages around in Ancient Egyptian in a form that will continue to be human and machine-readable for as long as is possible. But why? That’s what I imagine our scribe would say. We’re talking about a dead language here: one whose continued study is only justified by an attempt to understand ancient texts that we keep digging up. And he’d be right.

All existing texts written in Ancient Egyptian aren’t encoded in Unicode. They’re penned on rotting papyrus and carved into decaying sandstone walls. Sure, we could transcribe them, but we’d get exactly the same amount of data by transliterating them or using an encoding format for that specific purpose (which I’m sure must exist), and even more data by photographing them. There’s no need to create more documents in this ancient language: just to preserve the existing ones for at least as long as it takes to translate and interpret them. So why the effort to make an encoding system – and an associated font! – to display them?

Skipping with a two-headed snake. — Two-headed snakes: the original skipping rope.

Don’t get me wrong: I approve. I think Unicode is awesome, and I think that UTF-16 and UTF-8 are fantastic (if slightly hacky) ways to make use of the breadth of Unicode without doubling or quadrupling the amount of memory consumed by current 8-bit documents. I just don’t know how to justify it. All of those bits, just to store information in a language in which we’re producing no new information.

What I’m saying is: I think it’s wonderful that we can now put Egyptian hieroglyphics on the Bodleian Libraries websites. I just don’t know how I’d explain why it’s cool to a time-traveling Egyptian scribe. Y’know; in case I come across one.

My New Pet Hate, part II

A few years ago, I talked about a pet hate of mine that still seems to be prevalent: that is – that when people send me a screenshot, they’ll sometimes send me it in a Word document, for no apparent reason. They could just send me the picture, but instead they send me a Word document containing the picture, thereby increasing the file size, requiring that I have a program capable of viewing Word documents, and making it more-complex for me to extract the picture if I need to use it somewhere. And on top of all of that, it takes longer for them to do it this way: everybody loses!

Today, I saw somebody take the abuse of screenshots to a whole new level. My first clue that something was amiss was when the email arrived in my Inbox with a 300K TIFF file in it. “Well, at least it’s not a Word document,” I thought. And I was right. It was something more convoluted than that.

My only explanation for the contents of the file is as follows:

Print Screen. The user took the screenshot using their Print Screen key. So far, so good. They captured their whole screen, rather than just what they were trying to show me, but we’ll let that pass.
Open Paint. The user opened Paint. At this point, they could have pasted, saved, and emailed the file to me, and still been doing perfectly well. But they didn’t.
Resize canvas. The user expanded the canvas to an enormous size. Perhaps they didn’t know that this would be done automatically, if required. Or maybe they thought that I could do with a lot of white space in which to make notes on their screengrab.
Paste and reposition. The user pasted the screenshot into the Paint document, and positioned it near the centre, making sure to leave as much whitespace as possible. Y’know, in case I was running out of it on my computer. They could still at this point have just saved the file and emailed it to me, and I wouldn’t have complained.
Print Screen again. For some reason, the user pressed Print Screen again at this point, thereby taking a screenshot of themselves manipulating a screenshot that they’d already taken. Maybe the user has recently watched Inception, and decided that “a screenshot within a screenshot” was more likely to make an impact on me. We need to go deeper!
Open Photoshop. Paint obviously wasn’t going to cut it: it was time for a bigger graphics program. The user opened up Photoshop (waiting for a few minutes while this beast of a program warmed up).
Create a new document and paste again. Now the user had Photoshop open, containing a picture of Paint being used to display an (oversized) screenshot of what they wanted to show me.
Crop. This was a good idea. If the user had cropped the image all the way back down to the screenshot, I might not even have worked out what they were doing. Sadly, they didn’t. They cropped off Paint’s title bar and half of its toolbar. Then they added another few layers of whitespace to the bottom and right, just to be really sure.
Save as a TIFF. They could have saved as a PNG. Or a GIF. Even a JPEG. They could have saved as a PSD. But no, for some reason, an uncompressed TIFF was the way forwards.

Back in 2009, I predicted that Windows Vista/7’s new “Snipping Tool”, which finally brought screen captures to the level of more-competent operating systems, would see the end of this kind of nonsense. Unfortunately, Windows XP remains the standard at my workplace, so I doubt that this’ll be the last time that I see “matryoshka screenshots”.

Idiocy Repeats Itself

Two years and one month ago to this day, I made an idiot out of myself by injuring myself while chasing cake. Back then, of course, I was working on the top floor of the Technium in Aberystwyth, and I was racing down the stairs of the fire escape in an attempt to get to left-over cake supplies before they were picked clean by the other scavengers in the office building. I tripped and fell, and sprained by ankle quite badly (I ended up on crutches for a few days).

Last week, history almost repeated itself, and I’m not even talking about my recent head injury. Again, I’m on the top floor of a building, and again, there’s a meeting room on the bottom floor (technically in the basement, but that only means there’s further to go). When I got the email, I rushed out of the door and down the stairwell, skipping over the stairs in threes and fours. Most of the Bodleian’s stairwells are uncarpeted wood, and the worn-down soles of my shoes skidded across them.

You’d think I’d have learned by now, but apparently I’m a little slow. Slow, except at running down stairs. As I rounded the corner of the last stairwell, my body turned to follow the route but my feet kept going in the same direction. They took flight, and for a moment I was suspended in the air, like a cartoon character before they realise their predicament and gravity takes hold. With a thud, I hit the ground.

Perhaps I’d learned something, though, because at least this time around I rolled. Back on my feet, I was still able to get to the meeting room and scoff the best of the fruit and sandwiches before anybody else arrived.

Is this really worthy of a blog post? Dan doesn’t have an accident is hardly remarkable (although perhaps a little more noteworthy than I’d like to admit, based on recent experience). Well, I thought so. And I’ve got a free lunch. And I didn’t have to hurt myself to do so. Which is probably for the best: based on the number of forms I had to fill out to get root access on the systems I administer, I don’t want to think how complicated the accident book must be…

Content Freeze

Isn’t memory strange?

Last week, we updated to the latest version of the CMS that powers the Bodleian‘s web site. During the process of installing and testing the new version, we initiated a “content freeze”, disallowing the 100+ regular content editors access to the administration sections: any changes they’d have made wouldn’t have been replicated in the new version, and we didn’t want a discrepancy in content while we were testing that the change had taken! We still had back-end access, of course, and a few minor “emergency” changes were made (on both the old and the new version), but in general, the site was in a read-only mode for several days.

A similar thing happened to my head during this weekend’s house move.

While running a van-load of stuff from Old Earth to New Earth, Ruth, JTA and I stopped off at Argos to buy a few bits and pieces for our new home. We parked in one of the few remaining parking spaces capable of accommodating our extended wheel-base van. Unfortunately this brushed us up very close to an unfortunately-placed tree, whose branches reached in through the door as I clambered out. I spent a while trying to reposition them so as not to slam them in the door while Ruth and JTA walked ahead, towards Argos, and so when I was done they were quite a way ahead. I turned and ran to catch up with them…

BAM! Something struck me on the top of my head. We’re still not all in agreement as to whether it was a branch or the wing mirror of the van, but it hurt like hell. My knees buckled up and I collapsed into a heap.

Before long I was on my feet, but as I began to feel dizzy and nauseous, we started to worry that I might be concussed, and Ruth took me to the hospital. By then, I was unable to keep my eyes open without feeling like the world was spinning and I was going to throw up, and I kept feeling like I was moments away from falling asleep.

By the time I’d seen a doctor, about three hours later, I was starting to feel a little better. We took a leaflet of “things to watch out for after a concussion”, which advised that I shouldn’t lift any heavy things (“But I’m moving house today!”) nor use a computer or drink alcohol (“This is my life you’re talking about!”), all of which I ignored to some degree or another.

I napped on and off for a lot of Sunday and some of Monday, but it was on Monday that the amount of damage I’d done became most apparent. I got out of bed and staggered downstairs to find that Ruth and JTA had at some point bought a shoe rack. They weren’t around, but neither was the van, and I reasoned that they must have been out collecting more boxes, but I thought I might as well make myself useful by assembling this shoe rack they’d gotten. It was of the variety that hangs on the back of a door, so I spent some time deciphering the instructions and putting it together… only to find that it wouldn’t actually fit onto any of the (quite thick) doors in our new house.

That’s when Ruth & JTA arrived. “I saw you’d bought a shoe rack,” I said.

“Yes,” they replied, “We bought it yesterday. We told you about it.”

“Oh. I don’t remember that. Anyway, I built it, but it turns out that it won’t fit any of our doors.”

“Yes, we know: we told you that too. We were about to take it back to the shop.”

I have no recollection whatsoever of that conversation. Or several other conversations, it seems. In the hospital, I remember that Ruth talked to me for an hour or more (I wasn’t capable of conversation myself, some of the time, but it was nice to hear a familiar voice), and I still can’t remember any of it except for snippets (something about her father’s new house?).

For much of Sunday, my brain went into “content freeze”, too. A read-only mode where my memories worked fine, except that I couldn’t construct any new ones: everything just went in one ear and out the other. Maybe this is to be expected: a quick look at some maps of brains and an examination of the bump on my head indicates that the blow came to a point squarely in the centre of the middle frontal gyrus (the dorsolateral prefrontal cortex) of the right hemisphere of my brain: an area associated with emotional self-control, social judgement, lateral thinking, and the transfer of working memory.

Still: it was certainly a strange experience to be told about events from only a day earlier that I simply can’t remember. It also made Tuesday interesting: long weekends are confusing at the best of times, but parts of my memory made it feel like I’d had only a two-day weekend (as parts of Sunday are simply missing from my memory), and so it was even harder than usual to shake the feeling that it was Monday when I arrived at work on Tuesday. That’ll be a pleasant surprise on Friday, anyway, when the weekend “comes early”: maybe I should bang my head every time there’s a long weekend.

Leading By Example

This week, I was reading the new EU legislation [PDF] which relates to, among other things, the way that websites are allowed to use HTTP cookies (and similar technologies) to track their users. The Information Commissioner’s Office has released a statement to ask website owners to review their processes in advance of the legislation coming into effect later this month, but for those of you who like the big-print edition with pictures, here’s the short of it:

From 26th May, a website must not give you a cookie unless it’s either (a) an essential (and implied) part of the functionality of the site, or (b) you have opted-in to it. This is a stark change from the previous “so long as you allow opt-outs, it’s okay” thinking of earlier legislation, and large organisations (you know, like the one I now work for) in particular are having to sit up and pay attention: after all, they’re the ones that people are going to try to sue.

The legislation is surprisingly woolly on some quite important questions. Like… who has liability for ensuring that a user has opted-in to third-party cookies (e.g. Google Analytics)? Is this up to the web site owner or to the third party? What about when a site represents companies both in and outside the EU? And so on.

Seeking guidance, I decided to browse the website of the Information Commissioner’s Office. And guess what I found…

…not what I was looking for: just more circular and woolly thinking. But I did find that the ICO themselves does not comply with the guidance that they themselves give. Upon arriving at their site – and having never been asked for my consent – I quickly found myself issued with five different cookies (with lifespans of up to two years!). I checked their privacy policy, and found a mention of the Google Analytics cookie they use, but no indication about the others (presumably they’re not only “opt-out”, but also “secret”). What gives, guys?

Honestly: I’m tempted to assume that only this guy has the right approach. I’m all in favour of better cookie law, but can’t we wait until after the technological side (in web browsers) is implemented before we have to fix all of our websites? Personally, I thought that P3P policies (remember when those were all the rage?) had a lot of potential, properly-implemented, because they genuinely put the power into the hands of the users. The specification wasn’t perfect, but if it had have been, we wouldn’t be in the mess we are now. Perhaps it’s time to dig it up, fix it, and then somehow explain it to the politicians.

Another Crazy Connection

Remember about three weeks ago when I re-met a Bodleian Libraries employee whom I’d first met many years ago? And then went on to meet their friend, who turned out to have been somebody with whom I’d been trying to schedule a meeting anyway!

Well today I had that meeting (and was formally introduced to my friend-of-a-friend). And when I got back, I found the following (edited, here) email in my Inbox:

Hi Dan,

You may remember me from such RT requests as #1234567. I have an inkling that we may also have met (if you attended) at the National Nightline^W^WNightline Association AGM in Leeds a couple of years back. I used to be a Nightline volunteer at Oxford.

<snip>

Alex

This chap works for the Computing Services department of the University, and as a result he’s been helping to deal with my (many, many) tickets and request-for-change forms as I’ve tried to get access to all of the systems to which I’ve needed access. And recognised me, apparently.

It’s a crazy, crazy small world.

Manifold Greatness

Earlier this week, I went along one lunchtime to a free exhibition hosted by my new employer, entitled Manifold Greatness, dedicated to the history of the translation of the bible into English.

Of particular interest are the (never-before publicly exhibited) translation documents used by the actual translators who wrote the 1611 King James Bible, probably the most influential and significant English-language biblical translation projects ever undertaken. The exhibition includes the only known copy of a Bishops’ Bible (the earlier authorized text of the Church of England) with handwritten notes by the translation committees who were at that time writing what was to become the King James Bible. It’s quite fascinating to see the corrections they chose to make after consulting with earlier Greek texts.

They’re also showing off an original copy of the Wicked Bible in remarkably good condition (most were destroyed): this book, probably owing to industrial sabotage at the printers’ works at which it was produced, misses out the word “not” in the seventh commandment, “Thou shalt not commit adultery.” If you’re going to commit industrial sabotage, it’s nice to do so with a sense of humour.

If you want to go and see the exhibition – and I’d recommend it; and I’m not just saying that because I work here – you’ve got until 4th September.

A Small World Conspiracy

I keep getting caught up on small world coincidences, since I started working at the Bodleian Library last week. I know about selective biases, of course, and I’ve always said that coincidences happen nine times out of ten, but this is really starting to feel like some kind of amazing conspiracy that I’ve somehow wandered into.

The most recent chain of connected coincidences is also probably the most impressive. But to explain it, I’ll need to take you back in time by almost three years. Back in the summer of 2008, I went to BiCon for the second time, accompanied by Claire and Matt P. Among the various other things we got up to, we met a young lady called Ann (who, if I remember rightly, got along very well with Matt).

This morning I received an email from Ann. It turns out that she works in the Bodleian Libraries: she’s likely to be one of the very users who it’s now my job to provide training and technical support to! She saw my photograph in the newsletter I mentioned in my last blog post and looked me up: small world! I emailed back, suggesting that we get together for a drink after work, and she agreed: great! She also asked if she could bring a friend along, a colleague from the library. Sure, I said, sounds good.

This lunchtime I sorted out some of my holiday entitlement for the rest of this academic year. I booked off a few days for a Three Rings “code week” in the summer, and a couple of days around the time that I’ll be moving house next month. One of these days clashed with a meeting that I’d had planned with the Web/Digital Officer of one of the libraries (I’m doing a grand tour of many of the libraries that comprise the Bodleian, in order to meet all the relevant people), so I sent an email to this staff member to ask if we could reschedule our meeting to another time.

“Okay,” they said, “But I think I’m meeting you in the pub in 90 minutes anyway…”

It turns out that the person whose meeting I’ve asked to reschedule is the friend of the person who recognised me from the staff newsletter, having originally met me three years ago. Out of all of the people (I’m not sure how many exactly – it’s probably in the staff handbook I haven’t read yet – but I’ll bet it’s a lot) that are employed by this, the largest university library in the UK, what are the odds?

With The Bod

I know that there are about a million things I ought to be writing about; I’ll try to get time at the weekend. In the meantime, I thought I’d share with you this snippet from Outline, the internal newsletter of the Bodleian Libraries:

What does this tiny appearance on page three mean? Well; it means that the many libraries that I’ll be visiting over the next few weeks (I have a surprising number of meetings set up!) will know I’m coming, for one.

The article mentions geocaching, because the editor asked me for “something personal about me”, and it was the most family-friendly thing I could think of on the spot. I was also asked “what I did”, which I struggled with a little because, despite having been here a week, I’m still not entirely sure what it is that I do. That said, I achieved the first productive parts of my work, yesterday, helping a user with a self-inflicted (probably!) bug in the Libraries’ CMS system. Apart from that, I feel like I’ve spent most of my time running around the city meeting people and networking! Lots of new faces and names to learn!

Two things keep coming up in conversation with people, upon discovering that I’m new here:

Several people have asked “What university I worked for before?” The majority of people here were either Oxford undergrads or worked at other universities: to have somebody come in from the private sector is a little… unusual, it seems.
People keep telling me that I shouldn’t expect (or be expected) to achieve anything for the first six months or so. Six months! It’s taking a while to get started, certainly (I’m still finding my way around all of the systems I’m now responsible for), and I still don’t have logins on half of the computers and services that I’ll need them on, yet, but that’s just ludicrous!

The main Bodleian Libraries website; one of about 32 websites for which I now find myself responsible.

On the other hand, I’m seriously enjoying the comparatively-relaxed attitude that everybody seems to have, here. And I’ve been given a bugs-list as long as my arm that I’m sure they’ve been saving up for me to arrive, so there’s plenty to sink my teeth into even if I will have to go through half a dozen committees before I can implement any of the new features that these websites so desperately need.

On This Day in 2002 (New Job!)

This will be the first time I’ve ever written an On This Day post where I haven’t been able to link back to a blog post that I actually wrote in the year in question. That’s because, in 2002, I was “between blogs”: the only thing I wrote about online that I still have a copy of was the imminent re-launch of AvAngel.com, my vanity site at the time. In that post, however, I did mention that I’d re-written my CV, which was relevant to what was going on in my life in March 2002…

Looking Back

On this day in 2002, I first began working for SmartData, my primary employer for the last nine years. A few months earlier, Reb – my girlfriend whom I’d moved in with in 2001 – and I had broken up, and I’d recently found the opportunity to visit Aberystwyth and visit friends there (the trip during which I first met Claire, although we didn’t get together until a little later). On that same trip to Aber, I also met Simon, who at that point had recently accepted a voluntary redundancy from the Rural Studies department of the University and was getting started with the launch of his software company, SmartData. He’d recently landed a contract with the National Dairy Farm Assured Scheme and needed an extra pair of hands on board to help out with it.

Sorting out premises was coming along somewhat slower than he’d planned, though. As part of the SpinOut Wales scheme, SmartData had been offered cheap accommodation in a University-owned building, but they were dragging their feet with the paperwork. On our first day working together, Simon and I crammed into his tiny home office, shoulder-to-shoulder, to hack code together. The arrangement didn’t last long before we got sick of it, and we “moved in” to the room (that would eventually be legitimately ours) at Peithyll, a former farmhouse in the village of Capel Dewi, near Aberystwyth.

The entrance to Peithyll, Capel Dewi, near Aberystwyth. — The entrance to Peithyll, where SmartData established itself for much of the first six years of its life. It was quite a cycle to get out there every day, but in the summer it made for a great office: not many people can sit at their desk and watch red kites hunting outside, or go for a lunchtime walk up a hill with a picnic.

Over the last nine years since, as the company has grown, I’ve always felt like a core part of it, shaping it’s direction. As we transitioned from developing primarily desktop applications to primarily web-based applications, and as we switched from mostly proprietary technologies to mostly open-source technologies, I was pointing the way. By working with a wide variety of different clients, I’ve learned a great deal about a number of different sectors that I’d never dreamed I’d come into contact with: farm assurance schemes, legal processes, genetic testing, human resource allocation, cinema and theatre, and more. It’s been a wonderfully broad and interesting experience.

Looking Forward

When I began making plans to move to Oxford, I initially anticipated that I’d need to find work over here. But Simon stressed that my presence was important to SmartData, and offered to allow me to work remotely, from home, which is most of what I’ve been doing for the last year or so. Thanks to the miracles of modern technology, this has worked reasonably well: VoIP phones keep us in touch, tunneling and virtual networks allow us to work as if we were all in the same location, and webcams help us feel like we’re not quite so far from one another.

But this wasn’t to be a permanent solution: just a way to allow me to keep contributing to SmartData for as long as possible. Last week, I was offered and accepted a new job with a new employer, here in Oxford. Starting in April, I’ll be managing the administration and the ongoing development of the website of the Bodleian Libraries, the deposit library associated with Oxford University.

Clarendon building, Bodleian Library — My new office, right in the heart of Oxford. It looks a lot less green, and a lot more prestigious, than Peithyll.

It’s a huge change, going from working as part of a tiny team in a West Wales town to working with hundreds of people at one of the largest employers in Oxford. I’ve no doubt that it’ll take some getting used to: for a start, I’m going to have to get into the habit of getting dressed before I go to work – something I could get away with while working from home and that might even have been tolerated in the office at SmartData, as long as I threw on a towel or something (in fact, I have on more than one occasion taken a shower in the SmartData offices, then sat at my desk, wrapped in towels, until I’d dried off a little).

This feels like a huge turning point in my life: a whole new chapter – or, perhaps the completion of the “turning a page” that moving to Oxford began. My new job is a brand new position, which provides an exciting opportunity to carve a Dan-shaped hole, and I’ll be working with some moderately-exciting technologies on some very exciting projects. I’m sure I’ll have more to say once I’m settled in, but for now I’ll just say “Squeee!” and be done with it.

Oh: and for those of you who follow such things, you’ll note that Matt P has just announced his new job, too. Although he’s a sloppy blogger: he’s actually been working there for a little while already.

This blog post is part of the On This Day series, in which Dan periodically looks back on years gone by.