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 21-10<br />

rev. 11-07<br />

addition <strong>of</strong> the title in another language or script on a later issue would affect the<br />

choice <strong>of</strong> title proper if the description were based on that issue.<br />

For category b)vii), also consider the situation <strong>to</strong> apply when the language<br />

<strong>of</strong> the title varies according <strong>to</strong> the language <strong>of</strong> the text.<br />

For categories b)v) <strong>and</strong> b)vii), consider that there has been a major change<br />

if there is evidence that the publisher intentionally changed the title; such evidence<br />

may include, for example, a statement by the publisher or a new ISSN printed on the<br />

publication.<br />

terms.<br />

In applying category b)viii), consider that “a list” means at least three<br />

In applying category b)ix), note that the change from one word <strong>to</strong> another<br />

(e.g., the change from “magazine” <strong>to</strong> “journal”) is a major change. The word “series”<br />

does indicate a type <strong>of</strong> resource. A word denoting frequent (e.g., “monthly”) does not<br />

indicate a type <strong>of</strong> resource.<br />

Serials: Exceptions<br />

1) Session Laws <strong>of</strong> the U.S. States. LC/PCC practice: Consider all changes<br />

in the title proper <strong>to</strong> be minor changes <strong>and</strong> do not create new entries (cf. LCRI 25.15A1).<br />

2) 17th-19th Century U.S. almanacs. LC practice: Generally, consider all<br />

changes in the title proper <strong>to</strong> be minor changes <strong>and</strong> do not create new entries.<br />

21.3A2:CSB113<br />

Changes <strong>of</strong> persons or bodies responsible for a work. Monographs<br />

Change in LC/PCC policy: There should be only one record for an unnumbered<br />

multipart item. Prior <strong>to</strong> Dec. 1, 2002, separate series authority records were made for<br />

an unnumbered multipart item when the responsible person or body changed; do not change<br />

or condense any records created before Dec. 1, 2002. (The LC/PCC policy has always been<br />

<strong>to</strong> have only one record for a numbered multipart item when the responsible person or body<br />

changed.)<br />

LC/PCC practice: Follow <strong>rule</strong> 1.0A2 <strong>and</strong> always use the first part if<br />

possible as the basis <strong>of</strong> the description for the collected set bibliographic record. PCC<br />

practice: The same <strong>guide</strong>line applies <strong>to</strong> the heading in the series authority record. If<br />

that is not possible, use the first part that is available; in the collected set<br />

bibliographic record, make a "Description based on" note (see <strong>rule</strong> 1.7B23 <strong>and</strong> its LCRI).<br />

21.3B:CSB101<br />

Changes <strong>of</strong> persons or bodies responsible for a work. Serials <strong>and</strong><br />

integrating resources<br />

Remote Access Electronic Resources<br />

Original URI (Uniform Resource Identifier) is still active but the original<br />

resource is no longer available. If the resource located at the URI represents a<br />

completely different resource from that described in the bibliographic record (i.e., for<br />

an integrating resource, not just a subsequent iteration <strong>of</strong> that resource), make a new<br />

entry for the new resource now at the original URI. LC practice: See LCRI 9.7B for<br />

<strong>guide</strong>lines about updating the bibliographic record for the original resource.

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

Saved successfully!

Ooh no, something went wrong!