Difference between revisions of "RDA 1.3"
| Line 1: | Line 1: | ||
| − | == | + | ==RDA 1.4: Records to Deliver== |
{| border="0" cellpadding="5" cellspacing="0" align="left" | {| border="0" cellpadding="5" cellspacing="0" align="left" | ||
|- | |- | ||
| − | |||
|- align="left" style="background: white" | |- align="left" style="background: white" | ||
| || style="background: #CCFFFF;" | ☐ All bibliographic records returned || | | || style="background: #CCFFFF;" | ☐ All bibliographic records returned || | ||
| Line 11: | Line 10: | ||
<div style=clear:both></div><br> | <div style=clear:both></div><br> | ||
| − | === | + | ===All bib records=== |
When converting AACR2 records to RDA, all records will have some changes | When converting AACR2 records to RDA, all records will have some changes | ||
made (even if the only change is updating the Leader and adding 040 $e rda). If | made (even if the only change is updating the Leader and adding 040 $e rda). If | ||
| Line 17: | Line 16: | ||
every bib record returned to replace your existing record in your ILS. | every bib record returned to replace your existing record in your ILS. | ||
| − | === | + | ===Changed bibs only=== |
This option encompasses all changes made during the RDA processing. If you | This option encompasses all changes made during the RDA processing. If you | ||
would like the RDA processing to only take place when upgrading and validating | would like the RDA processing to only take place when upgrading and validating | ||
| Line 23: | Line 22: | ||
records returned. | records returned. | ||
| − | === | + | ===Bibliographic file segmentation=== |
ILS limitations or requirements for loading and indexing updated records are a | ILS limitations or requirements for loading and indexing updated records are a | ||
consideration in determining maximum bibliographic output size. | consideration in determining maximum bibliographic output size. | ||
| Line 35: | Line 34: | ||
and indexing processes at your side. | and indexing processes at your side. | ||
| − | == | + | ==links== |
<center><font size="4">[[RDA_1.1|1.1]] - [[RDA_1.2|1.2]] - [[RDA_1.3|1.3]] - [[RDA_1.4|1.4]] - [[RDA_1.5|1.5]] | <center><font size="4">[[RDA_1.1|1.1]] - [[RDA_1.2|1.2]] - [[RDA_1.3|1.3]] - [[RDA_1.4|1.4]] - [[RDA_1.5|1.5]] | ||
<hr> | <hr> | ||
[[RDA_1.0|1.0]] - [[RDA_2.0|2.0]] - [[RDA_3.0|3.0]] - [[RDA_4.0|4.0]] - [[RDA_5.0|5.0]] - [[RDA_6.0|6.0]]</font></center> | [[RDA_1.0|1.0]] - [[RDA_2.0|2.0]] - [[RDA_3.0|3.0]] - [[RDA_4.0|4.0]] - [[RDA_5.0|5.0]] - [[RDA_6.0|6.0]]</font></center> | ||
[[category:RDA Profile Guide]] | [[category:RDA Profile Guide]] | ||
Revision as of 15:05, 13 March 2013
Contents
RDA 1.4: Records to Deliver
| ☐ All bibliographic records returned | ||
| ☐ Changed bibliographic records returned |
All bib records
When converting AACR2 records to RDA, all records will have some changes made (even if the only change is updating the Leader and adding 040 $e rda). If you are choosing to do the full crosswalk from AACR2 to RDA, you would need every bib record returned to replace your existing record in your ILS.
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 upgrading 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.
links
1.0 - 2.0 - 3.0 - 4.0 - 5.0 - 6.0
