RDA 1.2 - Revision history

Judy: /* UTF-8 vs MARC-8 format */

2013-03-28T22:51:11Z

‎UTF-8 vs MARC-8 format

Nate: /* UTF-8 vs MARC-8 format */

2013-03-27T14:43:23Z

‎UTF-8 vs MARC-8 format

Nate: /* UTF-8 vs MARC-8 format */

2013-03-27T14:25:26Z

‎UTF-8 vs MARC-8 format

Nate: /* UTF-8 vs MARC-8 format */

2013-03-27T14:22:58Z

‎UTF-8 vs MARC-8 format

Judy: /* UTF-8 vs MARC-8 format */

2013-03-26T23:26:29Z

‎UTF-8 vs MARC-8 format

Nate: /* RDA 1.2: Records Delivered by Backstage */

2013-03-25T15:22:25Z

‎RDA 1.2: Records Delivered by Backstage

Nate at 22:01, 14 March 2013

2013-03-14T22:01:41Z

Nate at 21:55, 14 March 2013

2013-03-14T21:55:41Z

WikiSysop: /* RDA 1.2: Records Delivered by Backstage */

2013-03-14T21:52:25Z

‎RDA 1.2: Records Delivered by Backstage

Nate at 21:08, 13 March 2013

2013-03-13T21:08:02Z

@@ Line 2: / Line 2: @@
 [[Image:rda1-1.png]]<br><br>
 ===UTF-8 vs MARC-8 format===
-The MARC-8 character set uses 8-bit characters. Due to the limitation of
+MARC-8 has been the standard format for MARC-21 records since 1968.  Nearly every system that can export records in MARC format can do so in 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
@@ Line 13: / Line 13: @@
 While these methods allow for many additional characters to be used, it is still
-limited and somewhat burdensome.
+limited and somewhat burdensome.  For example, built into the MARC-21 format is a limitation that no record can exceed 99,999 characters, and no field can exceed 9,999 characters.  If a record exceeds the field or record size limits, there may be truncation or loss of data.
-UTF-8 is a standard based on 16-bit characters. It is a method of encoding
+UTF-8 has been in use since early 1993, and is a standard based on 16-bit characters. The main difference between MARC-8 and UTF-8 is that UTF-8 allows for more character types to be used within the records.  Since UTF-8 can represent many more characters than MARC-8, the files tend to be larger in size.  Each character in UTF-8 is between 1 - 4 bytes (whereas MARC-8 is only 1 byte in length).
-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
+If your system uses UTF-8, please also let us know whether the characters are in precomposed or decomposed format.  Precomposed characters use combined diacritics (e.g., n & ~ are combined to form: ñ).  Decomposed format separates the characters.
-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
+Additionally, to handle the various ways a composite character could be displayed,
-(NFC) are standardized forms for handling composite characters.
+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
-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
 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,

@@ Line 36: / Line 36: @@
 equivalent form.
-  <font size="3">
+==Default==
-  '''The default is to return your records through our website in UTF-8 format.'''</font>
+{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
 ==links==

@@ Line 36: / Line 36: @@
 equivalent form.
-   <font size="4">
+   <font size="3">
    '''The default is to return your records through our website in UTF-8 format.'''</font>

@@ Line 36: / Line 36: @@
 equivalent form.
-   '''The default is to return your records through our website in UTF-8 format.'''
+  <font size="4">
 ==links==

@@ Line 35: / Line 35: @@
 the sequence of characters for a given character changing into an alternate,
 equivalent form.
 ==links==

@@ Line 1: / Line 1: @@
 ==RDA 1.2: Records Delivered by Backstage==
-{| border="0" cellpadding="5" cellspacing="0" align="left" width="400" style="font-size:150%; font-family:'Courier new';"
+[[Image:rda1-1.png]]<br><br>
-|- align="center" style="font-weight: bold; background-color: #aaa;"
-| colspan="2" |
-|- 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

@@ 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;" | &#9744; Website || &#9744; FTP ||
-records (as designated by the 040 $e rda), or create hybrid AACR2/RDA bib
+|-
-records.
+| || &#9744; MARC-8 || style="background: #CCFFFF;" | &#9744; UTF-8 ||
-===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
 <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>
 [[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]]