MARC Machine Readable Cataloging

1
MARCMachine Readable Cataloging MARC family

• Reference Rebecca Guenther (2004) New and
  traditional descriptive formats in the library
  environment

2
1. MARC21 Bibliographic Format

• MARC - 1960s --gt USMARC, CANMARC, UKMARC, etc.
• UNIMARC - 1977
• MARC21 1997, Harmonization of USMARC and
  CAN/MARC
• Translations in several languages
• MARC21 Concise Format for Bibliographic Data is
  available at http//www.loc.gov/marc/bibliographi
  c/ecbdhome.html
• MARC21 Formats are available at
  http//www.loc.gov/marc/
• Good introduction to the use of MARC
  Understanding MARC Bibliographic,
  http//www.loc.gov/marc/umb/

3
MARC 21Parts of a MARC record

• Leader identifies the beginning of a new record,
  type of record
• Directory think of it as the index to the
  record. Identifies the position and length of
  each field
• Control Fields coded information about the
  resource described, standard/control numbers,
  dates, language, etc. Some are called fixed
  fields due to their fixed length
• Variable fields more detailed description of the
  recourse, fields have variable length

4
MARC 21 Content designators

• Types of codes used to indicate content of a
  record
• tags 3-digit numbers (001-999) to encode fields
• e.g. 100 personal name main entry
• indicators 2 possible positions for each field,
  special information about that field
• e.g. 100 1_ surname as the entry element
• subfield codes combination of a delimiter and a
  lower case letter or number, to encode subfields
• e.g. 100 1_ a name

5
MARC21groups of fields (by hundreds)

• Bibliographic format
• 0XX Control information, numbers, codes
• 1XX Main entry
• 2XX Titles, edition, imprint/publication
• 3XX Physical description, etc.
• 4XX Series statements (as shown in the book)
• 5XX Notes
• 6XX Subject added entries
• 7XX Added entries other than subject or series
• 8XX Series added entries (other authoritative
  forms)

6
Parallels in MARC formats

• X00 Personal names
• X10 Corporate names
• X11 Meeting names
• X30 Uniform titles
• X40 Bibliographic titles
• X50 Topical terms
• X51 Geographic names

1XX Main entry 4XX Series statement 6XX Subject
heading 7XX Added entry 8XX Series added
entries
7
2. MARC Family

• 2.1 MARC XML
• 2.2 MODS, Metadata Object Description Schema
• 2.3 MADS, Metadata Authority Description Schema

8
New needs

• Need to take advantage of XML
• Establish standard MARC 21 in an XML structure
• Need simpler (but compatible) alternatives
• Development of MODS
• Need interoperability with different schemas
• Assemble coordinated set of tools
• Need continuity with current data
• Provide flexible transition options

9
(No Transcript)
10
MARC 21 (2709) record (machine view)

• 00967cam 2200277 a 4500 001000800000005001700008
  00800410002502000530022904000180028205000240031208
  20021003361000030003572450074003872600044004613000
  03500505440001200540500002000552650004200572651002
  500614
• 347139419990429094819.1931129s1994
  wauab 001 0 eng a 93047676
  a0898863872 (acid-free, recycled paper)
  c14.95 aDLCcDLCcDLC 00aGV1046.G3bG47
  199400a796.6/4/09432201 aSlavinski,
  Nadine,d1968-10aGermany by bike b20 tours
  geared for discovery /cNadine Slavinski.
  aSeattle, Wash. bMountaineers,cc1994. a238
  p. bill., maps c22 cm. 0aBy bike
  aIncludes index. 0aBicycle touringzGermanyxGu
  idebooks.

11
2.1 MARC 21 evolution to XML
12
MARC 21 in XML MARCXML

• MARCXML record
• XML exact equivalent of MARC (2709) record
• Lossless/roundtrip conversion to/from MARC 21
  record
• Simple flexible XML schema, no need to change
  when MARC 21 changes
• Presentations using XML stylesheets
• LC provides converters (open source)
• Adopted by OAI to replace oai_marc
• http//www.loc.gov/standards/marcxml

13
MARC21 (2709) to MARCXML

• ltrecord xmlns"http//www.loc.gov/MARC21/slim"gt
• ltleadergt00967cam 2200277 a 4500lt/leadergt
• ltcontrolfield tag"001"gt3471394lt/controlfieldgt
• ltcontrolfield tag"005"gt19990429094819.1lt/control
  fieldgt
• ltcontrolfield tag"008"gt931129s1994 wauab
  001 0 eng lt/controlfieldgt
• ltdatafield tag"020" ind1" " ind2" "gt
• ltsubfield code"a"gt0898863872 (acid-free,
  recycled paper) lt/subfieldgt
• ltsubfield code"c"gt14.95lt/subfieldgt
• lt/datafieldgt
• ltdatafield tag"040" ind1" " ind2" "gt
• ltsubfield code"a"gtDLClt/subfieldgt
• ltsubfield code"c"gtDLClt/subfieldgt
• ltsubfield code"d"gtDLClt/subfieldgt
• lt/datafieldgt
• ltdatafield tag"050" ind1"0" ind2"0"gt
• ltsubfield code"a"gtGV1046.G3lt/subfieldgt
• ltsubfield code"b"gtG47 1994lt/subfieldgt
• lt/datafieldgt
• ltdatafield tag"082" ind1"0" ind2"0"gt

14
MARCXML record (continued)

• ltdatafield tag"245" ind1"1" ind2"0"gt
• ltsubfield code"a"gtGermany by bike lt/subfieldgt
• ltsubfield code"b"gt20 tours geared for
  discovery /lt/subfieldgt
• ltsubfield code"c"gtNadine Slavinski.lt/subfieldgt
• lt/datafieldgt
• ltdatafield tag"260" ind1" " ind2" "gt
• ltsubfield code"a"gtSeattle, Wash. lt/subfieldgt
• ltsubfield code"b"gtMountaineers,lt/subfieldgt
• ltsubfield code"c"gtc1994.lt/subfieldgt
• lt/datafieldgt
• ltdatafield tag"300" ind1" " ind2" "gt
• ltsubfield code"a"gt238 p. lt/subfieldgt
• ltsubfield code"b"gtill., maps lt/subfieldgt
• ltsubfield code"c"gt22 cm.lt/subfieldgt
• lt/datafieldgt
• ltdatafield tag"440" ind1" " ind2"0"gt
• ltsubfield code"a"gtBy bikelt/subfieldgt
• lt/datafieldgt
• ltdatafield tag"500" ind1" " ind2" "gt

15
MARCXML to DC

• ltrdfDescription xmlnsrdf"http//www.w3.org/1999
  /02/22-rdf-syntax-ns" xmlnsdc"http//purl.org/d
  c/elements/1.1/"gt
• ltdctitlegtGermany by bike 20 tours geared for
• discovery lt/dctitlegt
• ltdccreatorgtSlavinski, Nadine,
  1968-lt/dccreatorgt
• ltdctypegttextlt/dctypegt
• ltdcpublishergtSeattle, Wash. Mountaineers,
• lt/dcpublishergt
• ltdcdategtc1994.lt/dcdategt
• ltdclanguagegtenglt/dclanguagegt
• ltdcsubjectgtBicycle touringlt/dcsubjectgt
• lt/rdfDescriptiongt

16
Uses of MARCXML and related tools

• Standardize MARC 21 across community for XML
  communication and manipulation
• Open MARC 21 to XML programming tools and
  presentation style sheets
• Standardize MARC 21 for OAI harvesting
• Standardize transformations to and from other
  standard formats (DC, ONIX, )
• Basis for evolution while maintaining
  standardization

17
2.2 MODS Metadata Object Description Schema

• Bibliographic element set
• Initiative of the Network Development and MARC
  Standards Office, Library of Congress
• Uses XML Schema
• Specifically for library applications, although
  could be used more widely
• A derivative (and subset) of MARC elements

18
Why MODS?

• XML based, web friendly, transportable,
  processible, configurable, sufficiently
  descriptive without being too complex, extensible
• Benefits over MARC MARC isnt XML based and
  cant easily be output from web forms. Requires
  special cataloging knowledge and systems to
  implement
• Investigating XML as a new more flexible syntax
  for MARC element set

19
Why MODS? (cont.)

• Need for rich hierarchical descriptive metadata
  in XML but simpler than full MARC, especially for
  complex digital library objects
• Benefits over Dublin Core DC doesnt have
  sufficient specificity. DC doesnt specify a
  syntax and is inconsistently applied. DC isnt
  extensible
• Need compatibility with existing library
  descriptions

20
Features of MODS

• Uses language-based tags
• Elements generally inherit semantics of MARC
• MODS does not assume the use of any specific
  cataloging code
• Reuse element descriptions throughout schema
• Not intended to be round-trippable
• Not intended to be a MARC replacement

21
MODS high-level elements

• Title Info
• Name
• Type of resource
• Genre
• Origin Info
• Language
• Physical description
• Abstract
• Table of contents
• Target audience

• Note
• Subject
• Classification
• Related item
• Identifier
• Location
• Access conditions
• Part
• Extension
• Record Info

22
MARCXML to MODS

• ltmods xmlns"http//www.loc.gov/mods/"gt
• lttitleInfogt
• lttitlegtGermany by bike 20 tours geared
  for discovery /lt/titlegt
• lt/titleInfogt
• ltname type"personal"gt
• ltnamePartgtSlavinski, Nadine,lt/namePartgt
• ltnamePart type"date"gt1968-lt/namePartgt
• ltrolegtltroleTerm typetextgtcreatorlt/roleTermgtlt/
  rolegt
• lt/namegt
• lttypeOfResourcegttextlt/typeOfResourcegt
• ltoriginInfogt
• ltplacegtltplaceTerm typecode
  authority"marc"gtwault/placeTermgt
• ltplaceTerm typetextgt Seattle, Wash.
  lt/placeTermgt
• lt/placegt
• ltpublishergtMountaineers,lt/publishergt
• ltdateIssuedgtc1994lt/dateIssuedgt
• ltissuancegtmonographiclt/issuancegt
• lt/originInfogt
• ltlanguagegt

23
MODS (continued)

• ltsubject authority"lcsh"gt
• lttopicgtBicycle touringlt/topicgt
• ltgeographicgtGermanylt/geographicgt
• lttopicgtGuidebooks.lt/topicgt
• lt/subjectgt
• ltclassification authority"lcc"gtGV1046.G3 G47
  1994lt/classificationgt
• ltclassification authority"ddc"
  edition"20"gt796.6/4/0943lt/classificationgt
• ltrelatedItem type"series"gt
• lttitleInfogtlttitlegtBy bikelt/titlegtlt/titleInfogt
• lt/relatedItemgt
• ltidentifier type"isbn"gt0898863872 (acid-free,
  recycled paper) lt/identifiergt
• ltidentifier type"lccn"gt93047676lt/identifiergt
• ltrecordInfogt
• ltrecordContentSourcegtDLClt/recordContentSourcegt
• ltrecordCreationDate encoding"marc"gt931129lt/reco
  rdCreationDategt
• ltrecordChangeDate encoding"iso8601"gt19990429094
  819.1
• lt/recordChangeDategt
• ltrecordIdentifiergt3471394lt/recordIdentifiergt
• lt/recordInfogt

24
http//lcweb4.loc.gov/

• MODS descriptions for each web site (but not each
  capture)
• Transformation from XML to HTML display
• Links to web archive

25
(No Transcript)
26
Differences between MODS and Dublin Core

• MODS has structure
• Names
• Related item
• Subject
• MODS is more MARC-like so more compatibility with
  existing descriptions
• Semantics
• Conversions
• Relationships between elements
• MODS includes record management information

27
Choosing MODS for descriptive metadata

• MODS is particularly useful for
• compatibility with existing bibliographic data
• embedded descriptions in related item
• Rich, hierarchical descriptions that work well
  with METS structural map
• out of the box schema can use ltextensiongt for
  local elements and to bring in external elements
  from other schemas

28
3 Transformation tools

• MARC toolkit
• Converter from MARC 21 to MARCXML
• Transformations between metadata formats
• MODS
• Dublin Core
• ONIX
• http//www.loc.gov/marcxml