Expansion of available character set for configuration in ALEPH tables Idit Shachar-Abutbul May 2011 Aleph operations meeting

2 Copyright Statement All of the information and material inclusive of text, images, logos, product names is either the property of, or used with permission by Ex Libris Ltd. The information may not be distributed, modified, displayed, reproduced – in whole or in part – without the prior written permission of Ex Libris Ltd. TRADEMARKS Ex Libris, the Ex Libris logo, Aleph, SFX, SFXIT, MetaLib, DigiTool, Verde, Primo, Voyager, MetaSearch, MetaIndex and other Ex Libris products and services referenced herein are trademarks of Ex Libris, and may be registered in certain jurisdictions. All other product names, company names, marks and logos referenced may be trademarks of their respective owners. DISCLAIMER The information contained in this document is compiled from various sources and provided on an "AS IS" basis for general information purposes only without any representations, conditions or warranties whether express or implied, including any implied warranties of satisfactory quality, completeness, accuracy or fitness for a particular purpose. Ex Libris, its subsidiaries and related corporations ("Ex Libris Group") disclaim any and all liability for all use of this information, including losses, damages, claims or expenses any person may incur as a result of the use of this information, even if advised of the possibility of such loss or damage. © Ex Libris Ltd., 2009

3 Problem: We would like to add a phonograph symbol as a prefix to the display of the subfield {2xx}$$p we would need to use the Unicode U+2117 in edit_field.lng which is currently outside the available codes that can be used in this table. This is being considered for use in MARC21 in order to comply with RDA rules

4 Suggested configuration: Indeed in edit_field.lng table it is problematic to enter some actual Unicode characters, but there is a configuration to achieve this. The configuration is to use a regular letter from the Latin character set and make it become the unicode value that we need We will now describe this configuration

5 Step One In $alephe_root/unicode directory create the following character conversion table This means that in table bl_to_unicode the Z (Unicode value 5A becomes the phonograph symbol

6 Step Two Now in tab_character_conversion_line we will make reference to the bl_to_unicode table This means that character conversion BL_TO_UTF will use the values defined in table $alephe_uniocode/bl_to_unicode.

7 Step Three Now we need to add the appropriate character conversion line before the phonograph symbol (2117) will be converted from Z (5A) We also need to disable the character conversion after the Z is converted to the phonograph symbol, otherwise every Z will become the phonograph symbol. Therefore in the line after the conversion of Z to phonograph symbol we will use the default char-conv table which is 8859_1_to_utf.

8 Step Three For example, we created the following setup in edit_field.eng: Here we state the Z should convert to phonograph symbol Here we state that the character conversion should return “back to normal”

9 Step Four System number has field 24514$$p:

10 Step Five In the full view of this record in web OPAC we can see this symbol is being added:

11 The Unicode Value in templates It is also possible to add the Unicode value characters to cataloging templates For example if we want to add the Euro value to a cataloging template we can first add it to $alephe_unicode/bl_to_unicode USM01> cat bl_to_unicode !!-!!-!!-!!-!!-!!-!!-!!-!!-!!!! 5A 2117 #Z will become SOUND RECORDING COPYRIGHT 59 20AC #Y will become Euro sign USM01> This is YThis is a Euro

12 The Unicode Value in templates Here is a Y in the cataloging template using the special conversion 2451 L $$a $$b $$c $$h CHARACTER_CONVERSION=BL_TO_UTF 246 L $$a The symbol Y and the future of the European Union CHARACTER_CONVERSION=8859_1_TO_UTF 250 L $$a $$b

Thank You!