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:
Not a lot of developers in the library archives space – a challenge for staffing projects #pasignyc
— Sheila Morrissey (@sheilaMorr) October 27, 2016
This was something I have been pondering on for some time; it led me to retweet with this question:
— Sarah Mason (@DigitallySarah) October 27, 2016
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:
Or to pay developers who want to work in libraries competitively? If not on par w/corporate world, at least on par with IT unit on campus. https://t.co/VSninKAJq5
— Erin (@barkivist) October 28, 2016
Need to find those who are burnt out and want to do something they can care about.
— Spellbound Blog (@spellboundblog) October 27, 2016
— Tim Gollins (@timgollins) October 28, 2016
For sure but perhaps instead of paying low they shouldn't do/preserve as much. But that's very contentious
— Euan Cochrane (@euanc) October 27, 2016
@sheilaMorr Both. We need to build our capacity but bring in the experts
— Anthea Seles (@archivista13) October 28, 2016
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.
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: