Difference between revisions of "Step 6.13"
(→Step 6.13: Bibliographic Changes & Deletes) |
(→Step 6.13: Bibliographic Changes & Deletes) |
||
| Line 1: | Line 1: | ||
==Step 6.13: Bibliographic Changes & Deletes== | ==Step 6.13: Bibliographic Changes & Deletes== | ||
| − | [[Image:A6-13.jpg]]<br> | + | [[Image:A6-13.jpg]]<br><br> |
Sometimes you and your staff edit or weed Bibliographic records that were sent for processing previously. In either case, your MARS 2.0 Master Bibliographic File '''will not reflect these changes''' made locally by your staff. | Sometimes you and your staff edit or weed Bibliographic records that were sent for processing previously. In either case, your MARS 2.0 Master Bibliographic File '''will not reflect these changes''' made locally by your staff. | ||
Latest revision as of 09:05, 2 June 2022
Step 6.13: Bibliographic Changes & Deletes
Sometimes you and your staff edit or weed Bibliographic records that were sent for processing previously. In either case, your MARS 2.0 Master Bibliographic File will not reflect these changes made locally by your staff.
MARS 2.0 can apply the changes and deletes to your MARS 2.0 Master Bibliographic File. This will prevent redistribution of now obsolete bibliographic records that have been updated or deleted within your local catalog.
To have local changes and deletes applied to your MARS 2.0 Master Bibliographic File, you would need to provide Backstage with MARC files of changed Bibliographic records and either a TXT list of unique identifiers or a MARC file of records you have deleted from your system.
Note: MARS 2.0 also needs the files or lists submitted according to usage and type. For example, a file called deletes.d[mmyydd] instructs us to flag these bibs for deletion while changed.d[mmyydd] will overlay the existing copy of the bib with this version.
links
1.0 - 2.0 - 3.0 - 4.0 - 5.0 - 6.0
