- MARC-8 scripts (subsets of UTF-8 characters, so they also compatible with UTF-8 Unicode): Arabic, CJK (Chinese, Japanese, Korean), Cyrillic (within the MARC-8 character set), Greek, or Hebrew scripts.
- UTF-8 Unicode only scripts: Armenian, Bengali, Cyrillic (outside the MARC-8 character set), Devanagari, Ethiopic, Syriac, Tamil, or Thai scripts. These scripts are not included in MARC-8.
Upgraded record using newly supported characters (Kazakh example):
Connexion Client Help advises that non-Latin characters that are not supported by OCLC can be entered and exported to a local system using Unicode, but then deleted from the OCLC master record (NOTE: this violates Alliance policy, don”t do it); or you can enter the name of the character within square brackets using the Unicode standard name (for example, enter [schwa]), or for CJK characters, enter the reading of the character (for example, enter [yin]). NOTE: Client Help does not advise using NCRs. But AskUs@oclc.org told us via email: ‘However, for the stray unsupported character that appears in a supported script, then the NCR is appropriate. If the script is not supported, it should not be represented in the database, but rather be transliterated.’
Exceptions to this policy may be made in the case of large record sets provided by vendors, but Alliance members must make a commitment to using the available records that most closely adhere to this policy in such cases.
See OCLC”s International Cataloging Manual for more details: http://www.oclc.org/content/dam/support/connexion/documentation/client/international/internationalcataloging.pdf
|Current phase: Phase 5: Approved||Written by: Collaborative Technical Services Team|
|Approved by: Collaborative Technical Services Team on 8/15//2014; Reaffirmed with no changes by Technical Services Working Group on 10/25/2016; Minor update approved by Technical Services Working Group on 11/29/2106
||Last updated: 11/26/2016|
|Staff Contact: Cassie Schmitt||Nature of last update: minor update