Mods0210

476 views

Published on

This file is decribed about the LC(Library of Congress)'s MODS.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
476
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Mods0210

  1. 1. 지식기반실<br />학생연구원<br />송 유 화<br />
  2. 2. The LC&apos; Network Development and MARC Standards Office<br /> developed in 2002 <br />for a bibliographic element set <br />that may be used for a variety of purposes, <br />and particularly for library applications. <br />As an XML schema <br />It is intended to be able to carry selected data from MARC 21. <br />It includes a subset of MARC fields <br />uses language-based tags rather than numeric ones, in some cases regrouping elements from the MARC 21 bibliographic format. <br />As of June 2009 this schema is in its third version (version 3.3). <br />The standard is maintained by the MODS Editorial Committee of the Library of Congress . <br />Intro<br />
  3. 3. Jenn Riley, Indiana University, Chair<br />Joe  Altimus, Arizona State University<br />Jan Ashton, British Library <br />Ann Caldwell, Brown University<br />John Chapman, OCLC<br />Rebecca Guenther, Library of Congress<br />Bill Leonard, Library and Archives Canada<br />Sally McCallum, Library of Congress<br />Terry Reese, Oregon State University <br />Sarah Shreeves, University of Illinois/Urbana-Champaign<br />Jon Stroop, Princeton University <br />Robin Wendler, Harvard University<br /> Interact with other metadata efforts and standards where there is synergy (e.g. MARC, Dublin Core, METS, and PREMIS)<br />Current MODS Editorial Committee Membership <br />
  4. 4. The element set is richer than Dublin Core <br />The element set is more compatible with library data <br /> than ONIX<br />The schema is more end user oriented than <br /> the full MARCXML schema <br />The element set is simpler than the full MARC format <br /><ul><li>Appendix A & B</li></ul>Advantages<br />
  5. 5. Elements<br /><ul><li>Title Info
  6. 6. Name
  7. 7. Type of resource
  8. 8. Genre
  9. 9. Language
  10. 10. Physical description
  11. 11. Abstract
  12. 12. Table of contents
  13. 13. Target audience </li></ul>Note<br />Subject<br />Classification<br />Related item<br />Identifier<br />Location<br />Access conditions<br />Part<br />Extension<br />Record Info<br /><ul><li> Appendix C
  14. 14. http://www.loc.gov/standards/mods/v3/mods-userguide-elements.html</li></li></ul><li>Language and Related Attributes<br />lang - specify the language used within individual elements, This is equivalent to authority=&quot;iso639-2b&quot; <br />xml:lang - is used to specify the language used within individual elements, using specifications in RFC 3066.<br />transliteration - It specifies the transliteration technique used within individual elements. There is no standard list<br />Date Attributes<br />Encoding<br />W3cdtf<br />Iso8601<br />MarcMARC 21 rules in field 008/07-14 <br />point If no point attribute is specified, date is assumed to be a single date. (start, end)<br />keyDate - The following value is used with the keyDate attribute: <br />yes - This value is used so that a particular date may be distinguished among several dates. Thus for example, when sorting MODS records by date, a date with keyDate=&quot;yes&quot; would be the date to sort on<br />Qualifier<br />approximate - This value is used to identify a date that may not be exact, but is approximated, such as &quot;ca. 1972&quot;.<br />inferred - This value is used to identify a date that has not been transcribed directly from a resource, such as &quot;[not before 1852]&quot;.<br />questionable - This value is used to identify a questionable date for a resource, such as &quot;1972?&quot;.<br />Linking attributes<br />ID - This attribute is used to link internally and to reference an element from outside the instance.<br />xlink - This attribute is used for an external link.<br />Attribute<br />
  15. 15. Example<br /><ul><li>Appendix D</li></li></ul><li>MODS’ schema does not target round-tripability with MARC 21<br />some loss of specificity in tagging or loss of data<br />Limitations<br />
  16. 16. Brown Uni.CDI(Center for Digital Initiatives)<br />http://dl.lib.brown.edu/documentation/MODS.pdf<br />고려대학교 디지털도서관 <br />LC’AudioVisual Prototype project<br />http://www.loc.gov/rr/mopic/avprot/avprhome.html<br />MINERVA(Mapping the INternet Electronic Resource Virtual Archive)<br />http://www.loc.gov/minerva/<br />Oxford University’s Digital Library <br />University of Florida Libraries and Digital Library of the Caribbean/ Dates: 2006 - (ongoing)<br />http://www.uflib.ufl.edu/ufdc2/technical/index.htm<br />http://www.loc.gov/standards/mods/registry.php<br />Implementation<br />
  17. 17. Reference<br />http://www.loc.gov/standards/mods/<br />Morgan Cundiff .Using METS and MODS to Create anXML Standards-basedDigital Library Application .<br />Ann Caldwell. Introduction to MODS. 2006.<br />이수상. MODS-디지털 도서관의 서지정보 표준 메타데이터.2004.2004년도 KISTI”메타데이터설계 및 적용사례” 세미나 발표 자료.<br />

×