Treatment of "644 n" Titles

Introduction

These guidelines outline procedures for making decisions on the appropriate treatment of "644 n" titles and documenting those decisions.  As used here, a "644 n" title is one formerly treated as a series that LC has decided no longer to analyze.

Each title should be dealt with on a case-by-case basis unless a particular bibliographer has definite opinions that apply to all titles in her or his area (in which case, you may apply those decisions and go straight to step C, "Update the authority record").

Note:  A list is available by the ":pdw" shelves of titles on the shelves as well as titles that have been removed from them.  If you come across a "644 n" title yourself, to avoid duplication of effort you should first check this list and/or check with Olga to make sure that no one else is currently working on the same title.

A.      Consult with bibliographer

Consult with the appropriate bibliographer to confirm her or his preference regarding the title:

1. Whether we should analyze as a series or follow LC's current practise and treat as a serial.

2. If the title should be treated as an analyzed series, whether it should be classified together (all in one call number) or separately (CNV).

If the bibliographer has definite preferences, follow those decisions and go on to step C., "Update the authority record."

B.       Decide appropriate treatment

If the bibliographer has no preferences, you may use judgment.

1. If you think that the title would be best handled as a serial:  Catalogue as a serial; go on to step C., "Update the authority record."

2. If you think that the title should be analyzed as a series:  Make a decision regarding classification.
   • Series titles already catalogued in TULANET (precedent in TULANET):
     • Pattern:  If there is a consistent pattern in TULANET, either of treating the series as classed together (an "all-in-one-call-number" series) or as classed separately (a CNV series), lean towards following the precedent unless you have definite reason to think that a different treatment would be preferable.

     • No pattern:  If there is no consistent pattern, note the inconsistencies and follow the provisions for new series as though there were no precedent.

   • New series (no precedent in TULANET):  Lean towards classing together, as an "all-in-one-call number" series, using LC's call number, unless you have definite reason to think that classifying each title separately would be preferable.

C.      Update the authority record

Document the decisions made for each title.  (Please note:  The examples below assume an existing TULAF record; however, you may need to edit an LCNAF printout if no TULAF record is available.)

1. Serial:
   • 644:  Add "|5 HT" to the existing 644 field:

     E.g.        644    |a n |5 DLC |5 HT

   • 667:  Add a 667 note, all in caps:

     NOT A SERIES: SERIAL

   • 690:

     When applicable:  In a 690 field, cite the decision to treat as a serial, together with the bibliographer's or your initials.   If useful, add specific information given in support of the decision.

     E.g.        690    |a HT serial, per GNF.

     E.g.        690    |a HT serial, per EE (engineers think of this title as a serial, anyway)

   • Other:  Add other information standard in series authority record editing.

2. Analyzed series:

   Record:

   Analysis decision

   Tracing practise

   Classification decision

   Local notes

   Other standard information

   • Decision to analyze:
     • Fixed field:  Change the "Type of series" fixed field element, as appropriate and necessary, to

       a      (monographic series)

             or

       b      (multi-part item)

     • 644:  Add a 644 field that indicates that we analyze the title.   (It should be the first 644 field.)  Use the following format:

       644/1    |a f |5 HT

   • Tracing decision (confirm or record):

     645:  If the record includes a 645 field coded "n" as not traced, add a 645 field that indicates that we trace the title.  (It should be the first 645 field.)  Use the following format:

     645/1    |a t |5 HT

   • Classification decision:

     Classed together

     Classed separately

     • Series classed together:
       • 050 or 090:  Make sure that the call number to be used is present in the authority record.
         • Call number present:  If the basic call number is present, but the number designation is not present, add the number designation, in a separate |a subfield.  If books in the series are always routed to a particular location other than stx, add the location code, as well, in another |a subfield.  A final |5 subfield should include the HT processing unit code.

           E.g.        050    |a F1411 |b .X37 |a no. |a lal |5 HT

         • Call number not present:  Add it in an 050 (LC call number) or 090 (local call number) field as appropriate, including all the information indicated immediately above.

       • 646:  Should be present with code "c" (classed collectively).   Add "|5 HT."

         E.g.        646    |a c |5 DLC |5 HT

       • 690:  When applicable:  In a 690 field, note any inconsistencies in our classification treatment of titles already catalogued in TULANET.

         E.g.       690    |a TUL includes 4 titles classed separately.

     • Series classed separately (CNV):
       • 050 or 090:  If a call number is present in an 050 or 090 field, add to it:

         |5 HT: DO NOT USE; CNV

       • 646:  Add a 646 field with code "s" (classed separately).  (It should be the first 646 field.)  Use the following format:

         646/1    |a s |5 HT

       • 690:  When applicable:  In a 690 field, note any inconsistencies in our classification treatment of titles already catalogued in TULANET.

         E.g.        690    |a TUL includes 2 titles classed in DLC's call no. (cf. 050).

   • 690:   Make local notes, when applicable:

     Cite the decision to analyze the series, as well as the classification decision, together with the bibliographer's initials.  If useful, add specific information that (s)he gave in support of the decision.

     E.g.        690    |a HT analyzed series, classed in 1 no., per MSK (researchers look for individual v. in this series, series not indexed in standard sources).

     If you yourself made the decision to analyze the series or to classify it a certain way, you may want to put information to support your decision in a local 690 note.

   • Other standard information:  Add other information standard in series authority record editing.  In particular, a 642 field may need to be added.

     E.g.        642    |a v. 4 |5 HT

     E.g.        642    |a 1992, no. 2 |5 HT

HTML document last reviewed:  12 July 1999