01.05.2014 Views

faithful guide to each and every rule of ... - Oberlin College

faithful guide to each and every rule of ... - Oberlin College

faithful guide to each and every rule of ... - Oberlin College

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

OBERLIN LCRI CUMULATED 12-7<br />

rev. 12-10<br />

Modifying Pre-December 2002 Records for Updating Loose-leafs<br />

LC practice:<br />

The extent <strong>to</strong> which modifications due <strong>to</strong> changes should be made in records<br />

for updating loose-leafs created before LC’s implementation <strong>of</strong> the 2002 Revision <strong>of</strong> AACR2<br />

on Dec. 1, 2002, depends upon LC’s decision on filing updates in<strong>to</strong> those bibliographic<br />

resources.<br />

If LC doesn’t file updates <strong>and</strong> if the main entry <strong>and</strong>/or title proper changes<br />

on a current iteration, change the description <strong>and</strong> give a note <strong>and</strong> added entry for the<br />

earlier main entry <strong>and</strong>/or title proper. This modification <strong>of</strong> the bibliographic record is<br />

necessary <strong>to</strong> ensure identification <strong>of</strong> the resource in the future. If other data elements<br />

change, do not modify the bibliographic record.<br />

If LC does file updates, change the description <strong>to</strong> reflect the latest<br />

iteration according <strong>to</strong> the <strong>rule</strong>s in chapter 12. Give notes <strong>and</strong> added entries for changes<br />

if considered important. Insure that all name <strong>and</strong> series headings are in AACR2 form <strong>and</strong><br />

are represented by authority records. Change the record as appropriate <strong>to</strong> follow current<br />

MARC 21 practice.<br />

12.0A:CSB97<br />

Scope<br />

LC/PCC practice: See LCRI 1.0.<br />

12.0B1:CSB97<br />

Basis <strong>of</strong> the description<br />

First Issue<br />

The basis for the description is the first issue <strong>of</strong> the serial. In<br />

determining which issue is first, disregard the date <strong>of</strong> publication, etc., <strong>and</strong> use the<br />

designation on the issues. For serials that carry numeric or alphabetic designations,<br />

the first issue is the one with the lowest or earliest (in the alphabet) designation.<br />

For serials that do not carry numeric or alphabetic designations, the first issue is the<br />

one with the earliest chronological designation. (If the actual first issue is not<br />

available, use these same <strong>guide</strong>lines <strong>to</strong> determine which issue should be used as the basis<br />

for the description.)<br />

Serials may be issued with terms such as "premier," "sample," or "preview."<br />

The term "premier" generally implies the first true issue. Do not, however, base the<br />

description on an issue that bears only wording such as "Sample," "Preview," or<br />

"Introduc<strong>to</strong>ry issue." Such wording generally indicates that the publisher is testing the<br />

potential audience for the serial <strong>and</strong> it is possible that the serial may never be<br />

published. Such issues generally do not have numbering. An issue that bears numbering<br />

that precedes "1," such as "Vol. 1, no. 0," "No. 0," or "Vol. 0," may be treated as the<br />

first issue, provided that there is clear evidence that the issue is not merely serving<br />

as a sample or introduc<strong>to</strong>ry issue.<br />

LC practice: The National Serials Data Program (NSDP) creates records for<br />

sample issues in order <strong>to</strong> assign the ISSN. If LC later catalogs the serial, the<br />

description is based on the first "true" issue <strong>and</strong> a note is given <strong>to</strong> explain the sample<br />

issue.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!