Ead editor 2012
Download as PPT, PDF1 like599 views
The Archives Hub is an online aggregator of archival collection descriptions from over 200 UK repositories. It contains over 25,000 collection level descriptions and 100,000 lower level entries. This document provides an overview of the Archives Hub service, how to use the EAD Editor to create and edit archival finding aids, and exporting descriptions from other systems into the Archives Hub's EAD format.
Ead editor 2012
- 1. Jane Stevenson and Lisa Jeskins Archives Hub 2012
- 2. By the end of today’s session you will have learnt about: • The Archives Hub service • Using the EAD Editor to create and edit content • Embedding images and adding links to digital content
- 3. An aggregator for UK archives A JISC-funded service based at Mimas, The University of Manchester In service since 2000 Over 25,000 collection descriptions 100,000’s of lower-level entries Over 200 repositories contribute Management and service team at Manchester Development team at Liverpool Cheshire software
- 4. Higher/Further Education Specialist repositories Charities Learned institutions Local authorities Museum archives We encourage institutions to contact us John Rylands Library, Manchester
- 6. Flickr cc licence: soylentgreen23’s photostream Originally funded for collection-level but always multi-level Software/searches effective with both Collection descriptions can be updated at any time Researchers ask for detail, but also ask for descriptions to be available at any level rather than not
- 7. EAD: XML for archives ISAD(G) compliant ISO standard for language Thesauri for index terms We provide guidelines for best practice
- 8. It is XML, which is an international standard It is the most sustainable and future-proof option we have It is a simple and effective way of structuring content and providing meaning Machines can manipulate the content in all sorts of ways
- 9. Enable different kind of access to the data We support the principles of open data ◦ SRU ◦ OAI-PMH ◦ Z39.50
- 10. Effective cross-searching requires: ◦ Interoperability which requires ◦ Common standards
- 11. All Hub descriptions have their own identifiers – a unique reference An identifier is effectively a web address (http URI) Enables bookmarking of content Facilitates linking Enables exposure to Google
- 12. Hub Data Flow
- 13. Google (SEO) Blog Twitter Links from NRA Links to/from Copac Marketing strategy Networking, conferences and events More work on measuring impact
- 14. UKAD: UK Archives Discovery Network Genesis: subject portal using our API AIM25: collaboration to improve interoperability TNA: links from the NRA Copac: have links from the Hub to Copac records CALM/Adlib
- 15. Continuing to increase awareness and use Building images and links to content Utilising technology to best advantage Remaining relevant and sustainable Understanding Impact Understanding our users Flickr cc licence: hoodwink’s photostream
- 16. Increasing content and contributors Enhancing our user interface Automated data ingest Making the data ‘work harder’ Innovation through use of technology and understanding of user needs
- 17. Export descriptions from other sytems to the Archives Hub ◦ CALM ◦ AdLib ◦ Archivists Toolkit ◦ ICA AtoM ◦ Excel
- 18. You do not need to re-create descriptions Benefit from being part of the Hub – cross-searching, SEO, innovative projects Your descriptions are backed-up as EAD
- 19. ProjectHeadway: export routines for different data formats ◦ scripts to convert data ◦ requires mapping and an iterative process of development ◦ testing out the process with a few contributors before rolling-out
- 20. Get in touch Still in testing phase Need ‘guinea pigs’, especially if willing to work with us to help us hone our scripts
- 21. Run file -> reports -> archiveshub EAD 2002 Make the required edits in the Hub EAD Editor
- 22. Contact Adlib to ask for an XSLT for your institution Export description as xml, and apply the XSLT Make required edits in the Hub EAD Editor
- 23. Have a template for Excel Ensures your descriptions will convert to EAD May not be feasible to convert other Excel content – too diverse
- 24. See the website http://archiveshub.ac.uk/exporting/ Contact us: archiveshub@mimas.ac.uk
Editor's Notes
- #3: EAD Training Day: 27 April 2005
- #4: Generous JISC funding since inception. Enabled the Hub to grow with funding for content up until about 2006. Say what Mimas is and advantages of being part of a National Data Centre. Growing all the time. Have significant numbers of lower-level descriptions too. Emphasise that we welcome these. New contributors all the time. Cheshire software includes ‘Cheshire for Archives’ developed by Liverpool especially for EAD. Say what distributed means. Archives Hub Workshop 2010
- #5: So, have said about our remit, but we are still mainly HE/FE – they are our core contributors. Have also had consortium contributors in the past. We welcome archives of relevance to academic research. Building content v. Important to us (if you know of any likely contributors please encourage them to contact us). We ask potential contributors to make the case that their archives are of relevance for research, but in reality this means that practically all institutions who approach us are eligible. We have contributors such as the Institute of Electrical Engineers, Inst of Mechanical Engineers, Royal Institution, Royal Society, museums such as the Science Museum and Nat. Hist. Museum. Archives Hub Workshop 2010
- #6: Say a little bit about the principles behind the design of the site Archives Hub Workshop 2010
- #7: Emphasise the Hub has always had the ability to take and search multi-level descriptions. We know that researchers are keen to get as much detail as possible, although we have to balance this against providing a user-friendly interface. With our new software we have introduced visual aids to understanding the hierarchical nature of the collections, with a folder structure and hierarchical navigation. You will see that the EAD Editor makes multi-level descriptions easy to create. Archives Hub Workshop 2010
- #8: Underlying principles that we want technology to support are standards and interoperability as well as an effective and satisfying user experience. We use the Cheshire 3 information retrieval system, developed at Berkley and the University of Liverpool. Open source and free. Enabled us to implement a distributed system. Use of XML means we can take advantage of technology developed to create, store and process XML. Archives Hub Workshop 2010
- #9: EAD Training Day: 27 April 2005
- #10: Try to explain a bit about the benefits – it is all to do with ways into the data. Tell them what these interfaces are, but they do not need to understand them. Archives Hub Workshop 2010
- #12: Very important development. Talk about exposure to Google. Archives Hub Workshop 2010
- #13: Just point out that this is the basic flow of information. EAD is held natively. It is taken into an ‘EAD Store’ for each contributor and indexes are created (e.g. Full text, titles, names, etc). All this is then combined into one XML store and ‘meta indexes’ are created. You can see we did use Z39.50 to transport data, but we now use SRU. Archives Hub Workshop 2010
- #15: Collaboration is important to us, and these are examples of ways that we seek to disseminate our experience and expertise as well as learn from others. We are keen to find ways to promote the Hub and the archives that we represent and to make it easier for archivists to create and share content with different systems. Archives Hub Workshop 2010
- #16: Archives Hub Workshop 2010