USAGE OF “NEW” MARC 21 CHARACTERS IN MARC-8 RECORDS

Page 1 Last revised: 2006-04-04; earlier versions, 2006-03-16, 2006-01-14, 2005-11-21, 2001-01-08

Character Hex LC use in Bibliographic Use in Authority Records LC Processing Conversion NACO Node Name Records (LC and NACO) Implications of legacy Consensus data? Spacing 5E Current: Supply in Current: use %5E in Current: CDS has no No Agree to circumflex fields/subfields where URIs authority records until more substitutions for bib implement, no are likely to occur (“Enforced” controlled use of URIs in records; CDS and earlier than June with Validator on LC records authority records is NACO preprocessing 2006 only) implemented in NACO. rejects authorities

Proposed future: Proposed future: Future implications: Implement character. Implement character. -LC will arrange to lift restrictions on LC : LC will retain authorities. internal checks to minimize -LC will revise DCM confusion between spacing Z1 (670) and non-spacing circumflex. USAGE OF “NEW” MARC 21 CHARACTERS IN MARC-8 RECORDS

Page 2 Last revised: 2006-04-04; earlier versions, 2006-03-16, 2006-01-14, 2005-11-21, 2001-01-08

Character Hex LC use in Bibliographic Use in Authority Records LC Processing Conversion NACO Node Name Records (LC and NACO) Implications of legacy Consensus data? Spacing 5F Current: Supply in Current: use %5F in Current: CDS has no No Agree to fields/subfields where URIs authority records until more substitutions for bib implement, no are likely to occur (“Enforced” controlled use of URIs in records; CDS and earlier than June with Validator on LC records authority records is NACO preprocessing 2006 only) implemented in NACO. rejects authorities

Proposed future: Proposed future: Future implications: Implement character. Implement character. -LC will arrange to lift restrictions on LC note: LC will retain authorities. internal checks to minimize -LC will revise DCM confusion between spacing Z1 (670) and non-spacing underscore. USAGE OF “NEW” MARC 21 CHARACTERS IN MARC-8 RECORDS

Page 3 Last revised: 2006-04-04; earlier versions, 2006-03-16, 2006-01-14, 2005-11-21, 2001-01-08

Character Hex LC use in Bibliographic Use in Authority Records LC Processing Conversion NACO Node Name Records (LC and NACO) Implications of legacy Consensus data? Spacing 7E Current: Supply in Current: use %7E in Current: CDS has no No Agree to fields/subfields where URIs authority records until more substitutions for bib implement, no are likely to occur (“Enforced” controlled use of URIs in records; CDS and earlier than June with Validator on LC records authority records is NACO preprocessing 2006 only) implemented in NACO. rejects authorities

Proposed future: Proposed future: Future implications: Implement character. Implement character. -LC will arrange to lift restrictions on LC note: LC will retain authorities. internal checks to minimize -LC will revise DCM confusion between spacing Z1 (670) and non-spacing tilde. USAGE OF “NEW” MARC 21 CHARACTERS IN MARC-8 RECORDS

Page 4 Last revised: 2006-04-04; earlier versions, 2006-03-16, 2006-01-14, 2005-11-21, 2001-01-08

Character Hex LC use in Bibliographic Use in Authority Records LC Processing Conversion NACO Node Name Records (LC and NACO) Implications of legacy Consensus data? Spacing 60 Current: Should not be Current: Should not be Current: CDS has no n/a Agree to grave supplied in LC cataloging (no supplied in LC cataloging substitutions for bib implement, no known use for the character). (no known use for the records; CDS and earlier than June character). NACO preprocessing 2006 Proposed future: rejects authorities Implement character. Proposed future: Implement character. Future implications: LC note: LC will retain -LC will arrange to lift internal checks to minimize restrictions on confusion between spacing authorities. and non-spacing grave. Opening 7B Current: Supply (unlikely to Current: Supply (unlikely Current: CDS has no n/a Agree to curly appear). to appear). substitutions. implement, no earlier than June Proposed future: Proposed future: Future implications: 2006 Implement character. Implement character. None Closing 7D Current: Supply (unlikely to Current: Supply (unlikely Current: CDS has no n/a Agree to curly appear). to appear). substitutions. implement, no bracket earlier than June Proposed future: Proposed future: Future implications: 2006 Implement character. Implement character. None USAGE OF “NEW” MARC 21 CHARACTERS IN MARC-8 RECORDS

Page 5 Last revised: 2006-04-04; earlier versions, 2006-03-16, 2006-01-14, 2005-11-21, 2001-01-08

Character Hex LC use in Bibliographic Use in Authority Records LC Processing Conversion NACO Node Name Records (LC and NACO) Implications of legacy Consensus data? Degree sign C0 Current: use the superscript Current: use the Current: CDS has no Conversion Agree to zero as a replacement for the superscript zero as a substitutions for bib of legacy implement, no degree sign. replacement for the degree records; CDS and data under earlier than June sign. NACO preprocessing discussion 2006 Proposed future: rejects authorities Implement character. Proposed future: Implement character. Future implications: -LC will lift restrictions on authorities. -LC will revise LCRI 1.0E Lowercase C1 Current: Pass through but not Current: Pass through but Current: CDS has no n/a Agree to script l actively supply. not actively supply. substitutions. implement, no earlier than June Proposed future: Proposed future: Future implications: 2006 Implement character. Implement character. None Note: OCLC currently uses local value, but will switch to the MARC value USAGE OF “NEW” MARC 21 CHARACTERS IN MARC-8 RECORDS

Page 6 Last revised: 2006-04-04; earlier versions, 2006-03-16, 2006-01-14, 2005-11-21, 2001-01-08

Character Hex LC use in Bibliographic Use in Authority Records LC Processing Conversion NACO Node Name Records (LC and NACO) Implications of legacy Consensus data? Phono C2 Current: Do not use. Current: Do not use. Current: CDS has no Conversion Agree to copyright substitutions for bib of legacy implement, no mark Proposed future: Proposed future: records; CDS and data not earlier than June Implement character Implement character NACO preprocessing expected 2006 rejects authorities LC note: LC will not actively LC note: LC will not supply in 260$c (will continue actively supply in 670 Future implications: to substitute “p”) but will pass citations (will continue to -LC will lift through the character if found substitute “p”) but will pass restrictions on in copy cataloging and other through the character if authorities. contributed records input by another NACO -LC will adjust LCRI node 1.4F5 option decision to label as “LC Practice” USAGE OF “NEW” MARC 21 CHARACTERS IN MARC-8 RECORDS

Page 7 Last revised: 2006-04-04; earlier versions, 2006-03-16, 2006-01-14, 2005-11-21, 2001-01-08

Character Hex LC use in Bibliographic Use in Authority Records LC Processing Conversion NACO Node Name Records (LC and NACO) Implications of legacy Consensus data? Copyright C3 Current: Do not use. Current: Do not use. Current: CDS has no Conversion Agree to mark substitutions for bib of legacy implement, no Proposed future: Proposed future: records; CDS and data not earlier than June Implement character Implement character NACO preprocessing expected 2006 rejects authorities LC note: LC will not actively LC note: LC will not supply in 260$c (will continue actively supply in 670 Future implications: to substitute “c”) but will pass citations (will continue to -LC will lift through the character if found substitute “c”) but will pass restrictions on in copy cataloging and other through the character if authorities contributed records input by another NACO -LC will adjust LCRI node 1.0E -LC will adjust LCRI 1.4F5 option decision to label as “LC Practice” USAGE OF “NEW” MARC 21 CHARACTERS IN MARC-8 RECORDS

Page 8 Last revised: 2006-04-04; earlier versions, 2006-03-16, 2006-01-14, 2005-11-21, 2001-01-08

Character Hex LC use in Bibliographic Use in Authority Records LC Processing Conversion NACO Node Name Records (LC and NACO) Implications of legacy Consensus data? Sharp C4 Current: use the number sign Current: use the number Current: CDS has no Conversion Agree to as a replacement for the sharp sign as a replacement for substitutions for bib of legacy implement, no sign. the sharp sign. records; CDS and data under earlier than June NACO preprocessing discussion 2006 Proposed future: Proposed future: rejects authorities Implement character. Implement character. Future implications: -LC will lift restrictions on authorities USAGE OF “NEW” MARC 21 CHARACTERS IN MARC-8 RECORDS

Page 9 Last revised: 2006-04-04; earlier versions, 2006-03-16, 2006-01-14, 2005-11-21, 2001-01-08

Character Hex LC use in Bibliographic Use in Authority Records LC Processing Conversion NACO Node Name Records (LC and NACO) Implications of legacy Consensus data? Inverted C5 Current: Do not use except in Current: Do not use. Current: CDS has no On “as Agree to question HLAS database substitutions for bib encountered implement, no mark records; CDS and ” basis, not earlier than June Proposed future: Proposed future: NACO preprocessing systematic 2006 Implement character. Implement character. rejects authorities

Future implications: -LC will lift restrictions on authorities -LC will revise LCRI 1.0E USAGE OF “NEW” MARC 21 CHARACTERS IN MARC-8 RECORDS

Page 10 Last revised: 2006-04-04; earlier versions, 2006-03-16, 2006-01-14, 2005-11-21, 2001-01-08

Character Hex LC use in Bibliographic Use in Authority Records LC Processing Conversion NACO Node Name Records (LC and NACO) Implications of legacy Consensus data? Inverted C6 Current: Do not use. Current: Do not use. Current: CDS has no On “as Agree to exclamation substitutions for bib encountered implement, no mark Proposed future: Proposed future: records; CDS and ” basis, not earlier than June Implement character. Implement character. NACO preprocessing systematic 2006 rejects authorities

Future implications: -LC will lift restrictions on authorities -LC will revise LCRI 1.0E USAGE OF “NEW” MARC 21 CHARACTERS IN MARC-8 RECORDS

Page 11 Last revised: 2006-04-04; earlier versions, 2006-03-16, 2006-01-14, 2005-11-21, 2001-01-08

Character Hex LC use in Bibliographic Use in Authority Records LC Processing Conversion NACO Node Name Records (LC and NACO) Implications of legacy Consensus data? Eszett C7 Current: Do not use, Current: Do not use, Current: none, On “as [ON HOLD] substitute “ss” for Eszett substitute “ss” for Eszett character not yet encountered implemented in VwU ” basis, not Proposed future: Proposed future: systematic [ON HOLD] [ON HOLD] Future implications: -LC is consulting with LC note: the decomposition of Endeavor about a characters “feature” in change to the Voyager automatically character converts the eszett to roman decomposition table “ss”; this decomposition is a server level activity that can not be locally configured, so a fix from Endeavor will be necessary prior to implementation USAGE OF “NEW” MARC 21 CHARACTERS IN MARC-8 RECORDS

Page 12 Last revised: 2006-04-04; earlier versions, 2006-03-16, 2006-01-14, 2005-11-21, 2001-01-08

Character Hex LC use in Bibliographic Use in Authority Records LC Processing Conversion NACO Node Name Records (LC and NACO) Implications of legacy Consensus data? Euro C8 Current: Do not use, Current: Do not use, Current: none, unlikely? Agree to substitute “[Euro]” for substitute “[Euro]” for character not yet implement, no in some descriptive areas (LC symbol implemented in VwU. earlier than June does not supply prices in 2006 ISBNs, etc.) Proposed future: Future implications: Implement character -LC will revise LCRI Proposed future: 1.0E Implement character -LC will need to adjust configuration files for “special character” input, as well as MARC Repertoire-checking files for client workstations and roll the changes out to staff