Difference between revisions of "Step 4.1"
(Created page with "==STEP 4.1 : BIBLIOGRAPHIC FILE OUTPUT== Image:4a-1.png<br><br> ===all bib records=== Since many libraries request MARS 2.0 authority control when implementing or migrating t...") |
(→Step 4.1: Bibliographic File Output) |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | == | + | ==Step 4.1: Bibliographic File Output== |
| − | [[Image: | + | [[Image:a4-1.png]]<br><br> |
| − | === | + | ===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. Exporting all bibs does mean that you would potentially have to spend more time importing or overlaying them back into your system once processing has completed. However, it may also be useful to know which records have gone to Backstage for processing as opposed to changed bibs only. |
| − | === | + | ===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). | 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. | ILS limitations or requirements for loading and indexing updated records are a consideration in determining maximum bibliographic output size. | ||
| Line 14: | Line 14: | ||
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. | 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== | ||
| + | <center><font size="4">[[Step 4.1|4.1]] - [[Step 4.2|4.2]] - [[Step 4.3|4.3]] - [[Step 4.4|4.4]] - [[Step 4.5|4.5]] - [[Step 4.6|4.6]] - [[Step 4.7|4.7]] | ||
| + | <hr> | ||
| + | [[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center> | ||
[[category:Profile Guide]] | [[category:Profile Guide]] | ||
Latest revision as of 11:34, 25 June 2015
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. Exporting all bibs does mean that you would potentially have to spend more time importing or overlaying them back into your system once processing has completed. However, it may also be useful to know which records have gone to Backstage for processing as opposed to changed bibs only.
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
