Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
910_formatting [2017/10/20 18:18] annk |
910_formatting [2018/12/03 18:04] jeustis |
||
|---|---|---|---|
| Line 10: | Line 10: | ||
| If there is an existing 910 in a catalog record (such as 910 fields for PROMPTCAT records) leave the existing 910 in the record as is and add a second 910 field with your initials and date or your initials and date followed by a space and then any other information you may need to add such as pcatfix, recon, or recat. | If there is an existing 910 in a catalog record (such as 910 fields for PROMPTCAT records) leave the existing 910 in the record as is and add a second 910 field with your initials and date or your initials and date followed by a space and then any other information you may need to add such as pcatfix, recon, or recat. | ||
| - | Use the following codes in the 910 fields: | + | Use the following codes in the 910 fields (listed here as lowercase but should be entered as UPPERCASE): |
| recat | recat | ||
| Line 23: | Line 23: | ||
| scua | scua | ||
| + | |||
| + | batchn (new) | ||
| + | |||
| + | batchu (update) | ||
| + | |||
| + | batchm (merge) | ||
| Line 35: | Line 41: | ||
| - | RECAT (add to 910): Cataloging-related changes done on an existing record for material already owned by UM. This will include overlaying a record in Aleph with a record from Connexion with the SAME OCLC number (already owned). | + | RECAT (add to 910): Cataloging-related changes done on an existing record for material already owned by UM. This will include overlaying a record in Aleph with a record from Connexion with the SAME OCLC number (already owned) |
| - | + | ||
| - | RECON (add to 910): Any work with requires pulling a new record from Connexion or creating an original record for material already owned by UM. | + | |
| - | - Mismatches: A record will already exist in Aleph, but it does not match the item. Either it will be overlaid with a matching record from Connexion with a DIFFERENT OCLC number, or (if none exist) replaced by an original record created by the Cataloger. | + | |
| - | + | ||
| - | - No hits: No record will exist in Aleph. Either a matching record needs to be downloaded from Connexion, or (if none exist), an original record created by the Cataloger. | + | |
| DATABASE MAINTENANCE (manually record these): Non-cataloging-related work done on a record. Examples: For monos—transfers, correction of HOLs or item lists. For serials—addition or correction of prediction patterns, X-links, cancellations, transfers, correction of HOLs or item lists. | DATABASE MAINTENANCE (manually record these): Non-cataloging-related work done on a record. Examples: For monos—transfers, correction of HOLs or item lists. For serials—addition or correction of prediction patterns, X-links, cancellations, transfers, correction of HOLs or item lists. | ||
