CUL Technical Services Manual, Copy Holdings Records/Edit/Examples

Copy Holdings Records/Edit/Examples

Table of Contents | Reference Level | Instruction Level

EDITING A COPY HOLDINGS RECORD

Example Level

Example of a Blank Copy Holdings Record:

On the blank copy holdings screen, the system prompts "LTCU DONE" on the command line. As will be seen below, "same" can be typed over "DONE" on the command line.

The record ID assigned to the bibliographic record and the copy holdings record displays to the right on the command line.

"LBB0", which appears following "NOTIS COPY HOLDINGS" on the blank copy holdings screen, is the line number that the terminal is using to connect to the mainframe and the NOTIS system. If there are any problems with the terminal or the line, record this line number to report to Systems Office staff.

"CU", on the next line, is the institution ID for the LTCU file. "BOOK" is the display of the format of the bibliographic record. "LC" contains a display of the Library of Congress control number from the bibliographic 010 field. "ISBN" contains a display of the ISBN from the bibliographic record 020 field.

Bibliographic information is displayed in the copy holdings record, but cannot be changed on the copy holdings record.

The main entry, title, edition statement, imprint, and series note fields are displayed from the bibliographic record. Check the display of the bibliographic title at the top of the copy holdings screen to be sure there are no large gaps. If there are gaps, edit the bibliographic record to remove the blanks at the end of the lines within the field. Redisplay the copy holdings screen and continue with the copy holdings editing process.

Up to 7 blank copy holdings statements (numbered 001 through 007) display on the blank copy holdings screen. The number of copy holdings statements that display depends on the length of the bibliographic information at the top of the copy holdings screen.

Title-level notes (NOTES)/Examples

Example of revisions:

Replacing original revisers' initials:

Searching information:

Record deletion information:

Multi-part microforms/Example If a microfilm is complete on 3 reels, the copy status code should be "3" and the classification type code should be "T". For example:

Basic Call number examples

Non-CTS-style call numbers:

CTS-style call numbers:

Location/sublocation code (|a)/Example

Typing:

Results in the following:

Added copy/Example

Oversize symbol (|k)/Example

See the Oversize chart for guidelines.

Call number (|b and |c)/Examples

Non-CTS-style call number:

CTS-style call number:

Non-CTS libraries will use a semicolon before the decimal of the first cutter only if the "b" subfield contains more than 12 characters. For example:

If the "c" subfield contains more than 12 characters, insert semicolons as necessary. For example:

A skeletal call number with one cutter is typed with three spaces between the class number and the |c subfield. Note that one of the spaces is "eaten" by the delimiter-subfield code pair. For example:

A skeletal call number with two cutters is typed with two spaces between the class number and the decimal before the first cutter. For example:

A call number consisting of only a class number and a date is typed with two spaces before the |c subfield. For example:

The proper location for microforms for Olin, is "olin,micr" and the proper call number is "|b Film;". All other locations with approved "micr" sublocs, should be used when appropriate. The name of the loc is not repeated in the "b" subfield:

"Oversize" is included as part of the location, whenever a sublocation has been defined (e.g., "olin,ove1", "jgsm,over", "olin,rov2", etc.). Also type the plusses or other oversize indication in a |k subfield in the copy holdings statement. The |k subfield is typed between the location and the call number. For example:

On the item in hand, write the location and oversize symbol above the call number. For example:

 
Olin				    
++					     
PS					    
3556				 
A13					 
R3

 
Fine
#					     
 NA
680
J55

Call number stripped of diacritics:

Long call numbers/Examples

Multi-volume works:

and the related MHLD:

Here is an example of a card reference:

Guide card under no. 56 and following numbers:

 
					OLIN
					AS
					286		      see		OLIN
					O6				             AS
					V35				           286
					no.56			           O6
									                 V35
									                 no.38,etc.

Here is an example of an online guide record:

NAC Classification

Enter existing NAC call numbers as follows:

Modifying an Existing Copy Holdings Statement/Examples

As loaded into NOTIS:

As changed:

Fixing RLIN load problems:

RLIN holdings screen:

Loaded into NOTIS as:

Copy holdings record:

MARC holdings record:

Change the copy holdings record to:

Change the MARC holdings record to:

Transfers

Original copy holdings statement:

Change copy holdings statement for the transferred item:

By using the same copy holdings statement, any linked item records and order/pay/receipt records will remain linked to the new location, and do not require deletion, cancellation, or relinking.

Items ordered and/or received on NOTIS may have a two- or three-digit number in the NOTES field of the copy holdings record. This is the statistics code for CTS staff.

Do not delete "gift", "exch", "reg", "dep", or similar information from the copy-level NOTES field of the copy holdings record.

Do not delete statistical codes from this area unless the date in the |d subfield is from a month previous to the current month.

Remove any indication of parts received in a multipart item when a MARC holdings record and/or item records are created. For example:

Deleting a Copy Holdings Statement Without Linked Item Records, MARC Holdings Records or Order/Pay/Receipt Records:

A copy holdings statement incorrectly added to the wrong copy holdings record can be deleted from the copy holdings record if no item record, MARC holdings record or order/pay/receipt record has been attached to the copy holdings statement. See Section V.A.7 if a copy holdings statement to be deleted has a MARC holdings record or an order/pay/receipt record attached.

To delete a copy holdings statement, use the following sequence:

  1. Type same over "DONE" or "MORE" on the command line.
  2. Press TAB to place the cursor on the copy status code of the copy holdings statement to be deleted.
  3. Press ERASE-EOF to erase the copy status code and the classification type code. Note that it is not necessary to delete the location, call number, or copy-level notes; the system automatically deletes the entire copy holdings statement when the copy status code and the classification type code are erased. Do not use the `xxx' loc, unless the online loc was never correct and there are MARC holdings records or order/pay/receipt records attached. Then use "xxx" for the location code, and see Section 7h below.
  4. Press ENTER with same on the command line to proofread the deletion. The system replaces the copy holdings statement with an "empty" copy holdings statement containing only copy status code "0" and classification type code "A".
  5. Press ENTER with done on the command line to update the copy holdings record in the data base.

Deleting a Copy Holdings Statement with Item Records, MARC Holdings Records, or Order/Pay/Receipt Records Attached:

A copy holdings statement cannot be physically deleted from the copy holdings record if item records, MARC holdings records, or order/pay/receipt records have been attached to the copy holdings statement. See Section V.A.6 if a copy holdings statement to be deleted does not have an item record, a MARC holdings record, or an order/pay/receipt record attached.

  1. Display the copy holdings record.
  2. If required, delete or relink any linked item records from the copy holdings statement. See Section VI.D for information on deleting an item record; see Section VI.C for information on relinking an item record.
  3. If required, delete any linked MARC holdings records from the copy holdings statement. See Section VII.D for information on deleting a MARC holdings record.
  4. Display the copy holdings record and type same over "DONE" or "MORE" on the command line.
  5. Press TAB to place the cursor on the copy status code of the copy holdings statement to be deleted.
  6. For single-piece titles, type over the copy status code with "0"; for multi-piece titles, type 2. For both, type over the classification type code with "Z".
  7. For copies with MARC holdings records or order/pay/receipt records, press ERASE-EOF to erase the call number (if any) from the statement.
  8. Leave the location code as it appears, unless the location never represented reality and yet there are order/pay/receipt records and/or MARC holdings records attached. In that case, use "xxx" for the location code. An `xxx' loc is the only way to block a copy statement on a cataloged record from output to RLIN via the Tape Out Program (T.O.P). NOTIS copy holdings statements that contain legitimate location codes write over the HOL screen in RLIN, so that the RLIN HOL screen reflects all the NOTIS copy holdings statements except the `xxx' ones. Uncataloged copy statements on cataloged records (cat stat "h") are sent out just as are cataloged statements.
  9. Press TAB to place the cursor on the copy statement date (|d subfield) and change the date to today's date.
  10. If there are copy-level notes with the copy holdings statement, press TAB to place the cursor on the first character of the copy-level notes field and press ERASE-EOF.
  11. Type the following note in the copy-level notes field: "Incorrect copy stmt. removed; [date]"
  12. Press ENTER with same on the command line to proofread the correction.
  13. Press ENTER with done on the command line to update the copy holdings record in the data base.

If you are removing an incorrect copy location from the first statement of a cataloged record, use the 0Z code but leave the incorrect location code in the subfield a. This information will upload and blank out the holdings on RLIN. This is especially important when it is the location in the first statement that is incorrect and needs to be deleted. If an `xxx' location were to occur in the first NOTIS copy holdings statement, the record would not be output to RLIN at all. This means that when we have `xxx'-ed a first copy statement in NOTIS, the RLIN record is out of sync with the NOTIS record. In order to keep NOTIS and RLIN in sync, we will have to leave location codes untouched in erroneous first copy statements.

Whenever staff encounters an `xxx' statement in "copy one" of a NOTIS record, they can do an RLIN search to determine what the NOTIS location code would have been, reinsert it, and let the record go out via T.O.P. Or they can fix the record manually in RLIN. In some cases, these problems can be avoided by re-using an incorrect first statement. An "xxx" loc in the first copy statement can be avoided and the statement re-used if 1) there is no MARC holdings record attached OR 2) an existing MARC holdings record can be re-used AND 3) there is no order/pay/receipt record.

For records that were cataloged or reconned in RLIN, the 035 of the NOTIS record must match the 001 of the RLIN record. For records cataloged or reconned in NOTIS, the NOTIS id number will be enough for the record to match against the correct RLIN counterpart.

For copies being withdrawn, as opposed to erroneous copy statements, please follow the withdrawals procedure.

DELETING A COPY HOLDINGS RECORD

NOTE: Because the copy holdings record is so closely linked to the bibliographic record, a copy holdings record cannot be deleted without also deleting the bibliographic record. See Deleting a Bibliographic Record for information on deleting a bibliographic record and the linked copy holdings record. Table of Contents | Reference Level | Instruction Level

Rev. 12/12/95 dih