TagGen Catalog™ / Tokens & Mapping
The original metadata search engine
HiSoftware TagGen Catalog comes with a sophisticated metadata mapping feature and complete Token Support. 

Token Support

• Strict
  Strict Token Support is simple, it states that a token must be found in the file being indexed in order to add the file to the catalog.
  
  Token Example: <meta name = "x" content = "y" z='1'>
  The meta name in this case is derived from the "Z" Element and not the meta name. This provides the highest amount of interoperability between sites with different metadata schemas.
   

• Strict (Multi)
  Strict (Multi) is the same as Strict, except it supports multiple "Z" Elements for a more flexible indexing.
  
  Token Example: <meta name = "x" content = "y" z='1,2'>
  This allows a single tag to represent to possible Token variables so that a single tag set of information can represent multiple "Z" Elements.
   

• Loose
  In Strict Token Support, a token must be found to index the document. In Loose, the catalog supports tokens. But if a token is not found, it looks for a meta name equivalent for indexing. This allows for support of cataloging sites which do not use tokens. 
  
  Order of Importance/relevance
  If a Token is found, use that value for the catalog value, if it is not then look for a match on the meta name value.
  
  Why Loose?
  This allows for a blended catalog of documents that do and do not have the facility for Implementing Tokens!

Mapping Support

The Mapping Feature Supports maps metadata maps that control the spider and method of indexing. A Map supports a one to many relationship. 

In the Above table we demonstrate mapping support. In the first two lines we show how French and Spanish equivalents for Title can have their values added to the TagGen Catalog Catalog. Like Tokens this example shows Language Independent Querying. But more importantly it allows for the traversing of Dislike Schemas.

If the Engineering Section of a company is made up of Divisions they may add this in their metadata. The Marketing Division may call the same thing areas. So Example three shows how fields with like meanings can be mapped to a single field.

This allows for individual areas to use metadata for specific application or search reasons while still allowing for a mapping back to a company standard by the TagGen Catalog Engine with no user intervention or no need to index 100's of fields that mean the same thing!