<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress/wordpress-mu-1.2.5" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>

<channel>
	<title>Non-Roman Cataloging</title>
	<link>http://library.osu.edu/blogs/nonromancat</link>
	<description>Welcome to OSUL Non-Roman Cataloging Blog! - "The next best thing to knowing something is knowing where to find it." - Samuel Johnson.  So, here we are: Find updates on procedures, guidelines and new projects at our Non-Roman Section!</description>
	<pubDate>Wed, 27 Aug 2008 16:35:23 +0000</pubDate>
	<generator>http://wordpress.org/?v=wordpress-mu-1.2.5</generator>
	<language>en</language>
			<item>
		<title>MARC in Practice (2) Call Number and Subject Heading Fields</title>
		<link>http://library.osu.edu/blogs/nonromancat/2008/08/27/marc-in-practice-2-call-number-and-subject-heading-fields/</link>
		<comments>http://library.osu.edu/blogs/nonromancat/2008/08/27/marc-in-practice-2-call-number-and-subject-heading-fields/#comments</comments>
		<pubDate>Wed, 27 Aug 2008 15:56:11 +0000</pubDate>
		<dc:creator>Sherab Chen</dc:creator>
		
		<category><![CDATA[► General Procedures]]></category>

		<guid isPermaLink="false">http://library.osu.edu/blogs/nonromancat/2008/08/27/marc-in-practice-2-call-number-and-subject-heading-fields/</guid>
		<description><![CDATA[
====================
OUTLINE
I. Call number fields

Difference between 050 and 090 fields
Sub-fields and punctuation issues

II. Subject Heading fields

Types of Subject Headings
LC Subject Headings and &#8220;quasi-LC Subject Headings&#8221;
Subfields

III. Correlation
====================

I. Call number fields

At OSUL, we assign call numbers according to the Library of Congress Call Number (LCC) system
In a MARC record, there are two kinds of call number fields for [...] ]]></description>
			<content:encoded><![CDATA[<blockquote><p>
====================<br />
OUTLINE<br />
I. Call number fields</p>
<ol>
<li>Difference between 050 and 090 fields</li>
<li>Sub-fields and punctuation issues</li>
</ol>
<p>II. Subject Heading fields</p>
<ol>
<li>Types of Subject Headings</li>
<li>LC Subject Headings and &#8220;quasi-LC Subject Headings&#8221;</li>
<li>Subfields</li>
</ol>
<p>III. Correlation<br />
====================
</p></blockquote>
<p><strong>I. Call number fields</strong></p>
<ul>
<li>At OSUL, we assign call numbers according to the Library of Congress Call Number (LCC) system</li>
<li>In a MARC record, there are two kinds of call number fields for LCC: 050 and 090</li>
<li>The 050 field is for call numbers assigned either directly by Library of Congress catalogers or someone else on the level of assigning a LC Call number. When we create new record, we do not use the 050 field, instead, we use the 090 field.</li>
<li>The 090 field is for &#8220;locally assigned LC-type call number,&#8221; which means call numbers assigned by us according to LCC.</li>
</ul>
<p>In copy-cataloging</p>
<ul>
<li>when you find a record that (1) has <strong>only</strong> a 050 call number and (2) the form of that call number agrees with our local practice, accept that 050 field. This call number will be the call number we use for shelving.</li>
<li>at time when you find a record that (1) has <strong>only</strong> a 050 call number but (2) the form of that call number does not agree with our local practice, leave the 050 field alone, add a 090 field and put there the call number modified according to our local practice. For instance, if you see<br />
050 _ _ DS912.382.C48 $b C47 2007 $b Z54<br />
leave it alone, and add a 090 field following it, your record will look like this:<br />
050 _ _ DS912.382.C48 $b C47 2007 $b Z54<br />
090 _ _ DS912.382.C48 $b C47 2007</li>
<li>By default, the OPAC system (i.e. OSCAR) will automatically select the call number in the second call number field!</li>
</ul>
<p><strong>II. Subject Heading fields</strong></p>
<p>정조<br />
안동시</p>
<p><strong>III. Classification (Call number) and Subject Heading Correlation</strong></p>
<ul>
<li>We can assign more than one Subject Headings for a single publication. Totally, we can have 6 Subject Headings in a bib record.</li>
<li>The Classification is correlated with the first Subject Heading. In other words, assign a call number according to the first Subject Heading in a bib record.</li>
<li>Therefore, if a bib record has more than one Subject Heading fields, the first one should contain the major Subject Heading assigned for the publication. And the call number is determined by that Subject Heading.</li>
<li>In case if a work treats two subjects eaqually, the subject comes first will be the first Subject Heading.<br />
For instance, if a book is titled<br />
&#8220;Modern Mathematics and Western Philosophy,&#8221;<br />
put mathematics in the first Subject Heading field, provide secondary headings for western philosophy, and assign a call number for modern mathematics.</li>
<li>We do not have to assign Subject Headings for a fiction. In other words, a bib record made for a fiction may only have a call number.</li>
</ul>
 ]]></content:encoded>
			<wfw:commentRss>http://library.osu.edu/blogs/nonromancat/2008/08/27/marc-in-practice-2-call-number-and-subject-heading-fields/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Oversized Items</title>
		<link>http://library.osu.edu/blogs/nonromancat/2008/08/26/oversized-items/</link>
		<comments>http://library.osu.edu/blogs/nonromancat/2008/08/26/oversized-items/#comments</comments>
		<pubDate>Tue, 26 Aug 2008 19:58:12 +0000</pubDate>
		<dc:creator>Sherab Chen</dc:creator>
		
		<category><![CDATA[► General Procedures]]></category>

		<guid isPermaLink="false">http://library.osu.edu/blogs/nonromancat/2008/08/26/oversized-items/</guid>
		<description><![CDATA[&#8220;Oversize overrides the shelving rules.&#8221;
If a book is over 30 cm in height (or width), it will be treated as an oversized book, and shelved at a designated area in the library no matter what call number it is assigned. Each branch library will decide where to put the oversized items.
You need to do two [...] ]]></description>
			<content:encoded><![CDATA[<p><em>&#8220;Oversize overrides the shelving rules.&#8221;</em></p>
<p>If a book is over 30 cm in height (or width), it will be treated as an oversized book, and shelved at a designated area in the library no matter what call number it is assigned. Each branch library will decide where to put the oversized items.</p>
<p>You need to do two things when cataloging an oversized item:</p>
<ol>
<li>On the item record, choose the location code for oversized items.</li>
<li>Mark an asterisk beside the classification when you write call number on the piece.</li>
</ol>
<p>There&#8217;s no special treatment on the bibliographic record.</p>
 ]]></content:encoded>
			<wfw:commentRss>http://library.osu.edu/blogs/nonromancat/2008/08/26/oversized-items/feed/</wfw:commentRss>
		</item>
		<item>
		<title>MARC in Practice</title>
		<link>http://library.osu.edu/blogs/nonromancat/2008/08/06/marc-in-practice/</link>
		<comments>http://library.osu.edu/blogs/nonromancat/2008/08/06/marc-in-practice/#comments</comments>
		<pubDate>Wed, 06 Aug 2008 17:48:33 +0000</pubDate>
		<dc:creator>Sherab Chen</dc:creator>
		
		<category><![CDATA[► General Procedures]]></category>

		<guid isPermaLink="false">http://library.osu.edu/blogs/nonromancat/2008/08/06/marc-in-practice/</guid>
		<description><![CDATA[MARC in a nutshell

MARC stands for &#8220;MAchine Readable Cataloging&#8221;! &#8220;Machine&#8221; here refers to a computer in an automated library system.
MARC is, as a mainstream, the format used to create cataloging records for libraries&#8217; online catalog.
The two cataloging programs, Connexion and Millennium, we use to do cataloging job both handle the MARC format.

MARC anatomy

Each MARC record [...] ]]></description>
			<content:encoded><![CDATA[<p><strong>MARC in a nutshell</strong></p>
<ul>
<li>MARC stands for &#8220;MAchine Readable Cataloging&#8221;! &#8220;Machine&#8221; here refers to a computer in an automated library system.</li>
<li>MARC is, as a mainstream, the format used to create cataloging records for libraries&#8217; online catalog.</li>
<li>The two cataloging programs, Connexion and Millennium, we use to do cataloging job both handle the MARC format.</li>
</ul>
<p><strong>MARC anatomy</strong></p>
<ul>
<li>Each MARC record consists of many fields.</li>
<li>All the fields are divided into two big areas, namely, Fixed Field and Variable Field.</li>
<li>As a beginner, you only need to pay attention to some of them as shown in the following table.</li>
<li>Note: Do NOT attempt to remember all details of the fields &#8212; that will make you dizzy! In stead, try to have a whole picture of the fields and get familiar with those important ones gradually by your routine practice. Just as a shepherd may not be able to tell you the exact number of sheep he has, but he can notice immediately if one of them is missing! So does a cataloger can tell something is wrong in a MARC record by just taking a look at it.</li>
</ul>
<p>Let&#8217;s first take a look at some of the variable fields in a MARC record.</p>
<table width="”80%”" border="”1″">
<caption align="”left”">Basic MARC Variable Fields</caption>
<tr>
<td>100 or 700 field(s)</td>
<td>Personal name of responsibily</td>
</tr>
<tr>
<td>245 field</td>
<td>Title and statement of responsibility</td>
</tr>
</table>
<blockquote><p>&nbsp;</p></blockquote>
<p>Now, what do we need to know about those Fixed Fields?<br />
&#8211; <em>The Fixed Fields concern questions including what cataloging rule we follow when we create a bibliographic record, what level of record we are creating, when the entity is published, what the language of the publication is and what country the publishing agent belongs to? etc.</em></p>
<table width="”80%”" border="”1″">
<caption align="”left”">Basic MARC Fixed Fields</caption>
<tr>
<td>Type</td>
<td>Format of the entity we are describing</td>
</tr>
<tr>
<td>BLvl</td>
<td>Is the entity a monograph or serial?</td>
</tr>
<tr>
<td>Desc</td>
<td>Cataloging rule (we always use &#8220;a&#8221;)</td>
</tr>
<tr>
<td>DtSt</td>
<td>Is this entity published in one time?</td>
</tr>
<tr>
<td>Dates</td>
<td>When is it published?</td>
</tr>
<tr>
<td>Lang</td>
<td>What is the language of the publication</td>
</tr>
<tr>
<td>Ctry</td>
<td>What country does the publishing agent belongs to?</td>
</tr>
</table>
<blockquote><p>&nbsp;</p></blockquote>
<p><strong>Punctuations in MARC</strong></p>
<p><strong>More MARC fields to get familiar with</strong></p>
<p><strong>Co-relation between variable fields and fixed fields</strong></p>
<p><strong>Usage of the 246 field</strong><br />
1. &#8220;Use field 246 if a title differs substantially from the title statement in field 245 and if it contributes to further identification of the item. Also use field 246 for tracing a portion of the title.&#8221; (OCLC MARC Field Help)<br />
2. When to add a 246 field?</p>
<p>The following examples may illustrate the practice:</p>
<p>In cases when the second part of the title does not have any significant meaning, do NOT add 246 for it<br />
Zang Ao: zhong jie ban 藏獒：终结版<br />
Wu zhe: huo juan 舞者：火卷<br />
Wu zhe: bing juan 舞者：冰卷</p>
<p>In cases when the subtitle or part of the title conveys significant meaning, add a 246 field for it<br />
Cheng shi ji feng : Beijing he Shanghai de wen hua jing shen 城市季风：北京和上海的文化精神</p>
 ]]></content:encoded>
			<wfw:commentRss>http://library.osu.edu/blogs/nonromancat/2008/08/06/marc-in-practice/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Treatment for Serials Title Change</title>
		<link>http://library.osu.edu/blogs/nonromancat/2008/05/23/treatment-for-serials-title-change/</link>
		<comments>http://library.osu.edu/blogs/nonromancat/2008/05/23/treatment-for-serials-title-change/#comments</comments>
		<pubDate>Fri, 23 May 2008 18:43:50 +0000</pubDate>
		<dc:creator>Sherab Chen</dc:creator>
		
		<category><![CDATA[special formats - serials]]></category>

		<guid isPermaLink="false">http://library.osu.edu/blogs/nonromancat/2008/05/23/treatment-for-serials-title-change/</guid>
		<description><![CDATA[Step 1. Revise the bib record for the old title

Change 008, i.e. change DsTs from c to d; supply the closing date in the 2nd Dates field.
Close 362: supply the closing date.
Examples:
362 0_ Vol. 1 no. 1 (Nov. 1943) -v. 10 no. 12 (June 1953)
┌362 0_ 創刊號 (summer 1969)-
└362 0_ Chuang kan hao (summer 1969)-
362 [...] ]]></description>
			<content:encoded><![CDATA[<p><strong>Step 1.</strong> Revise the bib record for the old title</p>
<ul>
<li>Change 008, i.e. change DsTs from c to d; supply the closing date in the 2nd Dates field.</li>
<li>Close 362: supply the closing date.<br />
<blockquote><p>Examples:</p>
<li>362 0_ Vol. 1 no. 1 (Nov. 1943) -v. 10 no. 12 (June 1953)</li>
<li>┌362 0_ 創刊號 (summer 1969)-<br />
└362 0_ Chuang kan hao (summer 1969)-</li>
<li>362 1_ Ceased with autumn 2003 issue. etc.</li>
</blockquote>
<li>Add 785 field (Succeeding Entry), and 580 (Linking Entry-complex) if needed<br />
<blockquote>
<li>If continued by a new title<br />
785 00 $t (the new title). $x (ISSN of new title) $w (OCoLC)nnnnnnnn</li>
<li>If continued in part by a new title<br />
785 01 $t (the new title). $x (ISSN of new title) $w (OCoLC)nnnnnnnn</li>
<li>If the title is split into 2 or more entities, add a 580 and several 785 fields<br />
580 Split into: title1; title2; title3.<br />
785 16 (for each split title)</li>
</blockquote>
<li>Set OSUL Call number and/or other local info.</li>
<li>Update holdings and Export to overlay the OSCAR bib.</li>
</ul>
<p><strong>Step 2.</strong> Prepare the bib record for the new title</p>
<ul>
<li>Find or create a bib record for the new title on OCLC Connexion.</li>
<li>Make sure the record supplies a OSUL&#8217;s Call number.</li>
<li>Add 780 field (Preceding Entry or &#8220;Information about the immediate predecessor of the target item in a chronological relationship&#8221;):<br />
<blockquote>
<li>If continues an old title<br />
780 00 $t (previous title). $x (ISSN of previous title) $w (OCoLC)nnnnnnnn</li>
<li>If continues in part an old title<br />
780 01 $t (previous title). $x (ISSN of previous title) $w (OCoLC)nnnnnnnn</li>
</blockquote>
<li>Update holdings on OCLC, export/bring in the record into OSCAR.</li>
</ul>
<p><strong>Step 3.</strong> Notify the Serial Dept when complete, so they can fix the rest problems, such as add items, or transfer items to new title record, etc.</p>
<p><strong>Closing out a serial title that is continued by a new title etc.</strong><br />
On the old bib record, add 362 0_ for publication history, and add 785 00 $t (new title) $w (DLC) #### $w (OcoLC)nnnnnnnn.</p>
 ]]></content:encoded>
			<wfw:commentRss>http://library.osu.edu/blogs/nonromancat/2008/05/23/treatment-for-serials-title-change/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Cataloging Video recordings (DVDs, video cassettes etc.)</title>
		<link>http://library.osu.edu/blogs/nonromancat/2008/05/20/cataloging-video-recordings-dvds-video-cassettes-etc/</link>
		<comments>http://library.osu.edu/blogs/nonromancat/2008/05/20/cataloging-video-recordings-dvds-video-cassettes-etc/#comments</comments>
		<pubDate>Tue, 20 May 2008 16:57:37 +0000</pubDate>
		<dc:creator>Sherab Chen</dc:creator>
		
		<category><![CDATA[special formats - video recording]]></category>

		<guid isPermaLink="false">http://library.osu.edu/blogs/nonromancat/2008/05/20/cataloging-video-recordings-dvds-video-cassettes-etc/</guid>
		<description><![CDATA[I. DVD(s) &#8212; If the item you are dealing with is in the format of DVD
Examples
The Mission directed by Roland Joffe released as DVD movies
I.1. Preparing the bib record on OCLC Connexion

Use the form for &#8220;Visual Materials.&#8221; If start from scratch, [Menu] Cataloging - Create - Single Record - Visual Materials.

Fixed fields

The code in Type [...] ]]></description>
			<content:encoded><![CDATA[<p><strong>I. DVD(s) &#8212; If the item you are dealing with is in the format of DVD</strong></p>
<p>Examples</p>
<blockquote><p>The Mission directed by Roland Joffe released as DVD movies</p></blockquote>
<p>I.1. Preparing the bib record on OCLC Connexion</p>
<ul>
<li>Use the form for &#8220;Visual Materials.&#8221; If start from scratch, [Menu] Cataloging - Create - Single Record - Visual Materials.</li>
</ul>
<p><em>Fixed fields</em></p>
<ul>
<li>The code in Type is &#8220;g&#8221; (this corresponds to Millennium MAT TYPE g AUDIOVISUALS)</li>
<li>The code in BLvl is &#8220;m&#8221; for &#8220;monographs&#8221;</li>
<li>The code in TMat (type of material) is &#8220;v&#8221; (v = videorecording)</li>
<li>Fill out the rest fixed fields accordingly. If the running time is not available, put &#8220;&#8212;&#8221; in Time</li>
</ul>
<p><em>special treatments in Variable fields</em></p>
<ul>
<li>Add a 007 field (see example and check OCLC bib standard)</li>
<li>Use a 024 field to code Other Standard Identifier such as the ISRC (International Standard Recording Code) or CNG number (on Chinese DVDs)</li>
<li>Add the $h [videorecording] subfield immediately after the main title.</li>
<li>Describe number of DVDs, running time, and other characters of the item in the 300 field. It usually looks like this:<br />
300 __ 2 videodiscs (125 min.) : $b sd., col. ; $c 4 3/4 in.</li>
<li>Provide system requirements info in a 538 field.</li>
<li>Use the 511 field to provide names of participants or performers (1st indicator 1 for cast etc.)</li>
<li>Use the 508 field (usually follows 511) to provide names of credits such as film editor, director, music, photographer, producers, etc.</li>
</ul>
<p><em>Call number suffix &#8212; a local Call number treatment</em></p>
<ul>
<li>Add &#8220;DVD&#8221; to the end of the call number as an OSUL local practice. See Special Practices of Call Number in OSUL Cataloging for detailed information.</li>
</ul>
<p>►Click on the following links to see an example of MARC record for DVD movies (OCLC#52283425):</p>
<blockquote><p><a href="http://farm4.static.flickr.com/3229/2508353937_13e2ac870c_o.gif">part 1</a><br />
<a href="http://farm4.static.flickr.com/3028/2508353947_ee193be40f_o.gif">part 2</a><br />
<a href="http://farm4.static.flickr.com/3201/2509182354_fa10d4f05d_o.gif">part 3</a></p></blockquote>
<p>I.2. Preparing the bib and item record for OPAC (OSUL catalog)</p>
<p><em>Using Constant Data on Connexion</em></p>
<ul>
<li>949 _0 field: The location code in $l varies (e.g. &#8220;tho&#8221; for SUL DVD collection). The code for $m (MAT TYPE) is &#8220;g&#8221; (for Audiovisual).</li>
<li>949 _1 field: The detailed location code in $l varies (e.g. &#8220;thov3&#8243; for English DVDs to be shelved at SUL; &#8220;thov4&#8243; for Foreign DVDs to be shelved at SUL). The code in $t usually is &#8220;3&#8243; or &#8220;21&#8243; (this coresponds to the ITYPE field on the Millennium Item record. &#8220;3&#8243; is for audiovisual materials circulated for OSUL. &#8220;21&#8243; for audiovisuals circulated for OhioLINK).</li>
</ul>
<p>►Click <a href="http://farm4.static.flickr.com/3046/2508543481_9c4aba69d5_o.gif">here</a> to see <a href="http://farm4.static.flickr.com/3046/2508543481_9c4aba69d5_o.gif">an example of Constant Data for DVDs</a>.</p>
<p><em>Treatments on Millennium Item record</em></p>
<ul>
<li>Pay particular attention to the ITYPE and LOCATION fields. Use codes as mentioned above.</li>
<li>If there are multiple parts (more than one disc or with supplementaries), we may code &#8220;p&#8221; in the MESSAGE field to reimind the Circulation Desk to check for parts at time of checking in and out.</li>
</ul>
<p>►Click on the following to see examples of bib and item records on Millennium:</p>
<blockquote><p><a href="http://farm3.static.flickr.com/2267/2509182366_ebed597e8c_o.gif">bib record</a><br />
<a href="http://farm4.static.flickr.com/3278/2509371674_3224ca9b63_o.gif">item record</a></p></blockquote>
<p><strong>II. VHS &#8212; If the item you are dealing with is in the format of VHS video cassette</strong></p>
<p><strong>III. Combinations &#8212; If the item you&#8217;re dealing wiht is a mixture of DVD, audio tape, etc&#8230;</strong></p>
<p>First, decide what is the chief character of the item, if the major part of the entity is DVD video, catalog it as DVD videos; If the entity functions more as a software or computer file, catalog it as computer files.</p>
<p>Examples</p>
<blockquote><p>A Japanese item consists of 1 computer file, 1 DVD, and a user guide, which is cataloged as Computer files:<br />
<a href="http://farm4.static.flickr.com/3079/2508729045_36f107aac2_o.gif">Connexion bib record part 1</a><br />
<a href="http://farm4.static.flickr.com/3057/2508729051_0f00d307a4_o.gif">Connexion bib record part 2</a><br />
<a href="http://farm3.static.flickr.com/2162/2508729063_053be929a4_o.gif">Millennium bib record</a><br />
<a href="http://farm3.static.flickr.com/2016/2509557332_9cc333cd35_o.gif">Millennium item record</a></p></blockquote>
 ]]></content:encoded>
			<wfw:commentRss>http://library.osu.edu/blogs/nonromancat/2008/05/20/cataloging-video-recordings-dvds-video-cassettes-etc/feed/</wfw:commentRss>
		</item>
		<item>
		<title>How to catalog a translation</title>
		<link>http://library.osu.edu/blogs/nonromancat/2008/05/06/how-to-catalog-a-translation/</link>
		<comments>http://library.osu.edu/blogs/nonromancat/2008/05/06/how-to-catalog-a-translation/#comments</comments>
		<pubDate>Tue, 06 May 2008 18:49:59 +0000</pubDate>
		<dc:creator>Sherab Chen</dc:creator>
		
		<category><![CDATA[special formats - translations]]></category>

		<guid isPermaLink="false">http://library.osu.edu/blogs/nonromancat/2008/05/06/how-to-catalog-a-translation/</guid>
		<description><![CDATA[Step 1. Determine if the work is a translation
Examples of translations:

《資本論》Zi ben lun (a Chinese translation of Karl Marx&#8217;s Kapital)
Dream of the red chamber (an English translation of 《紅樓夢》 Hong lou meng)

Step 2. Look for the bibliographic record made for the original
It will be helpful if we know more about the orginal work, such as [...] ]]></description>
			<content:encoded><![CDATA[<p><strong>Step 1. Determine if the work is a translation</strong></p>
<p>Examples of translations:</p>
<ul>
<li>《資本論》Zi ben lun (a Chinese translation of Karl Marx&#8217;s Kapital)</li>
<li>Dream of the red chamber (an English translation of 《紅樓夢》 Hong lou meng)</li>
</ul>
<p><strong>Step 2. Look for the bibliographic record made for the original</strong></p>
<p>It will be helpful if we know more about the orginal work, such as title and author name in their original language and the call number assigned to the original. A bib record made for the original will do.</p>
<p><strong>Step 3. Prepare the the bibliographic record for the translation</strong></p>
<p>1. SPECIAL MARC FIELDS</p>
<p>1.a. The Lang in Fixed fields</p>
<ul>
<li>The Lang should be the languae of the translation</li>
</ul>
<p>1.b. Using the 041 field</p>
<ul>
<li>The 041 field is a language code field, and can be used for item that is or contains a translation:<br />
041 1_ language of the translation text $h language of the original and/or the intermediate text</li>
</ul>
<p>1.c. Treatment of title</p>
<ul>
<li>Transcribe the translation title in the 245 field</li>
<li>Give the title in original language (if we know) in either 240 or 130 field</li>
<blockquote><li>Use 240 field if there is an author main entry (i.e. 100 field)</li>
<li>Use 130 if there is no author main entry</li>
<li>If the original title is not available, omit this step.</li>
</blockquote>
<li>Optionally, provide a 500 note like this:<br />
500 __ Translation of: xxxxx.</li>
</ul>
<p>1.d. Other treatments</p>
<ul>
<li>If there is colophon or CIP page in the language of the translation, we can give a 546 field like this;<br />
Colophon title page in Chinese</li>
</ul>
<p>2. ASSIGNING LC CALL NUMBER FOR THE TRANSLATION</p>
<p>Generally, the call number for a translation will be the call number assigned for the original plus a language cutter. Use the Translation Table to determine the cutter number.</p>
<p><strong>Examples of records made for translations</strong></p>
<p>#56519602 - A Chinese translation of a English classic (Huxley&#8217;s Evolution and ethics)<br />
#227068880 - An English translation of a Chinese work but with colophon in Chinese</p>
 ]]></content:encoded>
			<wfw:commentRss>http://library.osu.edu/blogs/nonromancat/2008/05/06/how-to-catalog-a-translation/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Translation LC Cutter Table</title>
		<link>http://library.osu.edu/blogs/nonromancat/2008/05/05/translation-lc-cutter-table/</link>
		<comments>http://library.osu.edu/blogs/nonromancat/2008/05/05/translation-lc-cutter-table/#comments</comments>
		<pubDate>Mon, 05 May 2008 21:09:20 +0000</pubDate>
		<dc:creator>Sherab Chen</dc:creator>
		
		<category><![CDATA[tools &amp; resources]]></category>

		<guid isPermaLink="false">http://library.osu.edu/blogs/nonromancat/2008/05/19/translation-lc-cutter-table/</guid>
		<description><![CDATA[The OSU Libraries Cataloging Department adopts the LC Cutter Table for translations. However, only a limited number of Western languages are being listed on the table. Languages that are not in the table are given extensions consistent with the table so that the alphabetical language subarrangement is preserved. The Cutter numbers for Chinese, Japanese and [...] ]]></description>
			<content:encoded><![CDATA[<p>The OSU Libraries Cataloging Department adopts the LC Cutter Table for translations. However, only a limited number of Western languages are being listed on the table. Languages that are not in the table are given extensions consistent with the table so that the alphabetical language subarrangement is preserved. The Cutter numbers for Chinese, Japanese and Korean in the following table are tentative &#8212;</p>
<table width="65%" border="1">
<tr>
<td>.x</td>
<td>Original work</td>
</tr>
<tr>
<td>?</td>
<td>Arabic translation</td>
</tr>
<tr>
<td>.x12</td>
<td>Polyglot*</td>
</tr>
<tr>
<td>.x126</td>
<td>Chinese translation</td>
</tr>
<tr>
<td>.x13</td>
<td>English translation</td>
</tr>
<tr>
<td>.x14</td>
<td>French translation</td>
</tr>
<tr>
<td>.x15</td>
<td>German translation</td>
</tr>
<tr>
<td>?</td>
<td>Hebrew translation</td>
</tr>
<tr>
<td>.x16</td>
<td>Italian translation</td>
</tr>
<tr>
<td>.x163</td>
<td>Japanese translation</td>
</tr>
<tr>
<td>.x165</td>
<td>Korean translation</td>
</tr>
<tr>
<td>.x17</td>
<td>Russian translation</td>
</tr>
<tr>
<td>?</td>
<td>Persian translation</td>
</tr>
<tr>
<td>.x18</td>
<td>Spanish translation</td>
</tr>
<tr>
<td>?</td>
<td>Turkish translation</td>
</tr>
<tr>
<td>?</td>
<td>Yiddish translation</td>
</tr>
</table>
<p>* The Cutter for Polyglot is assigned when a work is written in several languages.</p>
<p>REFERENCES</p>
<ul>
<li><a href="http://digitalarchive.oclc.org/da/ViewObject.jsp?objid=0000003964">Cuttering for the Library of Congress Classification</a></li>
<li>OSUL TechServ Doc &#8212; <a href="http://library.osu.edu/sites/cataloging/cutter2.php">Adjusting Cutter Numbers: Executive Summary Draft ( JANUARY 11, 1995)</a></li>
<li>OSUL TechServ Doc &#8212; <a href="http://library.osu.edu/sites/cataloging/localpracticepolicy1.php">Decision on eliminating certain local practice</a></li>
</ul>
 ]]></content:encoded>
			<wfw:commentRss>http://library.osu.edu/blogs/nonromancat/2008/05/05/translation-lc-cutter-table/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Del.icio.us bookmarks for Non-Roman cataloging</title>
		<link>http://library.osu.edu/blogs/nonromancat/2008/04/23/delicious-bookmarks-for-non-roman-cataloging/</link>
		<comments>http://library.osu.edu/blogs/nonromancat/2008/04/23/delicious-bookmarks-for-non-roman-cataloging/#comments</comments>
		<pubDate>Wed, 23 Apr 2008 21:55:00 +0000</pubDate>
		<dc:creator>Sherab Chen</dc:creator>
		
		<category><![CDATA[tools &amp; resources]]></category>

		<category><![CDATA[► News - Events - Activities]]></category>

		<guid isPermaLink="false">http://library.osu.edu/blogs/nonromancat/2008/03/11/delicious-bookmarks-for-non-roman-cataloging/</guid>
		<description><![CDATA[Announcement
The Non-Roman Cataloging Section at the OSUL Cataloging Department now has a Del.icio.us account to gather bookmarks of useful online resouces and tools for non-Roman cataloging, which can be accessed from any computer workstation, as well as from your personal computer - any where and at any time!
http://del.icio.us/osul_nonroman_cat
More about this tool

What? This is a new [...] ]]></description>
			<content:encoded><![CDATA[<p><strong>Announcement</strong></p>
<p>The Non-Roman Cataloging Section at the OSUL Cataloging Department now has a Del.icio.us account to gather bookmarks of useful online resouces and tools for non-Roman cataloging, which can be accessed from any computer workstation, as well as from your personal computer - any where and at any time!</p>
<p><a href="http://del.icio.us/osul_nonroman_cat">http://del.icio.us/osul_nonroman_cat</a></p>
<p><strong>More about this tool</strong></p>
<ul>
<li><strong>What?</strong> This is a new tool we created on &#8220;Del.icio.us.&#8221; Del.icio.us is one of the new trendy web tools in the category of &#8220;social bookmarking&#8221;. Have you ever felt troublesome to get back to a page you bookmarked on another computer? and your list of bookmarks or favorites is getting messier and messier with folders, sub-folders&#8230;? Del.icio.us promises to help on this, and with it you can</li>
<blockquote><li>Store your bookmarks online</li>
<li>Access the same bookmarks from any computer
<li>Add bookmarks from anywhere</li>
<li>Use tags to organize and remember your bookmarks, which is a much more flexible system than folders</li>
<li>Share your bookmarks with others, and watch whoelse is bookmarking the same thing you did!</blockquote>
<li><strong>Who?</strong> - We made this tool public for everyone who is interested in non-Roman cataloging. Staffers here at the Non-Roman Cataloging Section is encouraged to use this tool and help building up the collection.</li>
<li><strong>How?</strong></li>
<blockquote><li>Simply go the page if you just want to get to the list of bookmarks; Use tags to help navigate and find what you want;</li>
<li>Login and you can start capture any web resources (webpages, databases, online dictionaries, blogs, etc.) using the Del.icio.us TAG installed;</li>
<li>For consistancy, we&#8217;re developing a list of specific tags for non-Roman cataloging (forthcoming&#8230; stay tuned)</li>
</blockquote>
</ul>
<p>How to install the handy Del.icio.us TAG button?</p>
<blockquote><p>On <a href="http://del.icio.us/">Del.icio.us homepage</a>, click on &#8220;help&#8221; at the very upper right corner of the window,<br />
under &#8220;Bookmarking&#8221; &#8220;install the tools for saving bookmarks&#8221;, choose one according to the browser your computer is using (mostly, &#8220;internet explorer buttons&#8221;)<br />
then follow the install instructions</p></blockquote>
<p>Click on <a href="http://del.icio.us/about/">here</a> if you want to learn <a href="http://del.icio.us/about/">more about Del.icio.us</a>.</p>
<p><strong>GUIDELINES ON SELECTING, NAMING AND ORGANIZING BOOKMARKS</strong></p>
<p><em>Criteria for selection</em></p>
<ul>
<li>The site bears informative, useful and/or instrumental content related to library cataloging in general and non-roman cataloging in particular.</li>
<li>Content on the site can enhance cataloging activities and decision making, such as determination of author name form, date, subject headings, classification, publication information, etc.</li>
<li>Examples of categories include:</li>
<blockquote><li>Databases</li>
<li>Online dictionaries</li>
<li>Converting tools such as the <a href="http://www.mandarintools.com/pyconverter.html">Chinese Romanization Converter</a> by Mandarin Tools</li>
<li>Blogs</li>
<li>Online calendar</li>
<li>Articles of instruction, guideline, or description of cataloging procedures</blockquote>
</ul>
<p><em>Name it meanfully and efficiently</em></p>
<ul>
<li>Give a meaningful name of the site you bookmark.</li>
<li>Use the site&#8217;s own name if it is unique.</li>
<li>Make it unique if is not already. For instance, not &#8220;Chinese-English Online Dictionary&#8221; but &#8220;<em>Jinshan</em> Chinese-English Online Dictionary&#8221;. Because there maybe more than one Chinese-English dictionaries on our list!</li>
</ul>
<p><em>Tagging to organize</em></p>
<ul>
<li>use lower case. For examples, &#8220;databases&#8221; but not &#8220;Databases&#8221;; &#8220;databases-chinese&#8221; but not &#8220;databases-Chinese.&#8221;</p>
<li>1 word tag</li>
<blockquote><li>use plural form when you are tagging a bookmark that belongs to a category. For examples, tag it &#8220;blog&#8221; if it is one of the blogs we select.</li>
<li>use single when you tag a site that is on or about the subject. For example, tag it &#8220;blog&#8221; if it is a site about the blog technology.</li>
</blockquote>
<li>compound tag</li>
<blockquote><li>Use hyphen &#8220;-&#8221; or underscore &#8220;_&#8221; to bond words.</li>
<li>Put the generic word at the beginning of the string. For examples, &#8220;databases-japanese,&#8221; &#8220;history-korean.&#8221;</li>
<li>Del.icio.us has a feature called &#8220;related tags&#8221; that can reduce the use of compound tag.</blockquote>
<li>Multiple tags for the same bookmark</li>
<blockquote><li>One bookmark can have more than one tags. For examples, a site functions both as a blog and a researching resource for the blog technology can be tagged &#8220;blogs&#8221; and &#8220;blog.&#8221;</li>
<li>tag as many as you like, but be efficient!</li>
</blockquote>
</ul>
 ]]></content:encoded>
			<wfw:commentRss>http://library.osu.edu/blogs/nonromancat/2008/04/23/delicious-bookmarks-for-non-roman-cataloging/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Cataloging Microform</title>
		<link>http://library.osu.edu/blogs/nonromancat/2008/04/23/cataloging-microform/</link>
		<comments>http://library.osu.edu/blogs/nonromancat/2008/04/23/cataloging-microform/#comments</comments>
		<pubDate>Wed, 23 Apr 2008 21:06:56 +0000</pubDate>
		<dc:creator>Sherab Chen</dc:creator>
		
		<category><![CDATA[special formats - microforms]]></category>

		<guid isPermaLink="false">http://library.osu.edu/blogs/nonromancat/2008/04/23/cataloging-microform/</guid>
		<description><![CDATA[The term &#8220;microform&#8221; is used here referring to reproduction of printed materials (monographs or serials) in microform. There are two types of microform reproduction: microfilm and microfiche.

Microfilm is a reel of film on which printed materials are photographed at greatly reduced size; useful for storage. A magnification system, often called a microfilm reader, is used [...] ]]></description>
			<content:encoded><![CDATA[<p>The term &#8220;microform&#8221; is used here referring to reproduction of printed materials (monographs or serials) in microform. There are two types of microform reproduction: microfilm and microfiche.</p>
<ul>
<li>Microfilm is a reel of film on which printed materials are photographed at greatly reduced size; useful for storage. A magnification system, often called a microfilm reader, is used to read the material.</li>
<li>Microfiche is a small sheet of film, or fiche, on which many pages of material have been photographed. A magnification system, called microfiche reader, is used to read the material.</li>
</ul>
<p><strong>Special treatments in the bibliographic record</strong></p>
<p>1. When creating MARC records for microfom, use approperiate form as for the original. For example, if it is a microform reproduction of a monograph book, then use the Books form; if it is a reproduction of a serial, use the Continuing Resources form.</p>
<p>2. Set the fixed fields just as if we are cataloging the original, print material. This means that the Dates for example, should be the publishing date of the original.</p>
<p>3. Add 007 field to code the physical characteristics of the microform as follows,</p>
<blockquote><p>007 __ h ǂb d ǂd a ǂe f ǂf b&#8212; ǂg b ǂh u ǂi c ǂj u</p></blockquote>
<p>4. In the 245 field, add ǂh [microform] righ after the main title</p>
<blockquote><p>┌245 00 光明日報 ǂh [microform] = ǂb Guangming ribao.<br />
└245 00 Guang ming ri bao ǂh [microform] = ǂb Guangming ribao.</p>
<p>┌245 00 文學 ǂh [microform] / ǂc 江蘇師範學院圖書館文學社編輯.<br />
└245 00 Wen Xue ǂh [microform] / ǂc Jiangsu shi fan xue yuan tu shu guan wen xue she bian ji.</p></blockquote>
<p>5. In the 300 field, describe the physical characters of the <strong>original, print version</strong>.</p>
<p>6. Use the <strong>533</strong> field to provide information about the microform reproduction. Please provide information in the following subfields. As for the record of microfiche, please provide the number of sheets of each item and length and width of the sheet in e subfield.</p>
<blockquote><p>ǂa Type of reproduction (NR)<br />
ǂb Place of reproduction (R)<br />
ǂc Agency responsible for reproduction (R)<br />
ǂd Date of reproduction (NR)<br />
ǂe Physical description of reproduction (NR)<br />
ǂf  Series statement of reproduction </p></blockquote>
<p>For microfiche, give the number of fiches of one item and the size of the fiche in the e subfield. For example,</p>
<blockquote><p>533 __ Microfiche. ǂb Zug, Switzerland : ǂc Inter-Documentation, ǂd [197-?]. ǂe 233 microfiches. 9 x 14 cm. ǂf (CH-363).</p></blockquote>
<p>For microfilm, give the number of reels (if known, otherwise &#8220;microfilm reels&#8221;) and the size of the microfilm in the e subfield. For example,</p>
<blockquote><p>533 __ Microfilm. ǂb Beijing : ǂc China National Microforms Import &amp; Export Corp. ǂe microfilm reels ; 35 mm.</p></blockquote>
<p>7. Add a 776 field if we know that there is an OCLC record made for the original. For example,</p>
<blockquote><p>┌776 1_ ǂt 光明日报 ǂw (OCoLC)2263314<br />
└776 1_ ǂt Guang ming ri bao ǂw (OCoLC)2263314</p></blockquote>
<p><strong>Local treatment</strong></p>
<p>1. Constant data for microform</p>
<p>The 949 _0 field is the same as for the original. Pay particular attention to the following areas in the 949_1 field(s):</p>
<p>(1) The value of ǂt:</p>
<ul>
<li> &#8220;2&#8243; for microform items circulated in OSUL</li>
<li>&#8220;20&#8243; for OhioLink circulating microform items</li>
</ul>
<p>&#8211; Always ask when you are not sure!</p>
<p>Examples,</p>
<blockquote><p>949 _1 ǂc v. nn ǂh yyyy ǂg 1 ǂi ######## ǂj 0 ǂl stxm ǂs p ǂt 2 ǂx -<br />
** ǂt represents Millennium ITYPE, i.e., the format of the item.</p></blockquote>
<p>(2) Sometimes we indicate the items are microform in the ǂc subfield. For example,</p>
<blockquote><p>949 _1 ǂc 1933July-1937July(microfiche) ǂh yyyy ǂg 1 ǂi ######## ǂj 0 ǂl stxm ǂs p ǂt 2 ǂx -</p></blockquote>
<p>(3) ǂl is for detailed location where the microform items will be kept. Usually, it is &#8220;stxm&#8221; (microform collection stored at Book Depository). </p>
<p>2. How to add / edit item records for microform on Millennium</p>
<ul>
<li>Open the record for the microform item on Millennium, make sure that the MAT TYPE field on the bib is set approperiately, i.e., if it is a serial, the value should be &#8220;s&#8221; SERIAL/JOURNAL.</li>
<li>Add item records, and make sure to set the ITYPE field as &#8220;2&#8243; for Microform (or &#8220;20&#8243; for OhioLink circ microform).</li>
</ul>
<p><img src="http://farm4.static.flickr.com/3118/2437527478_df0d313363_o.jpg" alt="Millennium Item record for a microform reproduction of a serial" /></p>
 ]]></content:encoded>
			<wfw:commentRss>http://library.osu.edu/blogs/nonromancat/2008/04/23/cataloging-microform/feed/</wfw:commentRss>
		</item>
		<item>
		<title>E-learning Courseware for Basic Cataloging Procedures</title>
		<link>http://library.osu.edu/blogs/nonromancat/2008/03/12/e-learning-courseware-for-basic-cataloging-procedures/</link>
		<comments>http://library.osu.edu/blogs/nonromancat/2008/03/12/e-learning-courseware-for-basic-cataloging-procedures/#comments</comments>
		<pubDate>Wed, 12 Mar 2008 19:07:34 +0000</pubDate>
		<dc:creator>Sherab Chen</dc:creator>
		
		<category><![CDATA[► E-learning Cataloging]]></category>

		<guid isPermaLink="false">http://library.osu.edu/blogs/nonromancat/2008/03/12/e-learning-courseware-for-basic-cataloging-procedures/</guid>
		<description><![CDATA[The OSUL Cataloging Department is developing e-learning lessons for new staff and student workers. Up to this point, 5 lessons (in 7 flash movies) are posted on the department homepage for evaluation. Note, links to large flash movies.

Lesson 5 : Basic Copy Cataloging Procedures
 part 1
part 2
part 3

Lesson 4 : Connexion and &#8220;searching for a [...] ]]></description>
			<content:encoded><![CDATA[<p>The OSUL Cataloging Department is developing e-learning lessons for new staff and student workers. Up to this point, 5 lessons (in 7 flash movies) are posted on the department homepage for evaluation. Note, links to large flash movies.</p>
<ul>
<li>Lesson 5 : Basic Copy Cataloging Procedures</li>
<blockquote><li><a href="http://library.osu.edu/sites/cataloging/forms/lesson05a.php"> part 1</a></li>
<li><a href="http://library.osu.edu/sites/cataloging/forms/lesson05b.php">part 2</a></li>
<li><a href="http://library.osu.edu/sites/cataloging/forms/lesson05c.php">part 3</a></li>
</blockquote>
<li>Lesson 4 : <a href="http://library.osu.edu/sites/cataloging/forms/lesson04.htm">Connexion and &#8220;searching for a matching bibliographic record&#8221;</a></li>
<li>Lesson 3 : <a href="http://library.osu.edu/sites/cataloging/forms/lesson03.htm">The Millennium cataloging interface</a></li>
<li>Lesson 2 : <a href="http://library.osu.edu/sites/cataloging/forms/lesson02.htm">What is cataloging and how we do it?</a></li>
<li>Lesson 1 : <a href="http://library.osu.edu/sites/cataloging/forms/lesson01.htm">Library catalog and bibliographic records</a></li>
</ul>
<p>Full text of voice-over instruction is available at our <a href="http://ecbchandouts.blogspot.com/">project blog</a>.</p>
<p><strong>Your comments are mostly welcome!</strong> Please email your comments to</p>
<p><a href="mailto:xsherabchen@hotmail.com">Sherab Chen</a> (Email: xsherabchen@hotmail.com)<br />
Principle Investigator<br />
E-learning Courseware for Basic Cataloging Project<br />
OSUL Cataloging Department</p>
 ]]></content:encoded>
			<wfw:commentRss>http://library.osu.edu/blogs/nonromancat/2008/03/12/e-learning-courseware-for-basic-cataloging-procedures/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
 