No…we’re not thinking of changing the name…but I am thinking about a presentation that I’m giving on the Archives Hub in the context of ‘Archives 2.0′.
We’ve been doing a great deal of work recently that relates to the interoperability of the Hub. As part of an Enhancements Project taking place at Mimas, we are promoting data sharing, and an important part of this is work on import and export routines between services. Ideally, of course, it would be great to share data without any need for complex routines that effectively alter the structure of the data to make it suitable for different services, and remote searching of other data sources is something that we are also going to be looking at. But I guess that whilst we like to think of our service as interoperable, it’s currently still within certain limitations. It is problematic even sharing data held as EAD (Encoded Archival Description XML for archives) because EAD is really quite a permissive standard, allowing a great deal of flexibility and thus in some ways inhibiting easy data exchange. It is even more challenging to share data held in different databases. Many archives use the CALM system or the AdLib system, and we are working towards improving the export option from these systems, thus allowing archivists to have all of the advantages of an integrated management system, whilst at the same time enabling them to contribute to a cross-searching service such as the Hub.
I firmly believe that Archives 2.0, as an implementation of Web2.0 for archives, should primarily be viewed as an attitude rather than a suite of tools or services, characterised by openness, sharing, experimentation, collaboration, integration and flexibility that enables us to meet different user needs. Whilst widgets and whizzy features on websites are certainly a way to work towards this, I do think that more fundamentally we should be thinking about the data itself and how we can open this up.