...
DBmeta files are *.jsettings and should be in “Settings\Reader\DBMeta"
Columns filters
...
Limiting the Settings Scope
You may limit the settings by the following criteria. This way, you may have multiple meta-definitions that each is effective for a limited scope.
Key | Description |
|---|---|
WorkspaceName | WorkSpace(s) to which the settings will apply. |
TableFilter | Tables to which the settings will apply. |
ColumnFilter | Tables that contain the given columns (if - is given, tables that do not contain the relevant columns are considered). If more than one is given, the relationship is AND. |
| Code Block | ||
|---|---|---|
| ||
{
"Defines":[
{
"__type":"Geodi.Database.Meta.DBView, Geodi.Database",
"WorkspaceName":"0000-Promotional and Educational Videos",
"TableFilter":"*",
"ColumnFilter":"*",
"Columns":"-FILEPATH,-ID,DATE,GEODIFILELINK"
},
]
} |
How rows appear in GEODI
...
Determining Row names
Each row is a document/content. GEODI behaves rows just like other documents. By default first text column is the name. The name is the content used by doc:(…) query.
You can change row names for each table using DisplayNameMacro. You can also use other columns in the title macro. Macro rules are given at the end of the page.
...
When there is no file name in the table in the database, you can build one using the
FileNameColumnMacrovalue. There are two examples below. The first example is a simple one. the second one assumes that some rows do not have an extension value.FileMemoColumnis the file stream.Code Block language json { "Defines":[ { "__type":"Geodi.Database.Meta.DBSubContent, Geodi.Database", "TableFilter":"CMS.FileContentCore", "IDColumnMacro":"[FieldId][VersionNumber][MinorVersionNumber]", "FileNameColumnMacro":"[Internalid][Extension]", "FileMemoColumn":"FileContent" } ] }In the following example, the
Extensioncolumn is assumed to have the file extension. Some rows may have empty values. We assumed that the file is PDF if no extension. The macro might have returned an empty string to skip the files.Code Block language json { "Defines":[ { "__type":"Geodi.Database.Meta.DBSubContent, Geodi.Database", "TableFilter":"Documents", "IDColumnMacro":"[DocumentsID]", "FileNameColumnMacro":'=string.Concat(d["Internalid"],"-",d["CreateDate"],string.IsNullOrEmpty(d["Extension"])?".pdf":d["Extension"])', "FileMemoColumn":"File" } ] }
Indexing
...
with File
...
Paths
...
You can also index files specified by file links in a record. (CSV files are not supported).
Key | Description | ||
|---|---|---|---|
| A macro that calculates the directories where files are located. This macro can be the value directly in a field (e.g. PATH), or it can be a path calculated in combination with other fields of the record.( Example: column name PATH on VT) |
| If there is more than one file in the file path, you can give the bracket character this wayfull paths for the files. This files becomes child of of the rows. |
| If there is more than one file in the file path, this is the splitter character. |
| Code Block | ||
|---|---|---|
| ||
{
"Defines":[
{
"__type":"Geodi.Database.Meta.DBSubContent, Geodi.Database",
"FileFullPathColumnMacro":"[PATH]",
"FileFullPathColumnSplitter":"|"
},
{
]
} |
Specifying a Primary Key Column
...
"__type":"Geodi.Database.Meta.DBSubContent, Geodi.Database",
"FileFullPathColumnMacro":"//server/files/[PATH][FILE].[EXTENTION]",
"FileFullPathColumnSplitter":","
},
{
"__type":"Geodi.Database.Meta.DBSubContent, Geodi.Database",
"FileFullPathColumnMacro":"//server/files/[ID].tif",
"FileFullPathColumnSplitter":","
}
]
} |
Specifying a Primary Key Column
Each table requires a primary column for scanning and versioning changes. GEODI sets the ObjectID value by default. You can specify a different column with the definition described here.
...
| Code Block | ||
|---|---|---|
| ||
{
"__type":"Geodi.Database.Meta.DBPKey, Geodi.Database",
"TableFilter":"tablo1",
"KeyColumns":"id"
}, |
Indexing the result of
...
an SQL statement
You create a new table named NewName with the SQL key. The SQL statement must be compatible with the relevant DBMS.
Alternatively, you can specify the value of KeyColums in SQL by writing "as P_KEY" or "as OBJECTID" in the column.
This feature is valid for file-based ones such as *.xDeceConnection and MDB.
Standard SQL must be used.
It should be ensured that there is no more than one repeating column with the same name in the result of the SQL statement.
...
Adjusting the Way Records Look
The html HTML template you provide with the "TemplateName" key will determine the appearance of the records that meet the criteria. This template with the ".html" extension should be under the Templates folder under the "DBMeta" file, and the generated meta should be saved under the "DBMeta" folder.
Using TemplateName gives you visual flexibility , but can be a performance penalty.
...
You should set ContentReaderEnumerators → Your Database → EnableAutoFieldIndex to true in the project detail settings and rescan your project. Rescanning can take time with big data, so planning it is better to plan it from the beginning is better.
If we are scanning the database connection to GEODI on a file basis, we cannot use this setting.
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, each discovery for a DB will have the column name with it.
...
...
Sampled 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.
...
GEODI samples random N records per table.
The sampling settings will be effective for File-based databases if this setting is used in folder sources. such as *.xlsx, *.mdb, *.accdb
...
.
...
Make column names multilingual and define aliases
...