Posts

Showing posts from September, 2017

The first UK AtoM user group meeting

Image
Yesterday the newly formed UK AtoM user group met for the first time at St John's College Cambridge and I was really pleased that myself and a colleague were able to attend. Bridge of Sighs in Autumn (photo by Sally-Anne Shearn) This group has been established to provide the growing UK AtoM community with a much needed forum for exchanging ideas and sharing experiences of using AtoM. The meeting was attended by about 15 people though we were informed that there are nearly 50 people on the email distribution list. Interest in AtoM is certainly increasing in the UK. As this was our first meeting, those who had made progress with AtoM were encouraged to give a brief presentation covering the following points: Where are you with AtoM (investigating, testing, using)? What do you use it for? (cataloguing, accessions, physical storage locations) What do you like about it/ what works? What don’t you like about it/ what doesn’t work? How do you see AtoM fitting into your wider technical inf

Moving a proof of concept into production? it's harder than you might think...

Image
Myself and colleagues blogged a lot during the Filling the Digital Preservation Gap Project  but I’m aware that I’ve gone a bit quiet on this topic since… I was going to wait until we had a big success to announce, but follow on work has taken longer than expected. So in the meantime here is an update on where we are and what we are up to. Background Just to re-cap, by the end of phase 3 of Filling the Digital Preservation Gap we had created a working proof of concept at the University of York that demonstrated that it is possible create an automated preservation workflow for research data using PURE, Archivematica, Fedora and Samvera (then called Hydra!). This is described in our phase 3 project report (and a detailed description of the workflow we were trying to implement was included as an appendix in the  phase 2 report ). After the project was over, it was agreed that we should go ahead and move this into production. Progress has been slower than expected. I hadn’t quite apprecia

Harvesting EAD from AtoM: we need your help!

Image
Back in February I published a blog post about a project to develop AtoM to allow EAD (Encoded Archival Description) to be harvested via OAI-PMH (Open Archives Initiative Protocol for Metadata Harvesting): “ Harvesting EAD from AtoM: a collaborative approach ” Now that AtoM version 2.4 is released (hooray!), containing the functionality we have sponsored, I thought it was high time I updated you on what has been achieved by this project, where more work is needed and how the wider AtoM community can help. What was our aim? Our development work had a few key aims: To enable finding aids from AtoM to be exposed as EAD 2002 XML for others to harvest. The partners who sponsored this project were particularly keen to enable the Archives Hub to harvest their EAD. To change the way that EAD was generated by AtoM in order to make it more scalable. Moving EAD generation from the web browser to the job scheduler was considered to be the best approach here. To make changes to the existing DC (