Libraries Hacked

Promoting open data and digital prototypes in libraries

5 minute read

In 2023 I delivered an online seminar about library data storytelling. Did it go OK? Hopefully, but writing is easier than speaking - here are some notes and thoughts on data storytelling.

What makes good storytelling?

A data story is a narrative constructed from one or many datasets to present a story that is engaging, interesting, and informative.

Library services know all about the power of storytelling. Thinking about characters, what happened, why, when, and how. There are no strict rules other than it needing to be something that people are interested in and get something out of. No story needs to be long or complicated or to require technical expertise. Calling it ‘data’ storytelling should not make it inaccessible, and everyone should be welcome to tell data stories.

What is not good data storytelling?

When discussing data with the library sector, there is an immediate assumption that we’re talking about statistics, performance data, and ‘traditional’ measures and metrics.

Effective performance monitoring is essential, but needs to continually evolve, cause frequent change in practice, and then re-evaluation of the data. Too often it is used to say libraries are doing well or poorly, with little action taken or further analysis of the data. It’s not really the same as data storytelling, but regardless, neither have good adoption in public libraries. That can make library data a dispiriting situation and not one that is engaging or enjoyable for those tasked with it.

Curiosity

Data storytelling is about satisfying curiosity and providing insight into services.

What are people curious about in their services? This will be down to individuals. I tend to be interested in a bit more ‘out there’ data stories. Merging in data such as climate, flooding, high street usage, and how these relate to library usage. Other people will be more interested in specific things they are passionate about. People who don’t use library services, those from deprived communities, etc.

It’s important to allow time for curiosity without having specific goals in mind, or anything to prove. Anything that provides insight into the service can be useful - often we won’t know how until much further down the line.

Getting started

How do you get started, or know what data to even think about? We need to allow time for ideas, and they should be about real life rather than about data. A couple of ways in which ideas can come are either information triggers, or original thoughts.

An information trigger

A library user may mention something, such as they prefer coming to visit the library when town is quiet. Because they can get there with less stress, and it becomes a more relaxed experience. Small bits of information can trigger an “Ah, that’s interesting, I wonder if…” response.

In that example, could we explore if libraries are used more when the surrounding area is quieter? Difficult to assess, but possible. It depends on usage type, and whether the library usage is for leisure or necessity. But these are areas that we should be exploring regularly and understand the data that could support that insight.

An original thought

Not everything has to come from a trigger, sometimes you may just be thinking about aspects of libraries. In the shower, on a walk, whenever. Thinking, and even speculating, is part of any job. It’s hard to give ourselves time to think, but it’s important.

The things that enable these processes to happen are allowing time for thinking, sharing our experiences between library users and staff, allowing ourselves time to explore data, and the key aspect of being curious about our library services.

Get internal data right

To enable good data storytelling, we need to get our data in order.

Sometimes we talk about what data we need to collect to analyse aspects of the service. We need to talk more about what data we already hold. Holding less data but using it more would be a good target.

Take the following steps:

  1. What data do we hold in systems?
  2. Do we need to hold that data; do we use it for operational purposes?
  3. If so, do we make effective use of it?
  4. How can we extract and query it?

Good data/bad data

There is data that is of limited use, and data that is particularly useful.

This tends to come down to level of detail. Using overly aggregated and generalised statistics can be a way of destroying some of our most useful datasets.

  • An example of limited data would be something like a count of loans (including renewals) in a library branch over the course of a year. What does it tell us? Not very much.
  • An example of useful data could be a dataset of all items being loaned in a year, which branch, which method (self-service/issue desk), whether they were a new issue or renewal, and the date and time.

Advocacy for open data (data provided to the public for anyone to use) needs to include insisting that data is useful. Giving the public data that says how many loans there were in each library branch is also of no use to them.

How to get the most from data

Developing rich data stories includes trying to see what we can extract from a single data item.

A date (e.g. 16th January 2024) can tell us a lot, including:

  • month
  • day
  • day of the week
  • season
  • termtime/holiday
  • weekend/non-weekend
  • bank holiday date
  • etc

Method

Putting this all together we can create a guiding method for enabling data storytelling.

  1. Map out what data you hold. This will be in systems like the Library Management System, E-book provider, Peoples Network, Wi-Fi, door scanners, etc. If you do not know what specific data is held in each system, the suppliers should be able to provide schema documents that list the tables and fields.
  2. For each system create rows of sample data (avoid using real data). For example, for loan transactions this would show all the fields you have available to you.
  3. Consider whether you are holding data you have no need for, and never use? If possible, try and limit the collection of that data.
  4. For each column create a list of things that can be derived from that data (e.g deriving the day of week from a date). Across a whole row of data that will provide potentially hundreds of things that could be explored
  5. Merge these together across datasets and create ‘wish lists’ of things that could be explored that would satisfy your curiosity

It’s not necessary to fully complete all those steps in sequence. For example, questions about what data you hold can include policy decisions and discussions with suppliers which will take time. But it’s still worth thinking about them in that order to ensure that data analysis is done with a grounding of good data management.