Difference between revisions of "RDA 1.4"

From AC Wiki
Jump to: navigation, search
Line 1: Line 1:
−
==RDA 1.2: Records Delivered by Backstage==
+
==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;" | ☐ Website || ☐ FTP ||
+
| || style="background: #CCFFFF;" | ☐ All bibliographic records returned ||
 
|-
 
|-
−
| || ☐ MARC-8 || style="background: #CCFFFF;" | ☐ UTF-8 ||
+
| || ☐ Changed bibliographic records returned ||
 
|-
 
|-
 
|}
 
|}
 
<div style=clear:both></div><br>
 
<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
+
===All bib records===
−
diacritic display issue. This is done by using escape sequences, which are special
+
When converting AACR2 records to RDA, all records will have some changes
−
codes to indicate which character set is being selected for display: subscripts,
+
made (even if the only change is updating the Leader and adding 040 $e rda). If
−
superscripts, CJK characters, etc.
+
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.
  
−
While these methods allow for many additional characters to be used, it is still
+
===Changed bibs only===
−
limited and somewhat burdensome.
+
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.
  
−
UTF-8 is a standard based on 16-bit characters. It is a method of encoding
+
===Bibliographic file segmentation===
−
characters into sequences of from 1 to 3 bytes. Unicode has definitions for nonspacing
+
ILS limitations or requirements for loading and indexing updated records are a
−
characters like MARC-8, except these characters are handled differently
+
consideration in determining maximum bibliographic output size.
−
for UTF-8.
+
  
−
UTF-8 also includes many precomposed characters. These are spacing
+
The response time in some local systems is sometimes degraded during
−
characters that are equivalent to one or more diacritic characters and a spacing
+
prolonged loads. In other ILS, essential online system tasks cannot be
−
character. To handle the various ways a composite character could be displayed,
+
performed during a load.
−
normalization forms have been defined.
+
  
−
Normalization Form Decomposed (NFD) and Normalization Form Composed
+
While Backstage can handle files in excess of 1,000,000 records, we can also
−
(NFC) are standardized forms for handling composite characters.
+
distribute files broken up into more appropriate chunks to facilitate the loading
−
 
+
and indexing processes at your side.
−
In NFD, every character that can be decomposed is converted to its most
+
−
decomposed form following rules for canonical decomposition.
+
−
 
+
−
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==

Revision as of 15:09, 13 March 2013

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.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=1165"