Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Language configuration is done via System Tools → Language. The role 'Editor_SystemTools_MetadataLanguage' is needed to gain access to this.

Image RemovedImage Added

There are just 2 options here:

  • Add a language by clicking the ‘add’ button and select a language.

  • Deactivate a language by clicking the button next to a language shaped like an 'x'.

Image RemovedImage Added

Info

Adding a language in an environment with large amounts of assets and metadata can take quite long to complete. Expect anywhere between 10 minutes and 1 hour for this in such cases. It is therefore recommended to add new languages from the beginning of a DAM systems life.

Each language in a system will add a performance overhead in all language translated parts of the system and this will be progressively noticeable. To avoid severe performance degradation it is recommended to not have more than 10 active languages at a time.

Info

Deactivating a language does not delete the data associated with the language.

Repopulate search caches after adding new languages

To improve query performance a number of search caches are supporting the system. These caches are not updated automatically as this can take a long time and it may be wise to do this outside of office hours. To repopulate search caches individually navigate to System Tools -> Config Manager and select your product and version.

Then select the ‘searches’ tab and from here select a search in need of repopulation and click the 'Repopulate search cache' button. If the button is not present the selected search does not contain a freetext part and in turn does not have a search cache.

Image RemovedImage Added

To repopulate all search caches manually an url needs to be constructed like this:

Code Block
DAMURL/dmm3bwsv3/jobservice.js?method=GenerateAndPopulateAllSearches&force=true&accesskey=accesskey

Be aware this will force all search caches to be repopulated including Solr cores which on most customer environments not only takes many hours to complete but the DAM system will also be quite busy and therefore less responsive until finished.