The document provides an overview of MARC 21 bibliographic records, including a brief history of MARC and how it facilitates information exchange. It describes the main components of a MARC record, such as the record structure, data content, fixed and variable fields. Variable fields are identified by tags, indicators, delimiters and subfield codes to provide specific bibliographic data. The document also gives examples of MARC records and defines different field codes.
Call Girls Bhubaneswar 9777949614 call me Independent Escort Service Bhubaneswar
Marc 21 Session 1
1. Understanding MARC 21 Bibliographic Records Session 1 Presented by Emily Dust Nimsakont PowerPoint by Devra Dragos, Nebraska Library Commission; revised by Sharon Mason, Charity Martin & Emily Dust Nimsakont
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12. FIC Kaplow, Robert. KAP The cat who killed Lilian Jackson Braun : a parody / by Robert Kaplow. – Beverly Hills, Calif. : New Millennium Press, 2004, c2003. 213 p. ; 18 cm. In this bawdy parody, Ms. Jackson's headless body has been discovered in a men's room of a bar in Lower Manhattan. The police are busy filming reality television shows, so it falls to Braun's writer friend James Qafka and his Siamese cats, Ying-Tong and Poon-Tang, to solve the ghastly mystery. 1932407391 (pbk.) 1. Braun, Lilian Jackson--Fiction. 2. Manhattan (New York, N.Y.) --Fiction. I. Title.
13. 00922nam 2200217Ia 45 0001001300000003000600013005001700019008004100036040001300077020002200090043001200112049000900124100002000133245007700153260006500230300002100295520029900316600003600615651004100651994001200692ocm55654318 OCoLC20050909094919.0040615r20042003cau 000 1 eng d aMPIcMPI a1932407391 (pbk.) an-us-ny aTPBB1 aKaplow, Robert.14aThe cat who killed Lilian Jackson Braun :ba parody /cby Robert Kaplow. aBeverly Hills, Calif. :bNew Millennium Press,c2004, c2003. a213 p. ;c18 cm. aIn this bawdy parody, Ms. Jackson's headless body has been discovered in a men's room of a bar in Lower Manhattan. The police are busy filming reality television shows, so it falls to Braun's writer friend James Qafka and his Siamese cats, Ying-Tong and Poon-Tang, to solve the ghastly mystery.10aBraun, Lilian JacksonvFiction. 0aManhattan (New York, N.Y.)vFiction. aC0bTPB
14.
15. 00922nam 2200217Ia 45 0001001300000003000600013005001700019008004100036040001300077020002200090043001200112049000900124100002000133245007700153260006500230300002100295520029900316600003600615651004100651994001200692ocm55654318 OCoLC20050909094919.0040615r20042003cau 000 1 eng d aMPIcMPI a1932407391 (pbk.) an-us-ny aTPBB1 aKaplow, Robert.14aThe cat who killed Lilian Jackson Braun :ba parody /cby Robert Kaplow. aBeverly Hills, Calif. :bNew Millennium Press,c2004, c2003. a213 p. ;c18 cm. aIn this bawdy parody, Ms. Jackson's headless body has been discovered in a men's room of a bar in Lower Manhattan. The police are busy filming reality television shows, so it falls to Braun's writer friend James Qafka and his Siamese cats, Ying-Tong and Poon-Tang, to solve the ghastly mystery.10aBraun, Lilian JacksonvFiction. 0aManhattan (New York, N.Y.)vFiction. aC0bTPB
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28. Workform Type Bib. level Books a,t a,c,d,m Continuing resources a b,i,s Visual materials g,k,r,o a,b,c,d,i,m,s Maps e a,b,c,d,i,m,s Sound recordings i,j a,b,c,d,i,m,s Scores c a,b,c,d,i,m,s Computer files m a,b,c,d,i,m,s Mixed materials p c,d,i
29.
30.
31.
32.
33. Tags Cartoon from: Bibliotoons: A Mischievous Meander Through the Stacks & Beyond by Gary Handman.
34.
35.
36.
37.
38.
39.
40.
41. FIC Kaplow, Robert. KAP The cat who killed Lilian Jackson Braun : a parody / by Robert Kaplow. – Beverly Hills, Calif. : New Millennium Press, 2004, c2003. 213 p. ; 18 cm. In this bawdy parody, Ms. Jackson's headless body has been discovered in a men's room of a bar in Lower Manhattan. The police are busy filming reality television shows, so it falls to Braun's writer friend James Qafka and his Siamese cats, Ying-Tong and Poon-Tang, to solve the ghastly mystery. 1932407391 (pbk.) 1. Braun, Lilian Jackson--Fiction. 2. Manhattan (New York, N.Y.) --Fiction. I. Title.
42. FIC Kaplow, Robert. KAP The cat who killed Lilian Jackson Braun : a parody / by Robert Kaplow. – Beverly Hills, Calif. : New Millennium Press, 2004, c2003. 213 p. ; 18 cm. In this bawdy parody, Ms. Jackson's headless body has been discovered in a men's room of a bar in Lower Manhattan. The police are busy filming reality television shows, so it falls to Braun's writer friend James Qafka and his Siamese cats, Ying-Tong and Poon-Tang, to solve the ghastly mystery. 1932407391 (pbk.) 1. Braun, Lilian Jackson--Fiction. 2. Manhattan (New York, N.Y.) --Fiction. I. Title. 099 $a 100 $a 245 $a : $b / $c. . – 260 $a : $b, $c. 500 020 650 $a -- $v. 651 $a -- $v. 245 1
We will be referring to the handout on Commonly Used MARC Tags throughout the course, so be sure to have it with you for all the sessions.
A list of these resources is also available on the NLC web site, linked from the cataloging services page.
Library of Congress web site has explanations of the various MARC fields, along with general information and announcements.
People who have taken the basic skills class have already seen this, but this “Understanding MARC” publication is available both in print and online.
OCLC Bibliographic Formats and Standards is also a good source of information.
MARC allows the information contained in a catalog record (or bibliographic record) to be exchanged between systems. You can import records from LOC or OCLC because of this. AACR2 rules tell you how to form the information that fits into the MARC framework. AACR2 and MARC are two different entities. We’re mainly focusing on MARC, but it will be necessary to discuss AACR2 to explain some things we talk about.
ISO 2709 – 1973 – International standard ANSI Z39.2 – 1971 – National standard These standards allow vendors to design ILS to manipulate MARC data.
MARBI, etc., meet at ALA Conferences Versions of MARC – LC MARC in the 1960s, US MARC in the 1980s, MARC 21 in 2000
We will be focusing on bibliographic data, but there are also MARC standards for other categories of data.
This is an example of bibliographic information in card format.
This is the same information in raw MARC format – this is what the computer understands.
OCLC translates the raw MARC data to look like this.
The public interface of WorldCat uses the same information to create a display like this.
Because of MARC format, the information from a record in OCLC…
… can be downloaded into your own system. This is how the information looks in the Commission’s Mandarin system.
Various libraries can display MARC-formatted data in different ways, and can choose which data to display. For example the notes field from the original record is missing in this display.
Another example of how MARC information is displayed.
Another example of how MARC info is displayed.
Another example of how MARC info is displayed.
Another example of how MARC info is displayed.
MARC records are made up of both fixed and variable fields. This is an image of the fixed fields as they appear in OCLC. The fixed fields are used to indicate various aspects of the items you are cataloging.
One of the things that the fixed fields indicate is the type of item. It is important to use this field correctly (don’t use book records for CDs, etc.) We’ll see why this is important later. These are the most common type codes, but there are some others, such as k for 2-d non-projected images, and r for realia (which you might use for games or cake pans.)
The bibliographic level field describes the form in which the item is published. The most commonly used levels are m, s, and i, which is fairly new. The other ones are used occasionally.
This cheat-sheet can help you remember the codes for type and level that are most commonly seen with some various forms of items.
When creating a new record, you will have the choice of what kind of record you want to create. This is what it looks like in OCLC Connexion.
You can also do this when creating records in your own system. This is what it looks like in Mandarin.
Parts of a MARC record are record structure, data content, and content designation. Record structure includes the leader, which identifies the beginning of a new record. (This is something that catalogers have no control over.) Record structure also includes the record directory. For the rest of the record, data content is what is put into the content designation.
The indicators are referred to as individual numbers – i.e., “one-oh”, not “ten.”
The handout on MARC tags lists the indicators and what they are used for, as well as the subfields. You’ll notice NR next to some fields and subfields – this means that that field or subfield is non-repeatable (can’t be used more than once.) The R means a field or subfield is repeatable.
For example, you will see that in this example the subfield b is repeatable.
The tags are grouped by hundreds, according to what type of fields they are. If you want to refer to a group of tags in the same 100, the shorthand for this is to say “1XX” for the 100 fields, for example.
Here is a bibliographic record in card format…
And here are the codes that go with the sections of the record.
Fields with parallel content are fields for which the last two digits are used consistently across fields to represent the same type of data. For example, a 100, 600, or 700 field is always a personal name. These fields with parallel content are also fields that require authority control.
Subject headings are also fields that require authority control.
The 001 field is generated by OCLC, LC, or your local system, wherever the record is created.
I mentioned the leader briefly before. This is generated by the computer and the cataloger has no control over it. The 008 is the fixed fields that we talked about before.
In OCLC, the 008 looks like this and is easier to read. When it is read by the computer, it is translated to a string of numbers and letters.
This is what the 008 looks like in our Mandarin system.. It appears as a single string in the record, but it can be expanded and edited.
The codes entered in the 008 show up in the string of characters read by the computer.
The 008 fields determine how things display in your local system. For example, the audio book and large type icons in this catalog display because those icons are linked to fields in the 008. (The difference between the CD audiobook and the cassette audiobook is determined by something else, which we will discuss later.)
Here’s an example: Here is the 008 for a regular format book.
And here is the 008 for a large print book. The d in the form field indicates large print.
The 006 field and 007 field are used to describe physical characteristics that can’t be coded in the fixed fields. The 006 field is used for additional material information that is not included in the fixed field; the coding is the same for this field as for the fixed field. For example, you would use this field in you had a serial that was issued on CD. You could cover the characteristics relating to it being a serial in the fixed field and describe the characteristics relating to it being a computer resource in the 006. The 007 is used to describe additional physical characteristics that can not be covered in the fixed field. The 007 is required for some categories of resources, like videorecordings or electronic resources.
To go back to our earlier example, the 007 field is where the information to provide the icon for either CD audio book or cassette audio book comes from. This is why codes are important – your local system draws on the codes to display information.
In a situation like that, where both items are audio books, in the fixed field, the type designation is the same for both (i for sound recording).
However, the 007 field is where the two are distinguished. The top one has s for sound recording and d for sound disc, while the bottom one has s for sound recording and s for sound cassette.
As another example, you can see in this screenshot from WorldCat how the information from the 007 field is used.
In this example, it looks like the 007 was incorrectly coded. The record
This week’s assignment has questions about your institution’s use of MARC records. It is due next Wednesday, August 5.
Our next session will cover fields 245 to 250. Remember to bring your Commonly Used MARC tags to that session.