Accessing and Using Servers in THDL
Introduction
THDL relies upon servers to store its content. A server is essentially just a special computer that is dedicated to serving many users rather than just one user. Its storage capacity, or hard drives, thus "serves" up content to many users who come to it through a local network or the Web. Those without technical background can easily understand the concept through comparing it to a kitchen such as one finds in a cafeteria or restaurant rather than preparing and processing meals for just one individual or family, it processes and "serves" up meals/content for many individuals. Thus it has to have industrial strength, though essentially it is just an amplification of an ordinary kitchen.
Since so many people rely upon a server, of course it needs significant security controls to insure that its contents are not altered or corrupted. Thus while anyone might be able to access the services and content a server provides to the public, only a very few content providers and maintainers are actually allowed direct access to the underlying folders/directories where information is stored so as to change and add content therein. Such interaction with a server can be done through through the medium of a program, such as a nice interface for editing a dictionary online, say, or can be done through directly accessing the directories on the server. Direct access is typically done using a FTP program, which allows one to contact the server, provide security information so as to be allowed inside, and then provides a graphic or textual list of directories much as you would see on your own computer's hard drive. You can then transfer over an individual file to your computer, edit it there, and then upload it back to the server the next moment, the public will see your changes live on the webpage. It's that simple.
THDL relies upon many servers, but its core servers at hosted at the University of Virginia Library. They can be directly accessed for work from anywhere in the world using a special program called "UVa-Anywhere" as detailed below. However such rights are limited to a few staff and other participants who require constant direct access to the servers to add and revise content. These rest of this document details the procedures for getting such access, and the protocols to follow for using such access. If are a THDL participant and think you should have such access, please contact us at thdl@virginia.edu.
The main array of HTML and XML pages in THDL are located on the Library's Orion server. These are secure servers because of security issues, and hence no one without a UVA computing ID and special software can directly access them. However, for core participants who require frequent access to THDL's servers, who are technically competent with HTML/XML and FTP, and who are completely dependable, we do have a means to arrange such access. This must be repeated each year or the account will lapse. If you already have a UVa Computing ID, you can skip the first step.
Securing a UVa Computing ID for Non-UVa Participants
- David Germano must write to accounts@virginia.edu to request that ITC at UVa set up a computing ID for the person in question. This email provides a short description of the rationale, name, affiliating department, sponsor (Germano), social security #, contact at UVa (Germano), and length of time (year). The email must also be clear that an ITC account is required, since to use UVa-Anywhere (see below), it is required that one make a PKI certificate which in turn requires either a CMS, Home Directory or hscmail password on CMS.
- ITC responds typically within 48 hours with approval, and a user ID along with a password (which can easily be changed).
Securing Account for Access to the Library Orion Server
- Germano contacts Guy Mengel via email to request that the person be given an account on Orion so that s/he can access THDL files housed there.
- The email gives the UVa ITC ID for the person, the person's name, his/her status and work done in THDL, and specifies what directories they need access to most generally the Tibet directory in LV9.
- Guy responds, and if he approves, provides a password for the User to access Orion.
The user must then change this password by logging onto the Scripta server:
- Detailed Instructions for logging onto the Scripta server.
Remote Access to UVa Servers
If the user is going to access Orion from an off-campus location, then they need to get a program called UVa-Anywhere which allows their computer to set up a special secure connection to UVa that allows them to do work as if they were on a campus networked computer. Supposedly it works for Mac OS, though we haven't tested this ourselves. The procedure takes a little time but is simple:
- Go to the UVa ITC VPN Homepage
- Click on "quick start installation" (there is also a link for Mac users)
- Install a personal certificate following the simple instructions
- Install the VPN Client following the simple instructions
- Restart your computer and open the VPN client to connect
- If it all works, you should be connected and into the UVa campus network
Secure FTP Software
Everyone, whether off-campus or on-campus, must use a secure FTP (SFTP) program to access the Orion server and upload/download files. It is not possible to access the Orion server except through an SFTP application. ITC provides free SFTP programs: SecureFX for Windows and Fugu for Mac.
- For Windows: go to the ITC SecureFX page and follow the installation instructions.
- For Mac OSX users, Fugu is a free SFTP application. For OS9 users MacSFTP may be an option; however, we have not tested it.
Configuring Secure FTP Software
It is important to configure properly your secure FTP (SFTP) application. You will not even be able to log onto the Orion server unless your FTP application supports secure FTP.
- Detailed Instructions for configuring your secure FTP software
As these instructions explain, you should configure your SFTP software so that other members of the THDL group can edit files you have created or edited. Implement the following configuration (you have already done this if you followed the detailed instructions for configuring secure FTP software from the link immediately above):
- Go to Options > Global Configuration...
- Click the Options > Advanced tab
- For File permissions enter 664
- For Directory permissions enter 775
Logging onto Orion
Once you have your computing ID, are on the campus network, and have a secure FTP program installed and configured, you are ready to go.
- Launch the SFTP application and connect to Orion. If you have problems, follow the Detailed Instructions for configuring your secure FTP software.
- Then follow these Detailed Instructions for uploading and downloading files (see step 14).
CVS Must Read before You Start Work
In 2004, we are implementing CVS which keeps track of multiple versions of a given Web page on a server. This requires downloading a CVS client. This is not difficult, but it is an additional step that has yet to be documented properly. Contact THDL staff in the meantime to step you through it.
HTML and XML Guidelines for Webpages
Before creating or editing a single file, please carefully consult the HTML Web management manuals in the Scholar's Toolbox on THDL. Otherwise you will wreck the files for everyone.
Folder Structure in Orion
The root directory on Orion has a folder/directory entitled "lv9", and within that is a directory entitled "tibet". All THDL files are located within this directory. The following is a list of the subdirectories within "tibet" and their contents. In general, you should not alter files in a directory unless you are in charge of it, or have cleared access with the person in charge.
- collections: this is a root level THDL domain folder. This is the only folder which multiple people will be working on. Below are the individual subfolders and responsibilities.
- architecture:
- art:
- av-archive:
- cultgeo:
- environment:
- geography:
- history:
- journal:
- langling:
- literature:
- medicine: Frances Garrett
- music:
- religion:
- resources:
- immersive:
- special:
- status:
- community: Steven Weinberger
- culture:
- education: David Newman
- tllr: Eric Woelfel.
- essays: Than Garson
- external:
- holdingarea: this is a folder holding various materials that may be eventually processed into the main THDL repositories, or may just be here as non-THDL items for reference. Either way, they are not for public dissemination.
- bibliographies: these are shallow bibliographies of specific types of texts, though they could have annotations.
- catalogs: these are catalogs of multi-volume compilations.
- e-texts: these are actual typed in texts.
- outlines: these are outlines, whether table of contents or more detailed topical outlines of Tibetan texts.
- reprints: these are reprints of modern scholarship or compositions which have been previously printed.
- summaries: these are summaries of texts, especially classical literature.
- images:
- intro:
- languagedocs:
- psdocs:
- reference: Steven Weinberger
- scripts:
- style:
- test:
- texts: this is a provisional folder where we are experimenting at keeping grouped together by type various resources which are concerned with texts.
- bibliographies: these are shallow bibliographies of specific types of texts, though they could have annotations.
- catalogs: these are catalogs of multi-volume compilations which should be in XML.
- e-texts: these are actual typed in texts which should be in XML.
- outlines: these are outlines, whether table of contents or more detailed topical outlines of Tibetan texts.
- reprints: these are reprints of modern scholarship or compositions which have been previously printed; they will generally be PDFs, but might be OCR-ed or author contributed as HTML, RTF, XML or other formats.
- summaries: these are summaries of texts, especially classical literature, which should be in XML.
- tools: Than Garson
- collaboration:
- scholartools:
- efolio:
- jskad_docs:
- nightly: David Chandler
- qtvr:
- quilldriver:
- savant:
- transitional:
- associates:
- french journal: pdfs of the French tibetology e-journal.
- worddocs: David Newman
- xml: Than Garson