DC 6.0 Administration dashboard in Media Manager

Owned by Rasmus Hjelmberg Duemose Hansen
May 13, 2024
2 min read

As part of the Elastic search integration, Digizuite provides a administration dashboard for managing and 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

This provides the user the ability to

  • Reload the store info

  • Start a complete reindexing

  • Force schema check

  • Remove all data

For a specific item

  • Load document (i.e. asset)

  • Re-index a specific document

Reloading the store information

A store is a Digizuite term which encapsulates multiple indexes. A store maintains two indexes

  • Read index

  • Write index

As the names indicate there is an index for reading and one for writing. The main reason for 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” during the rebuild as the read index is used.

Reload the store button 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. Use this as a last resort as it resets everything and it will take a 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 then the schema also changes (e.g. a new field is added, then it also has to be indexed).

This happens automatically, but should this fail, then the Force schema check button can be used to force a validation of the schema.

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

The Load document button uses the input field Document Id and loads the entire content from the index for 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

The Re-index document button uses the larger text input field and takes an 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.