I was watching the British Library Labs symposium and was interested to see a quick update on the public libraries Single Digital Presence (SDP) work. Check out the video of the whole library labs symposium on YouTube. It’s all ace, but the SDP update is 2 hours into the streaming event.
The Bookseller also published a recent update from the team, transforming the digital offer for public libraries, and research partners DXW have published a case study on creating a national digital presence for public libraries
The updates all show that the project includes a wider focus on digital transformation, rather than just a single software platform.
Having thought a little about digital transformation, I think there are a number of things worth considering for library digital services.
Fix before building
I try to advocate for the Local Digital Declaration.
We will ‘fix our plumbing’ to break our dependence on inflexible and expensive technology that doesn’t join up effectively
Local Digital Declaration
It includes fixing the issues that cause problems and hamper projects. These could be related to data and software, but also culture and skills.
The recent Bookseller piece included a fairly reserved comment on the current state of library digital presences.
many familiar with the sector will recognise that the quality and consistency of libraries’ digital offerings could be improved
Jacob Fredrickson, Single Digital Presence project manager
But what in particular is broken? Yes, the websites and services have poor usability, accessibility, and aren’t pleasant to use. But those are symptoms, not underlying problems.
In November I was approached by a web developer. Enthusiastic about libraries in their local area they wanted to create a new and accessible way of browsing the library catalogue (no, it wasn’t me!). They had asked their library service, via freedom of information, for data on all the titles in the catalogue, in spreadsheet format.
This isn’t an odd request, and it should be a situation that we jump at the chance of fulfilling. People creating software for interacting with their library? Great, get them that data!
Unfortunately the library service replied that with over 1 million records it wouldn’t be possible to provide the data within the £600 freedom of information limit. On appeal, they then insisted they were exempt from the request as the data was publicly searchable from the online catalogue.
It would be easy to be critical of the service. To say they were either overly protective of the data, or even intentionally obstructive. But I think they can be taken at face value. They likely don’t have the required knowledge to do it, and would have to go to the supplier, costing well over £600. But the member of the public is sent away disappointed with poor service from the library.
That’s (partly) what is broken. The library catalogue is the primary data held by a library management system, it shouldn’t be a problem to extract data on it. The problem is the skills and training for staff to be able to do it.
If there isn’t the investment in library system administration, what likelihood is there to be expertise in digital service skills like content design and user experience?
There are hugely encouraging words from the British Library showing they fully appreciate this, and are looking at enabling library services. But there will only be so much they can be responsible for.
we think that there is scope to develop patterns and designs that local libraries can use and re-work to improve their own websites and digital presences
Jacob Fredrickson, Single Digital Presence project manager
Everyone needs to be involved
Digital projects aren’t delivered to organisations with immediate success. Whether it’s an Intranet, a new Document Management System, or whatever. After implementation they need to be understood, adopted, and used effectively.
The tech industry can be guilty of solutionism by selling software as a fix for a problem, when it is only a tool to be used by people. But on the other side, libraries will buy software without considering the time and investment they need to put in. The funding rarely goes far enough to appreciate that whatever it costs to create and deliver, you will need a lot more after that.
It’s all very well to demand ‘where’s the single digital presence?’ But it is as relevant to ask library services how they are preparing for it. For all the work being done by the British Library to research and advise, more will be needed from each library service to make it a success.
We need multiple digital presences
This isn’t just being a smart arse about the term single digital presence. SDP clearly expresses someone being able to go to one place to see information about multiple services, catalogues, resources, etc.
However, in the ideal situation we would have multiple digital presences. Or perhaps more accurately: multiple single digital presences. Want an app to quickly reserve library books? Sure, search the app store, check the reviews, and choose one. What if the Reading Agency want to put a search for UK libraries on their website? Great, they should go for it. Delivery of those websites and apps can be out of the hands of library services.
True digital transformation will mean giving up control. The library website won’t necessarily be the place people go to find out about their libraries. The library catalogue site won’t be where users reserve and renew their loans. They may choose the alternative site that allows them to tick the auto-renew option; that website will then handle renewing items for them.
Work in the open
There is very little in the public library world that requires secrecy. The personal data of staff and the public being the primary exceptions.
Public organisations are quite locked down, often because they handle sensitive data. But it can mean all information and data becomes locked down and fiercely guarded. That reduces understanding of data protection rather than enhancing it.
It’s very hard to change this culture, but there are great examples of working in the open. Check out HackIT, the website of the technology, digital and data teams of Hackney Council. There are details of the projects they are working on, how they work, and service design principles. Most impressively, various personal weeknotes, which are the regular postings of what individuals have been doing.
And why not? It will improve their own work, and inform the public who may be interested. It will also give them a greater understanding of where the open/private divide is in the data and information they handle.
Don’t reinvent the wheel
Working last year with library staff and the DCMS on the library open data schemas I was nervous that it must have all been done before. You know that comic about standards and constantly creating new ones? That was on my mind. As it was, for data schemas like public library membership, and footfall, no, it hadn’t been done. And hopefully that work will be used in projects like the single digital presence.
That principle of adopting standards, plus building upon past work is an important one. I recently rediscovered a blog post by Nick Poole about his learnings from being involved in 5 attempts to create a Single Digital Presence, called building a successful online presence for libraries. This is essential reading for making a success of such a project (more so than this meandering one).
But one thing it didn’t delve into was how, if at all, those projects were linked. There is benefit in a ‘failed’ project if it moves the current situation further along. Have they done some groundwork of interoperability between systems, some standards for sharing data, or documented the work so it can be picked up the next time?
Other than thinking I know what a couple were, I don’t have details of those 5 projects. But if they had included working in the open then more information would be available about them. As it is, it doesn’t look like they were.