Gazetteer Filemaker Editorial Manual

THDL Toolbox> Places & Geography > THDL Gazetteer > Gazetteer Filemaker Editorial Manual

The THDL Tibetan & Himalayan Gazetteer Filemaker Editorial Manual

Contributors: David Germano, David Newman (last revised April 4, 2007).

Overview

The THDL Gazetteer is the basis for THDL’s study and archiving of information on Tibetan and Himalayan places. In this sense it can be understood a dictionary of place names, with limited additional information – types of places, location, relationships, and brief description. Technically, it is an index of all “features” in the region, which is a generic term signifying all places of any type that have a geographical footprint, whether they be regions – nations, counties, cultural regions, and so forth – or points – specific lakes, villages, archaeological sites, and so forth. Thus is includes natural and cultural features.

The Gazetteer is not intended to maintain specialized descriptive information on specific types of features – such as rich descriptive information on monasteries, or the linguistic attributes of a community, and so forth. Such information has to be maintained in separate repositories. The Gazetteer instead offers an authoritative resource to search for place names of all types, and consult standard and limited information on the corresponding places. Thus the most sophisticated aspect of the Gazetteer is the extensive information on place names in various forms corresponding to various languages, historical periods, and usages.

The Gazetteer is additionally intended to function as a service to index other resources on the basis of relevant locations. This entails other databases using the Gazetteer’s unique geographical identifier to specify location-based information. This applies to all types of information that involve a specific location – such as location of recording, or location of speaker’s birthplace for audio-video recordings.This will allow users of the Gazetteer to easily identify and consult various resources within THDL that are related to the feature being viewed – images, audio-video recordings, essays, journal reprints, and specialized feature databases (such as a Monasteries Encyclopedia). Ultimately, we plan to offer the Gazetteer’s services so that non-THDL projects might utilize it to geo-index their own holdings, thereby providing a means for a broader indexing of Tibetan and Himalayan digital resources on the basis of geographical criteria.

The chief areas of the Gazetteer are as follows for all features:

  1. Names
  2. Times
  3. Types
  4. Ids or geocodes
  5. Locations
  6. Relationships
  7. Descriptions

The Gazetteer currently uses a XML Database to store information, which is then transformed for display and searching over the Web. The Database is driven by a custom designed "DTD", or Document Type Definition, which essentially means a toolbox of elements/tags that the University of Virginia has designed for use in making geographical databases and marking up the entries therein. The technically inclined should see the external link: Gazetteer DTD, or read Gazetteer Dtd Decoded For Dummies.

1. Feature Names (sa cha'i ming)

Feature names provides comprehensive documentation of all the variant forms of the name of a given "feature", i.e. toponyms. This includes names in different languages, vernacular vs. official names, and names in different time periods. A feature may contain one or more feature names, each containing its own descriptive and administrative (e.g. date of entry) meta-data.

XML: Sub-elements that fall within <fname> include dates of validity of the name <covtime>, etymologies <etymology>, pronunciation <pronunciation>, explanation of the source of the name <authority>, and any alternative name for the feature <altname>. Attributes: certainty, entrydate, id, isCurrent, label, lang, priority, resp, trans, type. Subelements: covtime, authority, etymology, pronunciation, altname (and geogname which is nothing but a container for the name itself)

Name History (sa cha’i ming lo rgyus): this is a synoptic survey of the naming history of the feature, rather than simply the documentation of a single entry. Thus, as opposed to the data in the Name Details section above which apply to a specific name, this data applies to the feature as a whole. Multiple histories can be created for a feature if different editors want to express their specific interpretation. XML: 0 or 1.

History Editor: Choose the creator/editor of the history passage. If the name is not there, then add it to the list.

History Edit Date: Enter the date the history was created/revised in the form of yyyy/mm/dd.

Name: Make an entry for each distinct name.

FMP: You will see that if you enter anything into the white box for Names, a second row of white boxes will appear. Each row of boxes is a unique record in our Names database; entries can be repeated ad infinitum. Note, however, that if you want to draw a relationship between any names (such as defining a name as a translation of another name), you need to follow the link to "Manage more feature Name details…" and there you can indicate the ID number of the name from which the name is derived.

Language: Enter the language of the current name entry. Choices include:

  • Chinese
  • English
  • Nepali
  • Tibet

FMP: Edit… – Use this to add language choices.

Name Type: Choices are as follows:

  • "standard" (the name we designate as normative; tshad ldan sa cha’i ming)
  • variant (mi ‘dra)
  • Vernacular
  • old orthography (brda rnying)
  • mistaken orthography (dag nor)
  • formal
  • other (specify)

Transliteration/Translation Form: If the name is a translation or transliteration of another place name, indicate that here.

  • Translation
  • Transliteration
  • Transliteration/Translation

Transliteration Scheme: Indicate the transliteration scheme, if any applies.

  • THDL extended Wylie
  • Wylie
  • Unknown orthographic
  • THDL simplified phonetics
  • THDL phonetics
  • Pinyin
  • Chinese romanized Tibetan
  • Unknown phonetic

Name "Derived From" Note: If the name in question is not an original name, but rather is derived from another name – such as a Chinese translation of a Tibetan name, then ndicate here the name from which the name is derived.

Name Begin: Be as specific as you can in indicating the earliest instance of the name in the current entry. In asserting a date, make sure that you can cite a source. If you have a complete Western date, then enter that in the form of 4-digit year/2-digit month/2-digit day. If you only have a year or century then enter that. If you have only a Tibetan date, then enter that here instead.

Name Begin Certainty Range: If there is some degree of uncertainty about the begin date, enter that here. For example if your sources say it was some time within 10 years of 1450, you would enter Begin Date of 1450 and Certainty Range of 10 years.

Name End: If a name is no longer in existence, be as specific as you can in indicating the date at which the name ceased to apply. In asserting a date, make sure that you can cite a source. If you have a complete Western date, then enter that in the form of 4-digit year/2-digit month/2-digit day. If you only have a year or century then enter that. If you have only a Tibetan date, then enter that here instead.

Name End Certainty Range: If there is some degree of uncertainty about the end date, enter that here. For example if your sources say it was some time within 10 years of 1450, you would enter End Date of 1450 and Certainty Range of 10 years.

Instance Date: Use this field to indicate a date that the feature name is known to be applicable when the date is neither a beginning or ending date. This can be seen as a snapshot; for instance if a source indicates that a feature was called by a certain name in 1796 but the source does not specify when the name began or the feature was founded, merely enter the date referenced.

Date Free Text: This is field in which general dates can be entered, such as "19th Century" or "Early 19th Century", etc.

Period: The period is to be used if you only know a period during which the name was applied – eg. if your sources indicate that the name "Rasa" was in use during the reign of srong brtsan sgam po or during the chos ldan rgyal rabs period. We eventually probably need to make this a controlled vocabulary.

Sources: See the note on Bibliographic Sources above.

Is Name Current: If you are able to ascertain from your sources whether the name is currently in use, then indicate that here. Choices are “yes”, “no”, and “unspecified”.

Etymology: This should be filled out for each name if possible. Provide an etymology of what the place name means. Remember to use THDL Extended Wylie for Tibetan words, and NOT to use phonetics.

Sources: Indicate the sources used in creating the etymology entry.

2. Feature Times

This section addresses the temporal range of the feature itself - i.e. a start and end date - in contrast to the dates for any given names attached to the feature.

Feature Begin : Be as specific as you can in indicating the earliest instance of the feature in the current entry. In asserting a date, make sure that you can cite a source. If you have a complete Western date, then enter that in the form of 4-digit year/2-digit month/2-digit day. If you only have a year or century then enter that. If you have only a Tibetan date, then enter that here instead.

Feature Begin Certainty Range : If there is some degree of uncertainty about the begin date, enter that here. For example if your sources say it was some time within 10 years of 1450, you would enter Begin Date of 1450 and Certainty Range of 10 years.

Feature End : If the feature is no longer in existence, be as specific as you can in indicating the date at which it ceased to exist. In asserting a date, make sure that you can cite a source. If you have a complete Western date, then enter that in the form of 4-digit year/2-digit month/2-digit day. If you only have a year or century then enter that. If you have only a Tibetan date, then enter that here instead.

Feature End Certainty Range : If there is some degree of uncertainty about the end date, enter that here. For example if your sources say it was some time within 10 years of 1450, you would enter End Date of 1450 and Certainty Range of 10 years.

Instance Date : Use this field to indicate a date that the feature is known to exist when the date is neither a beginning or ending date. This can be seen as a snapshot; for instance if a source indicates that a feature was in existence in 1796 but the source does not specify when it began or ceased to exist, merely enter the date referenced.

Date Free Text : This is field in which general dates can be entered, such as "19th Century" or "Early 19th Century", etc.

Period: The period is to be used if you only know a period during which the name was applied – eg. if your sources indicate that the name "Rasa" was in use during the reign of srong brtsan sgam po or during the chos ldan rgyal rabs period. We eventually probably need to make this a controlled vocabulary.

Sources : See the note on Bibliographic Sources below.

Is Feature Current : If you are able to ascertain from your sources whether the feature currently exists or not, then indicate that here. Choices are “yes”, “no”, and “unspecified”.

3. Feature Types

Features can be classified into specific types - mountains, monasteries, cities, and so forth. The types are specified in THDL's evolving Feature Thesaurus. This classification allows users to view all features of a given type, or use that as a way to constrain searches.

  • Feature Type (Wylie): We are currently working on an extensive typology/thesaurus of features that are particularly relevant to Tibet and the Himalayas. Your entries and input will provide much needed data. For now the choices are in Wylie. Here are the choices in alphabetical order, with translation:
  • Type Begin: Be as specific as you can in indicating the earliest instance of the type in the current entry. In asserting a date, make sure that you can cite a source. If you have a complete Western date, then enter that in the form of 4-digit year/2-digit month/2-digit day. If you only have a year or century then enter that. If you have only a Tibetan date, then enter that here instead.
  • Type Begin Certainty Range: If there is some degree of uncertainty about the begin date, enter that here. For example if your sources say it was some time within 10 years of 1450, you would enter Begin Date of 1450 and Certainty Range of 10 years.
  • Type End: If a feature type is no longer in existence, be as specific as you can in indicating the date at which the type ceased to apply – an example would be a feature that was a monastery, which was then turned into a granary. In asserting a date, make sure that you can cite a source. If you have a complete Western date, then enter that in the form of 4-digit year/2-digit month/2-digit day. If you only have a year or century then enter that. If you have only a Tibetan date, then enter that here instead.
  • Type End Certainty Range: If there is some degree of uncertainty about the end date, enter that here. For example if your sources say it was some time within 10 years of 1450, you would enter End Date of 1450 and Certainty Range of 10 years.
  • Instance Date: Use this field to indicate a date that the feature type is known to be applicable when the date is neither a beginning or ending date. This can be seen as a snapshot; for instance if a source indicates that a feature was of a given type in 1796 but the source does not specify when the type began or ended, merely enter the date referenced.
  • Date Free Text: This is field in which general dates can be entered, such as "19th Century" or "Early 19th Century", etc.
  • Period: Though there are currently no existing choices in the dropdown menu, the period is to be used if you only know a period during which the type was applied.
  • Sources: See the note on Bibliographic Sources below.
  • Is Type Current: If you are able to ascertain from your sources whether the type is currently in use, then indicate that here

4. Feature Ids or Geocodes

This documents all relevant identification numbers for the feature used in government systems, or other important databases. In addition, it provides a unique Feature ID# within THDL. The THDL Feature ID is used in all other parts of THDL to refer in short hand to this feature, such as in citing the place where an photograph was taken i the image database, the birth place of an author, and so on.

  • THDL ID: This is generated automatically and is the same ID number that appears at the top of the entry form.
  • Other ID: Multiple IDs can be created for a feature; each horizontal line of boxes contains the metada about a given ID.
  • ID Type: Enter the type of ID number. The editable set of choices at this point includes:
    • THDL ID
    • Extended GB: This is the extension of the Chinese GB code as developed by Karl Ryavec and THDL; it applies to administrative features in China.
    • Postal Code
    • Address
  • ID Sources: See the note on Bibliographic Sources above.

5. Feature Locations

This provides details about the feature's location, such as the GIS (Geographical Information Systems) readings on latitude, longitude, and altitude, or more imprecise data such as a textually expressed description of its location from contemporary observation or textual sources.

The majority of features we will be documenting with this entry form are point features, or spot features. They are so termed because they are the types of features that exist as specific points on a map (such as monasteries, hermitages, buildings), as opposed to polygons, such as provinces, counties, etc. In the case of spot features, we have "point" data; for the larger features of the "polygon" variety, we provide a space to enter bounding box details.

  • Longitude (X) Degrees: Enter the longitude in degrees.
  • Longitude (X) Decimal: If one's reading is in decimal degrees, with a degree value followed by decimal point, followed by other values (commonly 5-digits), then enter the value at the right of the decimal.
  • Longitude (X) Minutes: Enter the minutes longitude.
  • Longitude (X) Seconds: Enter the seconds longitude.
  • East/West (X): Enter whether the value is east or west of the prime meridien (our values will most likely be in the East.
  • Latitude (Y) Degrees: Enter the latitude in degrees.
  • Latitude (Y) Decimal: If one's reading is in decimal degrees, with a degree value followed by decimal point, followed by other values (commonly 5-digits), then enter the value at the right of the decimal.
  • Latitude (Y) Minutes: Enter the minutes latitude.
  • Latitude (Y) Seconds: Enter the seconds latitude.
  • North/South (Y): Enter whether the value is north or south of the Equator (our values will most likely be in the North.
  • Point Time: Enter the time for which the point coordinates are valid.
  • Point Sources: See the note on Bibliographic Sources above.

For certain features, we will be able to obtain coordinates for a bounding box, usually in the form of at least 2 corners. Where you have corner coordinates, enter them here.

  • Northwest Longitude (X): Enter the longitude of the Northwest corner in decimal degrees format.
  • Northwest Latitude (Y): Enter the latitude of the Northwest corner in decimal degrees format.
  • Southwest Longitude (X): Enter the longitude of the Southwest corner in decimal degrees format.
  • Southwest Latitude (Y): Enter the latitude of the Southwest corner in decimal degrees format.
  • Northeast Longitude (X): Enter the longitude of the Northeast corner in decimal degrees format.
  • Northeast Latitude (Y): Enter the latitude of the Northeast corner in decimal degrees format.
  • Southeast Longitude (X): Enter the longitude of the Southeast corner in decimal degrees format.
  • Southeast Latitude (Y): Enter the latitude of the Southeast corner in decimal degrees format.
  • Box Basis: Enter the basis for which the box coordinates were derived - such as a GPS unit measured at each corner of a bounding wall.
  • Box Time: Enter the time which the readings were taken.
  • Box Source: Enter the source for the coordinates.

ALTITUDE

  • Altitude: Enter the altitude for the feature. If you need to specify minimum, maximum and average altitudes, follow the link to "Add additional SPATIAL details…"
  • Altitude Time: Enter the time which the readings were taken.

Altitude Source: Enter the source for the altitude.

6. Feature Relationships

This specifies relationships that exist between the feature and other features documented in the Gazetteer. The most important relationship to document is "part of", in which we indicate what feature a given feature is part of. For example, a "township" can be specified as "part of" a country which contains it. For example, 'bras pungs Monastery is in Lhasa; therefore when creating the Gazetteer entry for 'bras pungs, you would indicate that it is "part of" Lhasa. In terms of directionality, we only specify when something is "part of" something larger, but not the larger thing "containing" the smaller thing. You only need to specify the next level up which contains it, and then that next level is contained by other features - relationships will be implicitly inherited.

FMP: For example, if the entry we are creating is for se ra monastery, and we know that it is part of Lhasa, then we can go to the section below and choose China at the country level, Tibet at the province level, lha sa at the prefecture level (corresponding to Lhasa Municipality), and then lha sa at the county level (corresponding to Lhasa City). As we choose a feature from the dropdown menu, the THDL ID for that feature appears at the right. That is the ID of the Related Feature.

  • Related Feature ID: Enter the THDL ID for the feature whose relationship you are documenting. Enter the ID of the most granular feature you can for the "part of" relationship -- if you can find a relationship at the township level, then enter that. Each horizontal line of white boxes is the data about the relationship. If you have multiple relationships, enter one per line.
  • Relation Type: Enter the type of relationship. The current choices are:
    • part of
    • near
    • adjacent
    • intersects
    • other
  • Relation Begin: Be as specific as you can in indicating the beginning of the relationship in the current entry. In asserting a date, make sure that you can cite a source. If you have a complete Western date, then enter that in the form of 4-digit year/2-digit month/2-digit day. If you only have a year or century then enter that. If you have only a Tibetan date, then enter that here instead.
  • Relation End: If a relationship is no longer in effect, be as specific as you can in indicating the date at which the relationship ceased to apply. In asserting a date, make sure that you can cite a source. If you have a complete Western date, then enter that in the form of 4-digit year/2-digit month/2-digit day. If you only have a year or century then enter that. If you have only a Tibetan date, then enter that here instead.
  • Instance Date: Use this field to indicate a date that the feature relation is known to be applicable when the date is neither a beginning or ending date. This can be seen as a snapshot; for instance if a source indicates that a feature was part of another feature in 1796 but the source does not specify when the relationship began or ended, merely enter the date referenced.
  • Date Free Text: This is field in which general dates can be entered, such as "19th Century" or "Early 19th Century", etc.
  • Period: Though there are currently no existing choices in the dropdown menu, the period is to be used if you only know a period during which the relationship was applied.
  • Related Feature Note: Enter any additional information about the feature relationship here.
  • Sources: See the note on Bibliographic Sources below.
  • Is Relation Current: If you are able to ascertain from your sources whether the relationship is currently in use, then indicate that here.

7. Feature Descriptions

This is a short one paragraph summary and a longer descriptive note (from a paragraph to page) describing the feature. Any description more detailed should not be contained in the gazetteer, but rather in associated specialized databases.

  • Feature Summary: This is a single paragraph overview of the feature in narrative terms. It provides a brief indicator of the type of place’s identity and significance. For granular levels of places, it could be a particular shore of a lake, or even a particular room in a place, or a wing of a monastic complex.
  • Summary Editor: Choose the creator/editor of the summary. If the name is not there, then add it to the list.
  • Summary Edit Date: Enter the date the summary was created/revised in the form of yyyy/mm/dd.
  • Feature Description: This description is more detailed than the summary, ranging from one paragraph to maximum of one page. It provides a brief indicator of the type of place’s identity and significance.
  • Feature Description type: choose from a drop down list - General, Historical, Contemporary, and Physical Setting.
  • Description Editor: Choose the creator/editor of the description. If the name is not there, then add it to the list.
  • Description Edit Date: Enter the date the description was created/revised in the form of yyyy/mm/dd.
  • Sources: You must create a bibliographical entry for your source in the THDL Bibliography tool (external link: http://datastore.lib.virginia.edu/tibet/spt/) if no such entry exists. The form in which you should enter the sources is THDL ID, followed by the page, then the line, eg: "THDL#340 29.6-8". In the case of multiple sources, for separate each source cited with a semicolon (";")
  • Feature Notes: Enter any additional notes you may have about a feature.

Bibliographic Sources

Although ultimately all bibliographical references will be based on an ID generated by THDL's online Bibliography tool (called SPT - external link: http://datastore.lib.virginia.edu/tibet/spt/), using SPT requires some training and careful study of its manual in order to ensure consistent entries that conform with our standards. For that reason, unless you have a log-in ID and training in using the Bibliography tool, here is how we advise you to identify bibliographical sources in your references in this Gazetteer entry form:

  • Create a separate document (such as a Microsoft Word, Excel or simple text document) that you will use for maintaining your bibliography.
  • Use the same user ID that you are using with the Gazetteer entry form in order to make an ID for each bibliographical entry. An example would be calling a book that I use as a resource: "dln4n_spt#001". In your bibliography document you should keep track of bibliographic data for each identified entry. The most important data to keep track of is:

**Title **Author **Publisher **Publication Date *་When you enter a Source in the Gazetteer entry form you should use the ID, followed by the page, then the line, eg: "dln4n_spt#001 29.6-8". This would mean lines 6 through 8 of page 29 of the source that is for the time being known as "dln4n_spt#001". *་In the case of multiple sources, separate each source cited with a semicolon (";") If the reference already exists in SPT, here is how to get the THDL ID: *་Click the link for "Full Record". *་At the end of the URL, you will see "?ResourceId=" followed by a number, which is the Source ID, for example: "?ResourceId=356". *་The form in which you should enter the sources is THDL#, followed by the page, then the line, eg: "THDL#356 29.6-8". In the case of multiple sources, separate each source cited with a semicolon (";")

Provided for unrestricted use by the external link: Tibetan and Himalayan Digital Library