Primary features of Meta Manager include:

Meta Manager Addresses Many Metadata Management Issues A Comprehensive Metadata Management Application

• Support for direct integration into existing Oracle, ESRI SDE, Microsoft Access and Microsoft SQL Server inventory and metadata databases without requiring modifications or changes to the data structures.
   
• A comprehensive install script that includes options for installing and configuring the YAZ-Z39.50 server software; populating relational databases and installing the Meta Manager Administrative interface.
   
• Operation on UNIX and Windows 95/98/NT/2000 platforms.
   
• Meta Manager LE (Lite Edition) has been created to provide suppliers with limited budgets and resources an entry into the clearinghouse model. The Meta Manager LE product is limited by the number of records that can be included in the product and will only connect to Microsoft Access databases within a Windows NT environment. Data providers with limited resources are able to implement a searchable small inventory collection online, without the need for them to set up an existing database schema in MS Access. This is accomplished using a Meta Manager Wizard facility.
   
• ODBC driver support providing connectivity to many relational database engines.
   
• The Percipio PHTML engine for fast SQL-access querying and retrieval.
   
• Metadata mapping and inclusion of fields that are not included in the target database.
   
• Keyword look-up for selecting and identifying keywords associated with collections in the target database.
   
• A master collection definition facility for defining metadata fields, functions and defaults that can be applied to all collections of information available for searching and retrieval. Changing the master collection will cause all related global variables to be updated automatically.
   
• Provides the flexibility to render metadata entries using ASCII, HTML, SGML and XML display formats.
   
• Enhanced SQL syntax checking for maintaining the integrity of the targeted databases.
   
• Creation and population of metadata databases by selecting the metadata standard.
   
• Internet and FGDC Clearinghouse connectivity server software.
   
• Enhanced Support for GRS-1 and USMARC. Meta Manager GEO servers may transfer records in up to three record syntax's:
   
1. Simple Unstructured Text Record Syntax (SUTRS) -- REQUIRED
   
   In SUTRS, the formatting of the record contents is handled by the server and the client receives a record which is defined by the user to be in verbose text with long metadata tag names (the default presentation used by the FGDC metadata standard), SGML and HTML. Both SGML and HTML are formatted ASCII text documents which make them amenable to distribution via SUTRS.
   
   Client-side applications can be used to read the markup in the retrieved document and display it accordingly using SGML or HTML. Most World-Wide Web browsers can display HTML-formatted files and some can launch an SGML document viewer when an SGML mime-type is encountered.
   
   Negotiation between the client and the server can dictate which format is generated by the server as the user-preferred format for the downloaded document.
    
2. Generic Record Syntax (GRS-1) -- OPTIONAL
   
   Alternatively, GRS-1 can be used to encapsulate more complex bundles of information including images, related documents, video, or other ancillary information for further processing by the client. GRS could also be used to encapsulate the SGML along with the reference to -- or even inclusion of -- a DTD.
    
3. USMARC -- OPTIONAL
   
   MARC is an acronym for MAchine-Readable Cataloging. The standards for the representation and exchange of bibliographic, authority, classification, holdings, and community information data in machine-readable form in the United States are the five USMARC communication formats: Bibliographic Data, Authority Data, Classification Data, Holdings Data, and Community Information.
   
   Each separate MARC format provides detailed field descriptions and guidelines for applying the defined content designation and identifies conventions to be used to ensure input consistency.
   
   The server requirement to support the USMARC record syntax is concerned with communicating the record in USMARC record syntax on request from the client
   .