Page Comparison

...

How to Define Tabular Data

There are multiple ways:

1. File based ones such as SQLite, MDB, 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.

...

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

...

When this feature is active Words that are recognized in the database and fall in the KLV will be written next to the column in which they are found.

...

Sampling Data Discovery in Databases

By default, GEODI discovers all database contents. You can optionally sample and explore your database contents, so you can save on scanning time and storage space.

• Project detail settings ContentReaderEnumerators → Veritabanınız → GenericSettings to add "DB.SamplingMode":100 Tables/Selected Table/SQL query 100 records are randomly process.

  • File-Based databases for use in Folder enumerator GenericSettings to add "DB.SamplingMode":100 Such as *.xlsx , *.mdb, *.accdb from all types 100 records per table are random processed.

...

Make column names multilingual and define aliases

If you want, you should make the following definitions.

1. "fields" must be included in resx file names. These files must be located in the globalization directory.

2. The name value used must be att{fieldname} and must match the one in the table. You must use the same key in different languages.

3. The value value contains alternative column names (alias). You can separate multiple alternatives with "|".

4. If any of the alias you use is the same as another column name, it will be ignored.

5. In multilingual representations, the first alias is taken into account.

myfields.resx

  <data name="att_{fieldname}" xml:space="preserve">
    <value>{alias1}|{alias2}|{alias3}</value>
  </data>
  
  <data name="att_EnvanterNo" xml:space="preserve">
    <value>Envanter Numarası|Envanter N.|Envanter Sırası</value>
  </data>
  <data name="att_ADI" xml:space="preserve">
    <value>Ad|Adı Soyadı|AdSoyad</value>
  </data>

...