New Feature: Advance through search or collection results from the Asset Detail page

As part of the January 23rd Digital Media Hub release, users have an easier way to navigate through their Digital Media Hub content. When viewing an Asset Detail page, a single click can load the next or previous asset in a users collection or search result. 

Once a user has navigated to an Asset Detail page from either a search result page or a collection they will see some subtle 'previous' and 'next' buttons above the media preview window. Clicking these will update the detail page with an asset based on the list of assets in the current collection, or the search results. The buttons are only active when an asset is available - for example when viewing the 'first' asset the 'previous' button is disabled. The buttons also support pagination, so if you are viewing the last asset on a page of results, clicking the 'next' button will load the first result from the next page. 

New Feature: Configure checkout display 

Support has been added for Digital Media Hub customers that want to simplify the checkout interface. Customers now have the option to remove certain inputs on the checkout page which include Delivery Filename, VAT and PO Number. Within the Digital Media Hub Admin App, the UI config now includes flags that can disable of these optional inputs. 

New Feature: Updated permissions for viewing assets in Core 

Distinct permissions exist for editing clip metadata and seeing an 'open in Core' link within Digital Media Hub. This allows administrators more granular feature control. The existing EditClips permission will still control if a user can edit metadata for an asset within Digital Media Hub. A new ViewCoreClips permission now controls the display of the 'open in Core' button within Digital Media Hub. This means that users who still require the 'open in Core' button will need the new permission added to their Role.

Optimize search response processing 

As part of the January 23rd Digital Media Hub release, enhancements have been made to reduce the search response time by optimizing the number of rendition checks. When the Digital Media Hub Asset service is constructing a search response, it no longer calculates the availability of comp renditions. The result of this optimization should be a 10% reduction in the overall response time.   

Did this answer your question?