Archives hub ead 2011_lifeshare


Published on

PPT for EAD training.

Published in: Education
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • EAD Training Day: 27 April 2005
  • 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
  • Say a little bit about the principles behind the design of the site Archives Hub Workshop 2010
  • 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
  • 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
  • EAD Training Day: 27 April 2005
  • 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
  • Key UKAD partners: Access 2 Archives, Archives Hub, AIM25, Archives Wales, Genesis, Janus, National Register of Archives, Scottish Archives Network, A Vision of Britain EAD Training Day: 27 April 2005
  • EAD Training Day: 27 April 2005
  • EAD Training Day: 27 April 2005 In information technology, extensible describes something, such as a program, programming language, or protocol, that is designed so that users (or later designers) can extend its capabilities.
  • EAD Training Day: 27 April 2005
  • EAD Training Day: 27 April 2005
  • EAD Training Day: 27 April 2005
  • EAD Training Day: 27 April 2005 In order to be so flexible and powerful, the structure of XML is actually very strictly defined. A document must adhere to certain rules in order to be ‘well-formed’
  • EAD Training Day: 27 April 2005
  • Talk about exchange of information – need to agree rules – DTD/schemas EAD Training Day: 27 April 2005
  • EAD Training Day: 27 April 2005
  • EAD Training Day: 27 April 2005
  • EAD Training Day: 27 April 2005 It is always best to start with definitions so what then is EAD: EAD then is designed to represent finding aids electronically – it is a standard for the structure of electronic finding aids. As we will see, however, it is not a content standard in its own right EAD is designed to display finding aids on the internet, or locally, and allow them to be indexed, searched, retrieved and navigated EAD is standards based. It is compatible with archival description standards, such as ISAD(G) and with technical standards such as XML. We will look at the relationships to these standards more this morning. As such it is a future proofed technology especially as:
  • EAD Training Day: 27 April 2005 EAD is flexible enough to deal with all types of finding aids EAD can be used to convert old finding aids to electronic form (we use it for A2A) as well as create new ones
  • We will now look at EAD’s structure in detail. These slides show the tags as examples – this is not proper ead tagging. I have not after this slide showed the closing tags for example. An EAD document then begins and ends with an <ead> tag. Within that there are two mandatory parts nested within these.
  • We will now look at EAD’s structure in detail. These slides show the tags as examples – this is not proper ead tagging. I have not after this slide showed the closing tags for example. An EAD document then begins and ends with an <ead> tag. Within that there are two mandatory parts nested within these.
  • EAD Training Day: 27 April 2005 How then does EAD relate to al this. Well we have seen that particular XML (or SGML) documents can have their structures (their grammar) defined in of DTDs. A DTD then is simply a computer file, or files, (with the extension .dtd) that hold(s) the rules relating to particular documents. They are in fact simple text files that can be written in text editors like notepad. The DTD files are needed by software to create, validate and process EAD finding aids for display. The DTD for the type of document called an archival finding aid is the EAD.dtd. The EAD 2002 DTD is in fact modular – that is composed of several parts, each represented by an individual file – you can see these on your handouts and I won’t go into any more detail here. These files are available to download from the official EAD website, which we will say more about after coffee.
  • EAD Training Day: 27 April 2005 Library of Congress Official EAD site: As said EAD maintained by the Network Development and MARC Standards Office of the Library of Congress and this is the site they have for EAD. General Information: Under general information you will find background information covering the areas talked about before coffee. Also, however, there is a link to the EAD listserv. There is an online discussion group of EAD users which is extremely useful. This link gives instructions on how to subscribe to the list. You are welcome to simply read the discussions going on and reply or send your own questions - people are very good about answering and beginners need not be intimidated. The is also an archive of messages that can be looked at for any issue that you may have. This site also has all the official documentation: The DTD itself and the supporting documents such as: EAD Tag Library The Tag library gives a natural language translation of the EAD DTD for us users, which copious examples. It follows the break down of finding aids into various elements, which are described here element by element. It also lists the attributes that may qualify elements. It interprets the rules in the DTD and specifies where each element may (or may not be used) and how attributes may be used for each element; ; especially useful is the EAD structure overview. Which we will now look at in more detail. Technical Guidelines More detailed are the technical application guidelines, although these are not yet available for EAD 2002. Those for version 1.0 are still very applicable and I recommend them. These discuss administrative concerns, authoring, publishing etc of EAD Documents. They also have good introductions to SGML/XML and linking of documents. Appendices include maps (crosswalks) with ISAD(G) and other standards. If you do any serious work with EAD these are the documents to go to. EAD Roundtable Help Pages: There is also a link on this site to a list of examples of EAD encoded files on the Web with links. A very useful way to look at all the various different methods of delivery etc. This list is actually hosted by the site of the which is the equivalent of the EAD/Data Exchange Group in the Society of American Archivists. This site has very useful sections of online readings re SGML and XML (as already noted); Notes about Software and specific files for particular editors; and The EAD Cookbook.
  • Archives hub ead 2011_lifeshare

    1. 1. Lisa Jeskins and Bethan Ruddock Archives Hub Mimas Thurs 10 th March February 2010
    2. 2. <ul><li>By the end of today’s session we will have given you an introduction to: </li></ul><ul><ul><li>The Archives Hub </li></ul></ul><ul><ul><li>XML </li></ul></ul><ul><ul><li>EAD </li></ul></ul><ul><ul><li>EAD Editor </li></ul></ul>
    3. 3. <ul><li>JISC-funded service based at Mimas, The University of Manchester </li></ul><ul><li>In service since 2000 </li></ul><ul><li>Approx 25,000 collection descriptions </li></ul><ul><li>180 repositories </li></ul><ul><li>Management and service team at Manchester </li></ul><ul><li>Development team at Liverpool </li></ul>
    4. 4. Archives Hub Workshop 2010
    5. 5. <ul><li>Higher/Further Education </li></ul><ul><li>Consortium contributions </li></ul><ul><li>Institutions with a research agenda </li></ul><ul><li>Others on a case-by-case basis </li></ul><ul><li>We encourage institutions to contact us </li></ul>John Rylands Library, Manchester
    6. 6. <ul><li>EAD is XML for archives </li></ul><ul><li>We have EAD2002 (DTD) </li></ul><ul><li>Cheshire search engine searches and retrieves EAD descriptions </li></ul><ul><li>EAD is ISAD(G) compliant </li></ul>
    7. 7. <ul><li>It is XML, which is an international standard </li></ul><ul><li>It is a great format to store finding-aids, as it is sustainable and futureproof (? Hopefully) </li></ul><ul><li>It is a simple and effective way of structuring content and providing meaning </li></ul><ul><li>Machines can manipulate the content in all sorts of ways </li></ul>
    8. 8. <ul><li>UKAD: part of the UK Archives Discovery Network </li></ul><ul><li>Genesis: exploratory project to share data </li></ul><ul><li>AIM25: collaboration to improve interoperability </li></ul><ul><li>TNA: plans to create links from the NRA </li></ul><ul><li>Copac: have links from the Hub to Copac records </li></ul><ul><li>CALM/Adlib </li></ul>
    9. 10. <ul><li>Effective cross-searching requires: </li></ul><ul><ul><li>Interoperability </li></ul></ul><ul><ul><ul><li>which requires </li></ul></ul></ul><ul><ul><li>Common standards </li></ul></ul>
    10. 12. <ul><li>XML = Extensible Markup Language </li></ul><ul><li>XML is a system for creating languages: </li></ul><ul><ul><li>Or a meta - language </li></ul></ul><ul><li>Use XML to design your own markup language , consisting of meaningful tags that describe the data they contain </li></ul><ul><li>Create a language for describing …anything </li></ul>
    11. 13. <ul><li>the ability to exchange/share data </li></ul><ul><li>provides advantages of cross-searching, so user can easily search across and retrieve resources from a variety of different systems </li></ul><ul><li>allows users to move beyond individual websites for individual resources </li></ul><ul><li>integrates information resources presented in different formats </li></ul><ul><li>XML facilitates interoperability </li></ul>
    12. 14. <ul><li>XML does not do anything itself . It is pure information wrapped in XML tags </li></ul><ul><li>You must use other means to send, receive or display the data </li></ul>XML XML technologies is used by to create Detailed description to view in a browser Summary entry to view in a browser PDF for print
    13. 15. <ul><li>XML is not about content, though there might be certain restrictions on content </li></ul><ul><li>XML is essentially about structure </li></ul><ul><li>Creating a consistent structure via XML tagging enables content to be easily identified (by machines) and used in different ways </li></ul>
    14. 16. <title> Alice in Wonderland </title> *XML allows you to define your tags* <book>Alice in Wonderland</book> <filmtitle>Alice in Wonderland</filmtitle> <tag> content </tag>
    15. 17. Title Alice in Wonderland Author Lewis Carroll Extent 1 volume Format hardback
    16. 18. <ul><li><books> </li></ul><ul><li>< title >Alice in Wonderland</ title > </li></ul><ul><li>< author >Lewis Carroll</ author > </li></ul><ul><li>< extent >1 volume</ extent > </li></ul><ul><li>< format >hardback</ location > </li></ul><ul><li></books> </li></ul>
    17. 19. <ul><li>Valid XML provides consistency and facilitates the exchange of data </li></ul><ul><li>Valid XML is important for displaying, processing and exchanging XML in a wider environment </li></ul><ul><ul><ul><ul><ul><li>a root element is required </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><li><catalog> </li></ul></ul></ul></ul><ul><ul><ul><ul><li>… ..all your tags and content… </li></ul></ul></ul></ul><ul><ul><ul><ul><li></catalog> </li></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>closing tags are required </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>case matters </li></ul></ul></ul></ul></ul>
    18. 20. <ul><li>elements must be properly nested </li></ul><ul><li><physdesc> </li></ul><ul><li><extent>10 boxes</extent> </li></ul><ul><li></physdesc> </li></ul><ul><li><physdesc> </li></ul><ul><li><extent>10 boxes</physdesc> </li></ul><ul><li></extent> </li></ul>
    19. 21. <ul><li>Look at the album information on your sheet of paper </li></ul><ul><li>In pairs, create xml tags for the information that you see </li></ul><ul><li>e.g. </li></ul><ul><ul><li><title></title>, <albumtitle></albumtitle> </li></ul></ul><ul><ul><li><artist></artist>, <singer></singer>, <band></band> </li></ul></ul><ul><li>10 mins to create tags </li></ul><ul><li>5 mins to feedback </li></ul>
    20. 22. <ul><ul><ul><ul><ul><li><catalog> </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li><cd> </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li><title> Lungs </title> </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li><artist> Florence and the Machine </artist> </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li><genre> indie </genre> </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li><year> 2009 </year> </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li></cd> </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li><cd> </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li><title> Slash </title> </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li><artist> Slash </artist> </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li><genre> rock </genre> </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li><year> 2010 </year> </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li></cd> </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li></catalog> </li></ul></ul></ul></ul></ul>
    21. 23. <ul><li>A Document Type Definition or Schema define s the building blocks of an XML document </li></ul><ul><li>It specifies elements and attributes and defines how they can be used </li></ul><ul><li>P eople can agree to use a common DTD/Schema for interchanging data </li></ul>
    22. 24. XML file DTD or Schema Valid XML Blue Elephant Papers …………………… ………… Blue Elephant Papers Browse List
    23. 27. <ul><li>International standard, supported by the W3C </li></ul><ul><li>Open, licence free and platform neutral </li></ul><ul><li>Human and machine readable </li></ul><ul><li>Hierarchical structure (good for archive descriptions) </li></ul><ul><li>Can be used for data exchange </li></ul><ul><ul><li>XML is the main basis for defining data exchange languages </li></ul></ul><ul><ul><li>Meaningful tags facilitate extraction – data can be manipulated as required </li></ul></ul><ul><li>Government mandates XML for data exchange (e-GIF) </li></ul><ul><li>XML has been widely adopted commercially as well as in the public sector </li></ul>
    24. 29. <ul><li>EAD = Encoded Archival Description </li></ul><ul><li>EAD is XML for finding aids </li></ul><ul><li>A data structure standard – not a content standard </li></ul><ul><li>EAD Working Group (EADWG) </li></ul>
    25. 30. <ul><li>Allows finding aids to be indexed, searched, retrieved and navigated </li></ul><ul><li>Compatible with ISAD(G) </li></ul><ul><li>Flexible enough to deal with all types of finding aids </li></ul><ul><ul><li>single or multi-level, long or short, lists or calendars etc. </li></ul></ul><ul><li>Can create new finding aids as well as converting old ones to standardised form </li></ul><ul><li>Can share data between systems </li></ul>
    26. 31. <ul><li><ead> </li></ul><ul><li><eadheader> </li></ul><ul><li></eadheader> </li></ul><ul><li><archdesc> </li></ul><ul><li><did></did> </li></ul><ul><li></archdesc> </li></ul><ul><li></ead> </li></ul>
    27. 32. <ul><li><ead> EAD root element </li></ul><ul><li><eadheader> EAD file information wrapper </li></ul><ul><li></eadheader> </li></ul><ul><li><archdesc> Finding aid wrapper </li></ul><ul><li><did></did> Core collection information wrapper </li></ul><ul><li></archdesc> </li></ul><ul><li></ead> </li></ul>
    28. 33. <archdesc> <eadheader> <did> sub-fonds descriptions
    29. 34. <ul><li><archdesc level=&quot;fonds&quot;> </li></ul><ul><li><did> </li></ul><ul><li><unitid> GB 0001 Foster </unitid> </li></ul><ul><li><unittitle> Papers of Dr Foster </unittitle> </li></ul><ul><li><unitdate normal = &quot; 1820-1833 &quot;> 1820-1833 </unitdate> </li></ul><ul><li><repository> University of Gloucestershire </repository> </li></ul><ul><li><physdesc> </li></ul><ul><li><extent> 1 box </extent> </li></ul><ul><li><physfacet> Four folders of letters, 230 folios </physfacet> </li></ul><ul><li></physdesc> </li></ul><ul><li><langmaterial><language langcode= “eng” > English <language> </li></ul><ul><li></langmaterial> </li></ul><ul><li><origination> Dr Foster </origination> </li></ul><ul><li></did> </li></ul>
    30. 35. <ul><li>EAD version 1 DTD </li></ul><ul><li>EAD 2002 DTD </li></ul><ul><li>EAD 2002 Schema </li></ul><ul><li>Available from </li></ul><ul><li>Human-readable version: EAD Tag Library (Society of American Archivists) </li></ul>
    31. 36. <ul><li>Library of Congress Official EAD site: </li></ul><ul><li>Tag Library: </li></ul><ul><li>EAD Roundtable Help Pages: </li></ul>
    32. 37. <ul><li>XML is an international standard for sharing information </li></ul><ul><li>EAD is the XML language for archival finding aids </li></ul><ul><li>EAD is not a content standard </li></ul><ul><li>EAD will become increasingly important </li></ul>