| Page Properties | |||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Background
Best practices for overlaying bibliographic records in Alma. To dealing with numeric character references in records using non-Latin scripts. To be used in conjunction with the policy “Numeric Character References.”
Best practice recommendations
Non-MARC-8 scripts exported in MARC-8 data format are saved in Numeric Character Reference (NCR) format (see Numeric Character Reference for more information). However, all settings for Alma should be UTF-8 Unicode.
...
Connexion Client Help advises that unsupported non-Latin characters can be entered and exported to a local system using Unicode, but then deleted from the OCLC master record (NOTE: This violates CSU 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 OCLC noted: “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.”
.
Action log
| Section | Point Person | Expected Completion Date | Last action taken | Next action required |
|---|
Articulate the need for the policy (background)
Create a Policy Statement
Identify and create best practice recommendations
Where applicable, identify and write up procedures in Alma
Tasks to be completed
- Type your task here, using "@" to assign to a user and "//" to select a due date
Separated out best practices from policy | @Cataloging Task Force |
|