Difference between revisions of "RDA 1.4"
(→Changed bibs only) |
(→Bibliographic file segmentation) |
||
| Line 21: | Line 21: | ||
distribute files broken up into more appropriate chunks to facilitate the loading | distribute files broken up into more appropriate chunks to facilitate the loading | ||
and indexing processes at your side. | and indexing processes at your side. | ||
| + | |||
| + | '''The default is to return all bibliographic records in a single file.''' | ||
==links== | ==links== | ||
Revision as of 17:56, 26 March 2013
Contents
RDA 1.4: Records to Deliver
All bib records
If you prefer, you may have all bibs returned whether they have had any changes or not.
Changed bibs only
This option encompasses all changes made during the RDA processing. If you would like the RDA processing to only take place when enriching and validating existing RDA bib records, then you could choose to have only changed bib records returned.
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 Backstage 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.
The default is to return all bibliographic records in a single file.
links
1.0 - 2.0 - 3.0 - 4.0 - 5.0 - 6.0
