Difference between revisions of "RDA 1.2"

From AC Wiki
Jump to: navigation, search
(LINKS)
Line 1: Line 1:
==STEP 1.2 : TYPE OF RDA PROCESSING==
+
==RDA 1.2: Records Delivered by Backstage==
[[File:RDA_1.2.jpg]]
+
{| border="0" cellpadding="5" cellspacing="0" align="left"
===records to process===
+
|-
The steps taken in this profile can be used to convert all of your bibliographic
+
|- align="left" style="background: white"
records from AACR2 (or an older standard) to RDA, upgrade existing RDA bib
+
| || style="background: #CCFFFF;" | ☐ Website || ☐ FTP ||
records (as designated by the 040 $e rda), or create hybrid AACR2/RDA bib
+
|-
records.
+
| || ☐ MARC-8 || style="background: #CCFFFF;" | ☐ 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).
  
===convert all bib records to rda===
+
MARC-8 also employs the use of alternate character sets in order to tackle the
If you choose to convert all records to RDA, then every AACR2 record that is
+
diacritic display issue. This is done by using escape sequences, which are special
processed will be updated to include the RDA updates chosen in the rest of this
+
codes to indicate which character set is being selected for display: subscripts,
profile.
+
superscripts, CJK characters, etc.
  
===upgrade existing rda records===
+
While these methods allow for many additional characters to be used, it is still
When you choose to have Backstage upgrade your existing RDA bibliographic
+
limited and somewhat burdensome.
records, our processes will validate and correct standard information within
+
only records that already contain 040 $e rda.
+
  
===create hybrid aacr2/rda records===
+
UTF-8 is a standard based on 16-bit characters. It is a method of encoding
The PCC is working on guidelines for creating a hybrid AACR2/RDA bibliographic
+
characters into sequences of from 1 to 3 bytes. Unicode has definitions for nonspacing
record. Options within this profile can help you upgrade your existing AACR2
+
characters like MARC-8, except these characters are handled differently
and RDA bib records to be hybrid records as outlined by the PCC standard.
+
for UTF-8.
  
==LINKS==
+
UTF-8 also includes many precomposed characters. These are spacing
 +
characters that are equivalent to one or more diacritic characters and a spacing
 +
character. To handle the various ways a composite character could be displayed,
 +
normalization forms have been defined.
 +
 
 +
Normalization Form Decomposed (NFD) and Normalization Form Composed
 +
(NFC) are standardized forms for handling composite characters.
 +
 
 +
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==
 
<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:08, 13 March 2013

RDA 1.2: Records Delivered by Backstage

☐ Website ☐ FTP
☐ MARC-8 ☐ UTF-8

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 diacritic display issue. This is done by using escape sequences, which are special codes to indicate which character set is being selected for display: subscripts, superscripts, CJK characters, etc.

While these methods allow for many additional characters to be used, it is still limited and somewhat burdensome.

UTF-8 is a standard based on 16-bit characters. It is a method of encoding characters into sequences of from 1 to 3 bytes. Unicode has definitions for nonspacing characters like MARC-8, except these characters are handled differently for UTF-8.

UTF-8 also includes many precomposed characters. These are spacing characters that are equivalent to one or more diacritic characters and a spacing character. To handle the various ways a composite character could be displayed, normalization forms have been defined.

Normalization Form Decomposed (NFD) and Normalization Form Composed (NFC) are standardized forms for handling composite characters.

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

1.1 - 1.2 - 1.3 - 1.4 - 1.5
1.0 - 2.0 - 3.0 - 4.0 - 5.0 - 6.0