Contributor(s): THL Staff
This site is for access to technical documentation of the various databases used within THL for storing data of various types – the dictionary, image database, and so forth. The underlying technologies include the following types of databases - see these links for general information on these databases as we use them here, the links further below are about specific applications:
For general relatively shallow bibliographies of all types of print or non-print objects, whether English, Tibetan, or otherwise, we use a MYSQL database with PHP interface that is part of the SPT (Scout Portal Toolkit) application. SPT is a system built by the University of Wisconsin to make bibliographies of websites. In collaboration with the SPT group, we adapted it for use in making bibliographies of print materials and digital resources in addition to websites. SPT has extensive facilities for workflow management and online editing.
The documentation includes:
If online end-user bibliography web page is displaying an error saying a table is corrupt, run this command (according to Andres Montano, July 2015):
ssh sds-deployer@sdsv5.its.virginia.edu mysql -u rubyuser use thl_scoutportal2; repair table APSessionData;
For deep cataloging of Tibetan literature, we use a TEI-based XML DTD with a Tibet-specific modification.
The documentation includes:
Classical Tibetan literature is often marked by detailed internal structures that are often extracted as “outlines” of the content. For making such outlines of Tibetan texts, we use straight TEI-based XML markup. The “DIV” feature in TEI is used to render the nested levels. We have a manual for how to use Word Styles to create such an outline, and then a Visual Basic Macro to transform those word documents into valid TEI documents.
The documentation includes:
For marking up Tibetan e-texts, we use straight TEI for XML markup. We have a manual for how to use Word Styles to create such markup, and then a Visual Basic Macro to transform those word documents into valid TEI documents.
The documentation includes:
We use straight TEI for XML markup of scholarly essays in general. We have a manual for how to use Word Styles to create such markup, and then a Visual Basic Macro to transform those word documents into valid TEI documents.
The documentation includes:
The Gazetter of Tibet and the Himalayas is being completely re-engineered; here is the Gazetteer technical documentation.
The most important extension of our place studies into rich descriptive data belonging to a Place Encyclopedia is for monasteries. At present, we have only implemented this in a Filemaker Pro Database which simple adds on additional fields to the basic Gazetteer template. workflow purposes. This data is likely to be exported into XML, perhaps with EAC markup (see Biographical Encyclopedia for details on EAC).
We started out with a simple Word outline of our data structure and are now in the process of mapping this into XML using a new DTD called “Encoded Archival Context” (EAC). That process is not complete.
We are looking at using EAC, but there is nothing to report at present.
We currently only have implemented this in a Filemaker Pro Database for workflow purposes. This data is likely to be exported into XML, but that has not been resolved yet.
The documentation includes:
Our rich historical dictionary of the Tibetan language is a MYSQL database with a sophisticated JSP-based front end. It is used for presentation as well as extensive on-line editing with individuated metadata for each submission. It is where we keep studies of words, including rich analytical data from a linguistic point of view and passages attesting as to their historical use. We still are working out how to relate this to the Gazetteer, Biographical Encyclopedia, and other specialized resources. Our basic goal is to allow a search of the dictionary to include all of those, so that users can seamlessly find out if there is a Gazetteer entry for a place name and so forth.
The documentation includes:
Our simple Thangmi and Nepali dictionaries are both MYSQL databases with PHP interfaces. Both are purely for presentation and lack any online editing interface.
Our image database currently is a MYSQL database with a PHP interface. It is used for presentation but also has an extensive workflow and online managing interface. Our current plans are to begin to create XML-based collections using the GDMS DTD developed at the University of Virginia Library.
Many of the audio-video files in the Audio-Video Database have been transcribed using XML markup based on a simple linguistic DTD created by Michel Jacobson of CNRS-LACITO. However we have not yet indexed them nor set up a search interface.
Our image database currently is a MYSQL database with a PHP interface. It is used for presentation and has no online editing interface. Our current plans are to begin to create XML-based collections using the GDMS DTD developed at the University of Virginia Library.