Encrypted documents are now reported more clearly in the logs, and only at level FINE.

Document to Database now uses a specific JChemProperties table also when using the JChem Oracle cartridge database type. This avoids interference with other instances of JChem.

A new configuration layout was introduced. All configuration files are now stored inside a directory. The main configuration file (d2db.conf) contains only the essential properties and is therefore much simpler, while optional feature groups can be configured in separate files.
When using the default name "conf" for the configuration directory, d2db commands can now be called directly without repeating the configuration name each time, for instance: "d2db index <folder>".

Filesystem indexing would fail on directories without read permissions.

For documents with no title in the metadata in the file itself or the source repository, the path is now used as the title instead of having an empty title.

Installation of d2db with the JChem Oracle Cartridge is simplified, in particular by better logging and error messages.

Logging messages are improved to facilitate investigating problematic documents.

Indexing of Office documents with a Last-Author but no Author was failing.

Passwords in Oracle JDBC URLs are now hidden as *** in logging output for confidentiality.

Corporate IDs (registry numbers) can be converted by defining a regular expression and a database SQL query to convert them to structures. See the sample configuration file for instructions.

Performance when using the oracle cartridge was gradually degrading over time, when indexing a large number of documents (for several hours). This has been fixed, performance now remains constant.

Document to Database now uses a specific JChemProperties table, to avoid interference with other instances of JChem.

The connection to the database was optimized to improve speed. Please note however that performance can still degrade for tasks running for several hours. It is currently advised to split such tasks into smaller ones, as that will lead to shorter overall running time. This issue will be fixed in a future release (it has been fixed in version 14.7.7).

d2db can now index a set of documents stored in a filesystem. Only modified files are processed during reindexing.