Difference between revisions of "Step 6.13"

From AC Wiki
Jump to: navigation, search
(Created page with "==Step 6.13: Library Adds & Deletes== Image:a6-5.png<br><br> Sometimes you and your staff download individual authority records related to a bibliographic record in your c...")
 
(Step 6.13: Library Adds & Deletes)
Line 1: Line 1:
==Step 6.13: Library Adds & Deletes==
+
==Step 6.13: Bibliographic Changes & Deletes==
[[Image:a6-5.png]]<br><br>
+
[[Image:a6-13.png]]<br><br>
Sometimes you and your staff download individual authority records related to a bibliographic record in your catalog. You may also remove records from your local authority file for headings that are no longer present in your catalog. In either case, your MARS 2.0 Master Authority 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.
  
MARS 2.0 can apply the adds and deletes to your MARS 2.0 Master Authority File. This will prevent distribution of authority records that have already been loaded into a local authority file and, more importantly, will provide you with any future updates to the records that have been loaded locally.
+
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.
  
Removing authority records that have been removed from your local authority file from the MARS 2.0 Master Authority File prevents MARS 2.0 from distributing an update to a record that is no longer present in your authority file.
+
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.
  
To have local adds and deletes applied to your MARS 2.0 Master Authority File, you would need to provide Backstage with files of added and/or deleted authority records or the LC number corresponding to the authority record.
+
'''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.
 
+
'''Note''': ''MARS 2.0 also needs the files or lists submitted according to usage and type. For example, a file called '''NAME.DEL''' instructs us to only remove the '''name usage''' for entries listed in that file, as opposed to both name & subject usages.''
+
  
 
==links==
 
==links==

Revision as of 09:49, 2 June 2022

Step 6.13: Bibliographic Changes & Deletes

File:A6-13.png

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

6.1 - 6.2 - 6.3 - 6.4 - 6.5 - 6.6 - 6.7 - 6.9 - 6.10 - 6.11 - 6.12 - 6.13
1.0 - 2.0 - 3.0 - 4.0 - 5.0 - 6.0