As part of the Elastic search integration, Digizuite provides a administration dashboard for managing ad and troubleshooting Elastic.
| Info |
|---|
| Code Block |
This view is protected by the following role |
...
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 This provides the user the ability to
Reload the storeinformationinfoStart a complete reindexingForce schema checkRemove all dataLoad
For a specific item
Load 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 A store maintains two indexes
Read index
Write index
Essentially they are exactly what their name indicates. A As the names indicate there is an 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 “no assets” during the time it takes to rebuildrebuild as the read index is used.
Therefore all Reload 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 Use this as a last resort reset as it resets everything button and it will take a little while to complete.
The progress can be tracked under General jobs.
...
If the metadata configuration changes , it means then 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 Force schema check button can be used for to force a validation of the schema.
| Info |
|---|
If the schema check finds that an index is missing, then it’ll re-create it and start a complete reindex of it! |
Clear indexes
Remove all data will clear the indexes and should under normal conditions never be used. It is included as it can help in situations where issues are reported in the above functionality.
Load document
This The Load document button uses the input field Document Id which takes an assetid. It and loads the entire content in from the index for that asset and the given asset id. It can be used to validate that the index is up-to-date and/or troubleshoot if something does not work as expected.
Re-index document
This The Re-index document button uses the larger text input field and takes an assetid asset id. The button initiates a re-index of the data for the specific asset. This can be used if something comes out of sync.