To start exploring the database, please visit the database section and click on an item on the left panel. In the follwoing discussion, a token is defined as a text unit delimited by a white space, as appearing in the transliterations used as input for the project. Information on the individual textual tokens is displayed in the main panel on the right. This is arranged in 6 tabs, namely:

• Palaeography: this tab contains palaeographical variations of the token being browsed.
• Transliteration data: this tab show the context where individual tokens occur.
• Variations: this tab lists the variation patters attached to individual tokens. Consider two tokens, X and Y, each having variants ~a and ~b. In such scenario, four variations are possible, namely:

  X~a Y~a
  X~a Y~b
  X~b Y~a
  X~b Y~b

Variations are key in order to understand whether or not two variants represent in fact the same sign.
• Cluster data(1): a cluster is defined here as the set of all tokens in a given textual unit (line or textual box), arranged alphabetically. Note that brakes within lines are ignored, which may lead to artificial conflation of clusters. For instance, the following input strings are considered identical in terms of cluster formation:

  [...] X Y
  X [...] Y
  X Y [...]
  X Y

  Philological competence is required to disentangle the matter. In addition, numbers are also ignored: "1 X Y" is reduced to "X Y" while processing, thus avoiding possible variantions with "2 X Y", "3 X Y", etc. which are unwanted here.
• Cluster data(2): same as cluster data (1), except that token variations are ignored (X~a and X~b are considered identical). This does not imply that X~a and X~b actually have reading X. The order is again alphabetical.
• Graphemics: this tab contains frequency data attached to the token being browsed.