Date: Tue, 19 Mar 2024 04:35:31 -0400 (EDT) Message-ID: <1636358306.8703.1710837331938@lyrasis1-roc-mp1> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_8702_356190669.1710837331938" ------=_Part_8702_356190669.1710837331938 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Discussions and Recommendations for Common Practices su= bmitted August 6, 2020
Best Practices for Cataloging Translations (August 202= 0 version)
In September 20= 19 the Group has administered a Survey on Romani= zation = to help make recommendations on the use of romanization in lib= rary catalogs within a linked data environment.
Survey report = is available here https://docs.google.com/document/d/1HVmtQxXSE0aphipdACNTTck6rzT3gPEoq= jzKynYgL78/edit#
PDF version:&nb= sp;Survey-on-Romaniz= ation-analysis (Final).pdf
Link to PPT pre= sentation on the survey results https://drive.google.com/drive/folders/1YKilUeZfreL4lS-IUgXmk8C8WsO= TkiKk
This group is i= ntended to provide a forum for Sinopia cataloging community that deal with = non-Latin scripts. Current PCC practice for cataloging in multiscript envir= onment is to use MARC 21=E2=80=99s =E2=80=9CModel A=E2=80=9D (inclusion of = non-Latin script data and transliterated data in Latin script that parallel= s non-Latin script in bibliographic records). Linked data provides librarie= s with new opportunities for managing non-Latin script data, as well as pre= sent challenges. This affinity group is an effort to explore different mode= ls when dealing with vernacular scripts in Sinopia Editor and create a comm= unity of practice for cataloging non-Latin script materials in the linked d= ata environment in general, Sinopia in specific.
Any non-Latin s= cript but may focus on the ones that most likely to appear in cohort=E2=80= =99s library collections as listed below:
East Asian scripts: Chinese, Japanese, Korean <= /span>
Middle Eastern scripts: Arabic, Hebrew, etc.= p>
Southeast Asian scripts: Thai, etc.
South Asian scripts: Devanagari, Tamil, Bengali, etc.=
European scripts: Cyrillic, Greek, Latin extended, et= c.
American scripts: Deseret, Cherokee, etc.
<= /li>Co-chaired by Larisa Walsh and Pa=
tricia Thurston (2020-present), @Xiaoli Li and Larisa Walsh (2019-2020)
<=
/p>
Monthly calls (2022- ), bi-weekly calls (2019-2021)
Dedicated, open Slack channel in LD4P2 = =E2=80=93 #nonlatinaffinitygrp (join LD4 public Slack)=
Dedicated, open Google group =E2=80=93 https://groups.google.com/forum/#!forum= /ld4p2-non-latin-materials
Google email list - ld4p2-non-latin-materials@googlegroups.com
Monthly calls -=
2nd Tuesday of the month, 10-11 am (Pacific Time), 12am -1 pm (Central Time), 1-2 pm =
(Eastern Time)
Join: https://yale.zoom.us/j/98047774878
models for vernacular scripts in Sinopia: vernacular = only for transcribed data; vernacular plus transliteration; other? What is = Sinopia=E2=80=99s functionality in handling non-Latin data?
diacritics in Sinopia; tools available for entering d= iacritics
authority control for non-Latin script names = span>
impact of using vernacular script only on local disco= very layer and resource discovery in general
data in specific scripts (right-to-left scripts, scri= pts without full Unicode support, etc.)
transliterating vernacular scripts using tools which = may not follow LC Romanization tables