<mods:mods version="3.3" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-3.xsd" xmlns:mods="http://www.loc.gov/mods/v3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><mods:titleInfo><mods:title>Adding Non-Latin Data to ALEPH</mods:title></mods:titleInfo><mods:name type="personal"><mods:namePart type="given">Charles</mods:namePart><mods:namePart type="family">Husbands</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:abstract>Unicode enables us to integrate original script data in non-Latin scripts into our bibliographic systems.  This program will discuss bringing these data into ALEPH.  How are they different from each other and from Latin-script data in terms of their ALEPH needs?  Issues of character conversion, indexing, workflow, desktop setup, etc. will be discussed.  The scripts to be considered are those currently provided for in MARC21.&#13;
&#13;
Audience:  For people who either contemplate adding or have added non-Latin script data to ALEPH bibliographic files.&#13;
&#13;
Version: 16</mods:abstract><mods:classification authority="lcc">Aleph</mods:classification><mods:originInfo><mods:dateIssued encoding="iso8601">2004-06-15</mods:dateIssued></mods:originInfo><mods:genre>Conference or Workshop Item</mods:genre></mods:mods>