As part of the Elastic search integration, Digizuite provides a administration dashboard for managing ad troubleshooting Elastic.
This view is protected by the following role
Can_Admin_Accelerated_Search
Which means the user must be assigned a group that has that role or directly have the role assigned.
To access the administration dashboard navigate to General Settings → Accelerated Search Status in the top right corner of the Media Manager (e.g. media.company.com/settings/accelerated-search).
The Administration dashboard looks as follows
And provides the user the ability to
Reload the store information
Start a complete reindexing
Force schema check
Remove all data
Load a specific document (i.e. asset)
Re-index a specific document.
Reloading the store information
A store is a Digizuite invented term which encapsulates multiple indexes. We are maintaining two indexes
Read index
Write index
Essentially they are exactly what their name indicates. A index for reading and one for writing. The main reason for doing this is clear when we rebuild the entire index as the is conducted on the Write index, which means we can clear it out and rebuild everything without having no assets available during the time it takes to rebuild.
Therefore all the Reload store information button does is it reloads the store and thereby indices. Think of it as a refresh button.
Start complete reindexing
Start complete re-indexing will rebuild the index from scratch. This is the last resort reset everything button and it will take a little while to complete.
The progress can be tracked under General jobs.
Force schema check
A index is defined by a schema, which is a definition of what properties the index holds. Digizuite indexes every metadata field in the system and some asset related system fields.
If the metadata configuration changes, it means the schema also changes (e.g. a new field is added, then it also has to be indexed).
This happens automatically in Digizuite, but should this fail for some reason, then the force schema check button can be used for force a validation of the schema.
Load document
This button uses the input field Document Id which takes an assetid. It loads the entire content in the index for that asset and can be used to troubleshoot if something does not work as expected
Re-index document
This button uses the larger text input field and takes an assetid. The button initiates a re-index of the data for the specific asset. This can be used if something comes out of sync.