How do we solve the developer gap? The ever-present question for libraries and archives.

PASIG 2016 was held at MoMA in NYC on 26-28 October 2016. And like many digital preservation conferences, Twitter was ablaze with ideas and discussions—both those in attendance and those watching from twitter feeds at their desks.

During Karen Cariani’s (Director WGBH Media Library and Archives) presentation, ‘The Complexity of Preserving Digital Media Files,’ there was a tweet highlighting a point from Cariani regarding the lack of developers in the library and archives sector:

This was something I have been pondering on for some time; it led me to retweet with this question:

And then I went back to the conference only to realise I had unleashed quite a strong debate among developers, IT staff, librarians and archivists working in a diverse range of institutions. Turns out, this is a question many people are asking as well. And the answer is probably not straightforward, or at least not answerable in 140 characters.

However, I was inundated with plenty of good ideas. Here are a few of the highlights:

And this only a selection of the conversations from the Twitterverse. It shows that there are many ideas for potential solutions to the ‘developer gap’ in libraries and archives. However, there’s no one-size-fits all solution for every institution. These ideas sound great, but do they work in practice?

Pay developers market rates. Or at least on par with IT staff.
This would ideally make our developer roles competitive, but as budgets continue shrink in our sector this proposal can be hard for some institutions to get the support from senior management to pay market rates. Paying on par with other IT staff seems a given and I would be interested to see where this is not put into practice and why not.

Find burnt out IT staff and lure them over.
If we can sell a work-life balance and other benefits in our organisations, perhaps that would make up for different rates. Remuneration is not all about the salary, but about the overall benefits. And if your institution can offer them, should this be highlighted in job advertisements up front better? After all, it’s not always all about the money…we also have interesting puzzles to solve!

Improving higher education curriculums for library and archives programmes.
Should understanding the digital environment (such as Web 2.0 and the Internet) still be taught in 2016 or can we all agree that students should have these prerequisite skills? Can we include basic computing science and basic programming skills? These skills are reaching into broader fields than just computer science, so why have library and archives courses not bothered to catch up? Even if it doesn’t give a librarian/archivist all the skills to be a developer, it will help to bridge the communication gap between IT and librarians/archivists.

Preserve less?
Likely a very contentious solution, for a number of reasons. Having strong and clear collections development policies will outline the scope of collection, but sometimes institutions cannot simply say ‘no’. However, whenever we acquire a collection, considerations must be made. It’s not just about the cost of storage that matters in digital preservation, but the cost of care and management over time.

There is likely no one easy solution. It is likely a combination of many things and shifts that will take place over years—probably at a glacial pace. These questions and potential solutions should be considered, because our development needs aren’t going anywhere. I think it’s safe to say that digital is here to stay…


Have an idea how to fill the developer gap? Share below:

One thought on “How do we solve the developer gap? The ever-present question for libraries and archives.

  1. From: Andy

    This is not just a problem in digital preservation, nor libraries in general either, but the whole GLAM sector. I left working in archaeology and moved into the libraries because the pay was significantly more, so can understand why developers leave libraries. Archaeology really is on the cliff face of this problem as they are expected to use the most modern technologies in their work, but have very little strong IT behind them, often relying on the haphazard skills of existing staff, or those savvy enough to up-skill themselves (not necessarily to a level up to date/scratch!).

    I’ve known several developers, some of whom were extremely dedicated to the digital humanities, leave libraries because they can earn more, and easier, money – I think there’s also a problem with librarians understanding the methods and language of developers and they therefore find it a frustrating, very often unrewarding area to work in. There is also a lack of staff/mechanism in between to “translate” what the librarian wants to the developer and vice-versa.

    That said, there is also an older generation of librarians who do have a better understanding of computer science methods than the younger generation because they had to be aware of them in order to even use a computer decades ago.

    There must be a balancing act somewhere along the line. Getting computer science and librarian students to interact more at the learning stage would perhaps draw out more interest and skill in both, and perhaps increase the ability to talk to each other without a “translator”. More library internships for computer scientists with solid senior developers to ensure they receive a positive rewarding experience is also worth considering, but essentially it will probably all come back down to money.

    The wider institutions will need to recognise that libraries need more funding for developers (solid, not just project by project) in order to create services and infrastructure that can and will stand the test of time and continue to be permanently developed in sync with technological changes is probably the only way to ensure any level of digital preservation. Staff retention in the long term should be the goal, think how much more work would be done if we could all stop explaining all of our specific issues to a new developer every 6 months!