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 [2015/05/13 18:36] 127.0.0.1 external edit |
910_formatting [2018/12/03 18:13] mbanach [910 Formatting] |
||
---|---|---|---|
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): |
- | recon | + | RECAT |
- | recat | + | PCATFIX |
- | pcatfix | + | REINSTATE |
- | reinstate | + | WITHDRAW |
- | withdraw | + | RUSH |
- | rush | + | SCUA |
- | scua | + | BATCHN |
+ | BATCHU | ||
+ | |||
+ | BATCHM | ||
+ | |||
+ | |||
+ | BATCHN stands for batch records newly added, BATCHU stands for batch records updated, and BATCHM stands for batch records merged. | ||
You can use up to three codes, and each should be separated by a single space. So it would look like this: | You can use up to three codes, and each should be separated by a single space. So it would look like this: | ||
Line 31: | Line 37: | ||
MBB 09/12/2014 code code code. | MBB 09/12/2014 code code code. | ||
- | The codes are not case sensitive. | + | The codes are case sensitive. |
Line 37: | Line 43: | ||
- | 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. | ||