Using character conversion to display non standard Unicode values

Slides:



Advertisements
Similar presentations
19.1 Chapter 19 Network Layer: Logical Addressing Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display.
Advertisements

Data Representation in Computers
ASCII & Gray Codes.
BIAF Print Label software setup
STRINGS CMSC 201 – Lab 3. Overview Objectives for today's lab:  Obtain experience using strings in Python, including looping over characters in strings.
Z39 Server and Z39.50 Gateway. Z39 Configuration Z39.50 Server Bath Profile conformance has been added to the Z39 Server. Z39 server supports Structure.
V. 21. new fix_doc_notes fix routine (downgraded to version 20 RC 3513) Yoel Kortick Aleph Support Manager.
How to sort the “Order Information report” from the service “Print Acquisitions Records acq-03” Yoel Kortick.
How to transfer 85x prediction patterns from ADM library to HOL library Presenter: Yoel Kortick.
How to Open a New Language in Web OPAC for Testing Web Screens Presenter: Yoel Kortick.
1 Audible Alert for Return Item on Hold rep_ver in V20 Yoel Kortick Aleph Support Manager.
Examples of UTF compliance in version 20.1 Yoel Kortick Aleph support manager.
V. 21. Automatic LKR field creation from item. Rep_ver and Yoel Kortick Aleph Support Manager.
V. 21. Controlling and limiting the creation of photocopy and hold requests according to “service hours”. Rep_Ver Yoel Kortick.
Display of combined characters in Aleph GUI Yoel Kortick May 2010 Version 20.2 Minor Release Development A rep_change #
Dates in ILL Yoel Kortick Dates in ILL The purpose of this presentation is to show how the various date parameters work when performing borrowing.
How to create and use authority records Version 16 and up Yoel Kortick.
How to control bracket and parentheses appearance in right to left display of web Presenter: Yoel Kortick.
1 Controlling directionality with Unicode Characters Yoel Kortick Aleph Support manager.
Full text indexing of multi character PDF documents as ADAM digital objects. V18 RC 2089 This presentation applies to Version 18 and up Presenter: Yoel.
© 2015 Ex Libris | Confidential & Proprietary Yoel Kortick Senior Librarian Cataloging introductory flow.
1 Designing and using normalization rules Yoel Kortick Senior Librarian, Ex Libris.
Aleph Publishing services with a special focus on PRIMO-FULL and PRIMO-AVAIL version 18 Presenter: Yoel Kortick.
1 Yoel Kortick | Senior Librarian Serials automation tasks for summary holdings.
1 Yoel Kortick Senior Librarian Alma Product Management Mapping the bibliographic call number to the holding record call number.
Indexing and filing the “thorn” character as “th” Yoel Kortick Jan
Expansion of available character set for configuration in ALEPH tables Idit Shachar-Abutbul May 2011 Aleph operations meeting.
Merge Rules and Routines
1 RDA in Aleph 500 Version 21 Yoel Kortick. Aleph support manager Nov
Validation Check Version 21 rep_ver # Yoel Kortick.
SMS Messaging in Aleph 500 Version 20 and up
An Introduction to the Bibliographic Metadata Profile in Alma
How to separate semicolon delimited values to separate columns
How to create links from an Alma Analytics report to Primo
How to add a non-Analytics widget to the Alma Dashboard
Binary 1 Basic conversions.
An article in an anthology and derive new record
Version 20 Feature Developments
MARC extensions Yoel Kortick | Senior Librarian
Digital Assets Module Services adam-01 and adam-02 versions 17 and up
How to Define Separate Order Counters for Separate Sub-Libraries
Yoel Kortick Senior Librarian
Publishing Course Readings to PRIMO Version 20
Presenter: Yoel Kortick
ReturnLoadPatron RC 2024 in V20
Yoel Kortick Aleph Support Manager
How to configure and use the Holdings record Accession Number
Metadata Editor Introduction
Special Issues in Hebrew Cataloging in Alma
How to Add Pinyin Text to a Record with CJK Version 18 RC 1807 Version 19 RC 409 Yoel Kortick.
Cataloging introductory flow
How to create links from an Alma Analytics report to Primo
Data Encoding Characters.
Chapter 19 Network Layer: Logical Addressing
Customize Letters How to customize letters via xsl
Network Layer: Logical Addressing
Yoel Kortick Senior Librarian
An article in an anthology and derive new record
Yoel Kortick Senior Librarian
Yoel Kortick Senior Librarian
Yoel Kortick Senior Librarian
Designing and Using Normalization Rules
‘Splitting’ the MUSIC format
Configuring and using the Accession Number and Inventory Number
Alternate graphic representation 880 field
New “replace string” parameter for fix_doc_do_file_08
Options > Settings > Rules
Prediction Patterns and Summary Holdings
Yoel Kortick Senior Librarian
Presentation transcript:

Using character conversion to display non standard Unicode values Yoel Kortick Aleph Support Manager

Problem (from actual SI): We would like to add a phonographic copyright symbol as a prefix to the display of the subfield 245$$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

Solution via configuration: In $alephe_unicode we will make a table which will convert a specific character to the phonographic copyright symbol with unicode value 2117 We will then refer to this table in $alephe_unicode/tab_character_conversion_line with a unique identifier We will then use this unique identifier in edit_field.eng

Step One In $alephe_root/unicode directory create the following character conversion table yoelk@il-aleph07(a20_3):~>cat $alephe_unicode/yoel_to_unicode !!-!!-!!-!!-!!-!!-!!-!!-!!-!!!! !* The first column below should be the Hx column in http://www.asciitable.com/ !* The second column below should be the value from http://www.unicode.org/charts/ 22 2117 # ! will become sound recording copyright 21 263A # " will become smiley face yoelk@il-aleph07(a20_3):~> This means that in table yoel_to_unicode the “ (quotation mark, Ascii value 22) becomes the phonographic copyright symbol (Unicode value 2117) We could have used any symbol, we chose “ because it is not used often (as is a regular character like a,b,c,d etc.)

Step Two Now in tab_character_conversion_line we will make reference to the yoel_to_unicode table yoelk@il-aleph07(a20_3):~>grep yoel_to_unicode $alephe_unicode/tab_character_conversion_line YOEL_TO_UTF ##### # line_sb2line_utf yoel_to_unicode yoelk@il-aleph07(a20_3):~> This means that character conversion YOEL_TO_UTF will use the values defined in table $alephe_unicode/yoel_to_unicode.

Step Three Now in edit_field.eng we need to add the appropriate character conversion line before the phonographic copyright symbol (2117) so that will be converted from “ (21) We also need to disable the character conversion after the “ is converted to the phonographic copyright symbol, otherwise every “ will become the phonographic copyright symbol. Therefore in the line after the conversion of “ to phonographic copyright symbol we will use the default character conversion table which is 8859_1_to_UTF.

Step Three For example, we created the following setup in edit_field.eng: Here we state the Z should convert to phonograph symbol 1 # 245## D B -6 2 a A ^ 2 b A ^ 2 c A ^ 2 h A ^ CHARACTER_CONVERSION=YOEL_TO_UTF 2 p A " CHARACTER_CONVERSION=8859_1_TO_UTF 1 # 245## 3 -6 2 # Due to the character conversion line the “ will become a phonographic copyright symbol Here we state that the character conversion should return “back to normal”

Step Four System number 85911 has field 24510$$p:

Step Five In the full view of this record in web OPAC we can see this symbol is being added as a prefix. The configuration effects web full view because it was done for identifier D in edit_field.eng

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 phonographic copyright symbol value to a cataloging template as a prefix to 245$$p we can add it as follows: Here we state the Z should convert to phonograph symbol Due to the character conversion line the “ will become a phonographic copyright symbol 0821 L $$a 1001 L $$a $$d CHARACTER_CONVERSION=YOEL_TO_UTF 2451 L $$a $$b $$c $$h $$p" CHARACTER_CONVERSION=8859_1_TO_UTF 250 L $$a $$b Here we state that the character conversion should return “back to normal”

The Unicode Value in templates Here is the phonographic copyright symbol in the template template using the special character conversion

Yoel. Kortick@exlibrisgroup.com Thank You Yoel. Kortick@exlibrisgroup.com