You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Rationale

This group is intended to provide a forum for Sinopia cataloging community that deal with non-Latin scripts. Current PCC practice for cataloging in multiscript environment is to use MARC 21’s “Model A” (inclusion of non-Latin script data and transliterated data in Latin script that parallels non-Latin script in bibliographic records). Linked data provides libraries with new opportunities for managing non-Latin script data, as well as present challenges. This affinity group is an effort to explore different models when dealing with vernacular scripts in Sinopia Editor and create a community of practice for cataloging non-Latin script materials in the linked data environment in general, Sinopia in specific.

Scope:

Any non-Latin script but may focus on the ones that most likely to appear in cohort’s library collections as listed below:

  • East Asian scripts: Chinese, Japanese, Korean  

  • Middle Eastern scripts: Arabic, Persian, Hebrew, etc.

  • Southeast Asian scripts: Thai, etc.

  • South Asian scripts: Devanagari, Tamil, Bengali, etc.

  • European scripts: Cyrillic, Greek, Latin extended, etc.

  • American scripts: Deseret, Cherokee, etc.

  Approach

Possible topics:

  • Models for vernacular scripts in Sinopia: vernacular only for transcribed data; vernacular plus transliteration; other? What is Sinopia’s functionality in handling non-Latin data?

  • Diacritics in Sinopia; tools available for entering diacritics

  • authority control for non-Latin script names  

  •  impact of using vernacular script only on local discovery layer and resource discovery in general
  • data in specific scripts (right-to-left scripts, scripts without full Unicode support, etc.)
  • transliterating vernacular scripts using tools which may not follow LC Romanization tables
  • No labels