Difference between revisions of "Step 4.1"
(→STEP 4.1 : BIBLIOGRAPHIC FILE OUTPUT) |
(→STEP 4.1 : BIBLIOGRAPHIC FILE OUTPUT) |
||
| Line 1: | Line 1: | ||
==STEP 4.1 : BIBLIOGRAPHIC FILE OUTPUT== | ==STEP 4.1 : BIBLIOGRAPHIC FILE OUTPUT== | ||
| − | [[Image: | + | [[Image:ac4-1.png]]<br><br> |
===all bib records=== | ===all bib records=== | ||
Since many libraries request MARS 2.0 authority control when implementing or migrating to a new ILS, or when building a consortial database, returning all records is usually necessary to build a new catalog. | Since many libraries request MARS 2.0 authority control when implementing or migrating to a new ILS, or when building a consortial database, returning all records is usually necessary to build a new catalog. | ||
Revision as of 12:52, 21 March 2013
Contents
STEP 4.1 : BIBLIOGRAPHIC FILE OUTPUT
all bib records
Since many libraries request MARS 2.0 authority control when implementing or migrating to a new ILS, or when building a consortial database, returning all records is usually necessary to build a new catalog.
changed bibs only
Encompasses all changes made during MARS 2.0 processing. Selecting this option often results in return of a majority of bibliographic records (80-95% is common). This option includes changes made during Step 2 (Bibliographic Cleanup) as well as Step 3 (Authority Cleanup).
bibliographic file segmentation
ILS limitations or requirements for loading and indexing updated records are a consideration in determining maximum bibliographic output size.
The response time in some local systems is sometimes degraded during prolonged loads. In other ILS, essential online system tasks cannot be performed during a load.
While MARS 2.0 can handle files in excess of 1,000,000 records, we can also distribute files broken up into more appropriate chunks to facilitate the loading and indexing processes at your side.
LINKS
1.0 - 2.0 - 3.0 - 4.0 - 5.0 - 6.0
