Page Comparison

GEODI can also evaluate databases, i.e., structured data. Databases and their file information (including embedded) can be indexed (all tables and rows). With simple rules, you can limit tables, rows, or fields and set how rows are displayed to the user.

Database Clients

Some DBs may require a driver on the server where GEODI is locatedUse Project Wizard/Database connection to define the connection.

...

Use “New Connection” to choose the database and define the connection string. ( This dialog only opens if you are logged into the server)

Some databases may require an extra driver to be installed. Please check the lşiste below.

How to Connect Database Source

1. You can start by selecting the Database Source with the Project Wizard/Database.

   1. Image Removed

2. You must select the database you want to define with Define Connection from the screen that opens.

   1. Image Removed

How to Define Tabular Data

There are multiple ways:

...

Alternative Connection Methods

Other than using the project wizard

1. File-based ones such as SQLite, MDB, and AccDB are indexed automatically . Rule files/DBMeta are considered if defined.

2. Excel files are not recognized as structured data by default. But we can do this with appropriate meta and settings.

3. With Project Wizard/Database source we can connect to all listed DBMSs. Rule files/DBMeta are taken into account if defined. In this structure, desired tables and columns can be selected and SQL statements can be written. Views are supported.

4. Settings made with Project Wizard/Database can be stored. A structure in *.xDeceConnection format is now recognized as file based. This structure has multiple benefits.

   1. It is portable. This means you can use the same file in other GEODIs or the same GEODI in other projects.

   2. It is secure. Depending on the system settings security level settings, the password/username inside the connection cannot be known.

   3. Some DBMeta capabilities mentioned on this page only work this way.

How to Index?

Databases can consist of many tables. By default, GEODI traverses all tables and indexes all rows. System administrators can make definitions to restrict tables and rows through GEODI. If desired, "view(s)" can be defined and how GEODI will see the database can also be defined. Many different systems/formats such as Oracle, SQL Server, Postgres, Mysql, sqlite, access, shapefile, excel are supported.

There is no need to define for file based ones like sqlite and access. These files are automatically indexed when found in any source.

You can also store the connection definitions you create with GEODI as *.dececonnection and let GEODI scan this content like any other file.

IIndexed tables and rows are not taken into account in the crawl for changes process as long as they do not change. Changed rows will be automatically versioned. 

1. Tables to be crawled must have a primary key. You can remove this constraint with a setting, but the crawl changes or versioning features will not work for tables without a primary field.

2. . If you do not want Geodi Table objects in the search results, but only records, DisableIndexTables should be set to True in the Enumerator Detail settings.

3. Files embedded in tables or linked within tables can also be included in indexing. How these features work is explained on this page.

4. You overcome the limited search capabilities offered by the software that creates the database

Changing Table Indexing Settings

• You can change the default behavior with jsettings settings files under Settings\Reader\DBMeta. Within the same settings file you can apply different settings for different tables or projects as shown in the example.

Separate setting types require a separate __type key.

Example:

...

...

1. when found in a directory and don't have a password. You may define DBMeta for them.

2. You must use Project Wizard for Excel files to be indexed as structured content.

3. Settings made with Project Wizard/Database can be saved in *.xDeceConnection format. These files are automatically processed. It is a portable and secure way of defining connections.

Indexing DBs

1. The default behavior is to crawl all tables and rows.

2. Tables must have primaryKey by default. You may choose to index tables w/o a primary key also.

3. You may choose a sampling mode, as only the selected number of rows is indexed in each table.

4. You may choose a subset of tables.

5. You may limit columns by their names.

6. You may define SQLs to change content to be indexed

7. Embedded files are indexed with proper definitions

8. File paths are processed with proper definitions

9. If rows have some permission information you may utilize it with proper definitions.

10. When you search in GEODI, Each row is content. You may define the name and appearance of a record database or table-wise.

DBmeta is a way to change all behavior here by database and/or tablewise. This page contains necessary information about how DBmetas are defined.

DBmetas are jsettings files under “Settings\Reader\DBMeta”

Columns filters

Limit indexing by table or column.

{
   "Defines":[
      {
         "__type":"Geodi.Database.Meta.DBRowDisplayNameDBView, Geodi.Database",
         "WorkspaceName":"0000-Promotional and Educational Videos Educational Videos",
         "TableFilter":"*",
         "DisplayNameMacroColumnFilter":"[TITLE]*",       }  
  ]
}

With the values in the table you can limit the scope of the settings. For all settings, you can specify all with "*", exclude with "-" and considere with ",".

...

Key

...

Description

...

WorkspaceName

...

WorkSpace(s) to which the settings will apply.

...

TableFilter

...

Tables to which the settings will apply.

...

ColumnFilter

...

       "Columns":"-FILEPATH,-ID,DATE,GEODIFILELINK"
      },
   ]
}

How rows appear in GEODI

In databases, each record appears on a record-by-record basis. The default title is the first text column value. You can change this for each table individually using DisplayNameMacro. You can also use other columns in the title macro. Macro rules are given at the end of the page.

{
   "Defines":[
      {
         "__type":"Geodi.Database.Meta.DBRowDisplayName, Geodi.Database",
         "DisplayNameMacro":"[TEXT4]/[TEXT2]-[TEXT3]"
      }
   ]
}

...

Indexing files embedded in tables

 Geodi can scan files that have with file paths in the database or are embedded in the database as blobs. This document explains how to make the necessary settings. 

...