Difference between revisions of "RDA 1.4"

From AC Wiki
Jump to: navigation, search
(→‎Default)
 
(13 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
==STEP 1.4 : FILE DOWNLOAD AND FILE FORMAT==
+
==RDA 1.4: Records to Deliver==
−
{| border="0" cellpadding="5" cellspacing="0" align="left"
+
[[Image:rda1-4.png]]<br><br>
−
|-
+
===All bib records===
−
! colspan="3" style="background: lightblue" | 1.1 - Records Delivered by Backstage
+
When enriching AACR2 records and creating hybrid AACR2 / RDA records, even though all records may not be changed, it may be preferable that all bibs are returned. This is especially useful in conjunction with Step 1.5 when adding change stamps to the records.
−
|- align="left" style="background: white"
+
−
| || style="background: #CCFFFF;" | &#9744; Website || &#9744; FTP
+
−
|-
+
−
| || &#9744; MARC-8 || style="background: #CCFFFF;" | &#9744; UTF-8
+
−
|-
+
−
|}
+
−
<div style=clear:both></div><br>
+
−
===utf-8 vs marc-8 format===
+
−
The MARC-8 character set uses 8-bit characters. Due to the limitation of
+
−
characters that this allows, MARC-8 also includes methods to extend the
+
−
displayable characters: spacing based characters (for cursor movement) and
+
−
non-spacing characters (diacritics).
+
  
−
MARC-8 also employs the use of alternate character sets in order to tackle the
+
===Changed bibs only===
−
diacritic display issue. This is done by using escape sequences, which are special
+
This option encompasses all changes made during the RDA processing. If you
−
codes to indicate which character set is being selected for display: subscripts,
+
want the RDA processing to only take place when enriching and validating
−
superscripts, CJK characters, etc.
+
existing RDA bib records, then you could choose to have only changed bib
 +
records returned.
  
−
While these methods allow for many additional characters to be used, it is still
+
===Bibliographic file segmentation===
−
limited and somewhat burdensome.
+
ILS limitations or requirements for loading and indexing updated records are a
 +
consideration in determining maximum bibliographic output size.
  
−
UTF-8 is a standard based on 16-bit characters. It is a method of encoding
+
The response time in some local systems is sometimes degraded during
−
characters into sequences of from 1 to 3 bytes. Unicode has definitions for nonspacing
+
prolonged loads. In other ILS, essential online system tasks cannot be
−
characters like MARC-8, except these characters are handled differently
+
performed during a load.
−
for UTF-8.
+
  
−
UTF-8 also includes many precomposed characters. These are spacing
+
While Backstage can handle files in excess of 1,000,000 records, we can also
−
characters that are equivalent to one or more diacritic characters and a spacing
+
distribute files broken up into more appropriate chunks to facilitate the loading
−
character. To handle the various ways a composite character could be displayed,
+
and indexing processes on your side.
−
normalization forms have been defined.
+
  
−
Normalization Form Decomposed (NFD) and Normalization Form Composed
+
==Default==
−
(NFC) are standardized forms for handling composite characters.
+
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
−
 
+
|- style="background:#CCFFFF; font-size: 110%;"
−
In NFD, every character that can be decomposed is converted to its most
+
| Deliver all bibliographic records returned in a single file.
−
decomposed form following rules for canonical decomposition.
+
|}
−
 
+
<div style=clear:both></div><br>
−
In NFC, the characters are first decomposed as in NFD, then composed into
+
−
precomposed (composite) forms following canonical rules. This may result in
+
−
the sequence of characters for a given character changing into an alternate,
+
−
equivalent form.
+
  
−
==LINKS==
+
==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]]

Latest revision as of 14:52, 27 March 2014

RDA 1.4: Records to Deliver

Rda1-4.png

All bib records

When enriching AACR2 records and creating hybrid AACR2 / RDA records, even though all records may not be changed, it may be preferable that all bibs are returned. This is especially useful in conjunction with Step 1.5 when adding change stamps to the records.

Changed bibs only

This option encompasses all changes made during the RDA processing. If you want 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 on your side.

Default

Deliver all bibliographic records returned in a single file.

links

1.1 - 1.2 - 1.3 - 1.4 - 1.5
1.0 - 2.0 - 3.0 - 4.0 - 5.0 - 6.0
Retrieved from "https://ac.bslw.com/community/wiki/index.php?title=RDA_1.4&oldid=2404"