Bibliographic records such as those in the International Union of Crystallography (IUCr) dataset often contain author names and other entries originating in non-roman scripts, but listed in transliterated form. Bibliographic tools should be capable of smoothly handling datasets with multiple representations of item data, including data in non-roman scripts.

Because transliteration results in data loss, legacy data sets cannot be refactored by automated means. However, with an ever closer connection between bibliographic data sets and authoring tools (Endnote, Zotero, Mendeley), it will become possible to crowdsource this work, by opening a path for the reuse of data sets which are enriched by end users during the authoring process.

The first step toward such an objective would be to extend an existing reference manager to work smoothly with multilingual data, for RDF import, editing, and RDF export.

submitted 22 Jan '11, 05:26

fbennett's gravatar image

accept rate: 0%

One response

I really like this because translation is a very easy discrete task that a lot of people could do and would enhance the underlying metadata.


solved 21 Apr '11, 10:03

rgrp's gravatar image

rgrp ♦♦
accept rate: 45%

Your response
toggle preview

Follow this question

By Email:

<span class='strong'>Here</span> (once you log in) you will be able to sign up for periodic email updates about this idea.



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported



Asked: 22 Jan '11, 05:26

Seen: 911 times

Last updated: 21 Apr '11, 10:03

powered by OSQA