...

We’ve also made some improvements for the retrievability of batches. When starting a batch, it’s now possible to add a tag to a batch. This makes it easier to follow up the batch in the list of batches. You can also filter on these tags in the list of batches to have a quick status update on the batch. On top of that, admin users can also filter on initiator and status of batches.

Another addition is the possibility to handle heavy batches. In the case that a large batch is having an impact on the performance of your MediaHaven environment, it’s possible to prevent further issues by lowering the priority of the batch, changing the worker deamon zone or canceling the batch. These functions are available via the API and are especially interesting for integrators.

You can find more information about batches on this page: /wiki/spaces/CS/pages/3500245010.

...

Do you want certain metadata to be immediately available when downloading assets? It is now possible to pre-define the name of the export file. By using the file name expression functionality, admin users can it’s possible to dynamically determine the filename of an export. For example: you can choose to combine the title and keywords of the asset. This gives you more context when further handling the downloaded file.

More information about the possibilities of this feature and how to set these filename expressions is available on this page: https://mediahaven.atlassian.net/wiki/spaces/CS/pages/3502768171/Export#Filename-Expression-24.3%E2%80%8B.

DoubleFields are now supported

MediaHaven2.0 now supports the visualization of DoubleFields. By supporting this field type, MediaHaven ensures an accurate representation of numerical data, crucial for assets that require high precision. An example is technical metadata from camera’s such as aperture or iso values.
Please contact our support team if you want to use DoubleFields in your MediaHaven2.0 environment. Please contact our support team if you want to start using this functionality.

Improvements for the position field

From now on, users can provide any addresses or location. These values will no longer be overruled by the API, that used to select the nearest existing address. This is especially interesting when indicating exact coordinates or a fuzzy address, like in the middle of a field. Another use case might be addresses that no longer exist but the link with an outdated address is obliged on assets for historical purposes.

...

• Status
  colour Green title handling failed browses

  When the system could not generate a browse of a media records, a message is shown on the list of representations with more information that no transformation could be made or that the transformation failed.

• Status
  colour Yellow title External source URL

  The validation of external source URLs is now handled asynchronously. This to avoid the REST API being blocked.

• Status
  title Permissions inheritance

  Permission inheritance is now forced between data objects and their underlying objects. More information is available on this page: /wiki/spaces/CS/pages/4251942913.

• Status
  colour Blue title Settings and management

  We’ve improved the navigation bar in the Settings & Management module. The available settings are now grouped more intuitively. All settings regarding user management are centralised in one menu. On top of that, it is now possible to add new users, groups and zones via the action in the top right-hand corner on the specific lists. It also still possible to add users, groups and zones via the “Add” button on top of the navigation bar.

• Status
  colour Red title improved thesaurus

  Retrieving thesaurus values when describing records is now a lot faster. This makes it easier for users to search and select the necessary values to continue describing records.

• Status
  colour Red title Improved reindexation

  The reindex process is now a lot faster. This means that changes to certain metadata fields or classifications are now handled more smoothly.

• Status
  colour Purple title Position field

  From now on, users can provide any addresses or location. These values will no longer be overruled by the API, that used to select the nearest existing address. This is especially interesting for addresses that no longer exist but the link with an outdated address is obliged on assets for historical purposes

  support for Double fields

  MediaHaven2.0 now supports the visualization of DoubleFields. By supporting this field type, MediaHaven ensures an accurate representation of numerical data, crucial for assets that require high precision. An example is technical metadata from camera’s such as aperture or iso values. Please contact our support team if you want to use DoubleFields in your MediaHaven2.0 environment.

Bug fixes

• [MH2.0] When changing the permissions of a serie an intellectual object, it is now possible again to perform actions on underlying dossiers and documents of that serieits underlying items.

• [MH2.0] Performing a search with quotation marks is possible again.

• [MH2.0] We have fixed a bug where users using SAML login where not logged out on first try.

• [MH2.0] The correct values of the “Authors” dropdown are shown when describing records. There are no longer doubles or values of other lists available in these dropdown menus.

• [MH2.0] When switching between list or grid view and map view on lists, the available filters and their values are adjusted based on the available records.

• [MH2.0] It is now possible again to click on URL fields that are used in a list. When clicking on the URL, the user is redirected to the corresponding web page.

• [MH2.0] When navigating back to the search results from the detail page of an object, the correct page in the list is shown. On top of that, the previously selected filter(s) or search values are still applied on the list.

• [Settings and management] Admin users can now edit the organisation preferences.

• [Submit with special characters in the comment] We’ve fixed a bug so that it is possible to submit an object when you enter special characters like ““ in the comment of your task.