3 Configuration - MM v4.11.0

Owned by Jens Fristed Navne (Unlicensed)
Last updated: Jan 04, 2018 by Mathias Mattson (MHM)
7 min read

3.0 Add new Media Manager version

After the instalaltion script has run, you need to add a new version of the Media Manager under the Parent (4.0.0) version:
In the DAM Center go to Config MnanagerĀ ā†’ Medida MangerĀ ā†’ 4.0.0.
Then on the main page in teh free text field add a name for the new version "Default" and thenĀ click the button "Create new version" - a new version of MM is created underneath the parent version.



3.1 Guest user access

The Digizuiteā„¢ Media Manager requires a backend user for accessing the API to collect configuration (required) and for ordinary guest user access (optional). Specify this user in the web.config file in the root website folder. Locate AppSettingsĀ guestUsernameĀ and guestPasswordĀ (md5) and enter credentials for a valid DAM user.

The guest user must belong to a group that defines the roles MediaPortal_UserĀ and MediaPortal_Collection. In standard Digizuiteā„¢ DAM Center there is already a user (Guest_be) and group (Contributor) for this.

Note

The guest user must be different from the social media user (product configuration).

By default, the guest user has write access to assets in the Digizuiteā„¢ Media Manager. You can change this behavior by following these three steps:

  1. Navigate to System tools ā†’Ā Users and groups ā†’Ā Users. Select Guest_be and open the Editor. Access the Standard tab and remove the Contributor group.
  2. Navigate to System tools ā†’Ā Config Manager ā†’Ā Digizuiteā„¢ Media Manager. Right click on Digizuiteā„¢ Media Manager and select Edit folder rights. Give read access to Guest_be to all menus and submenus.
  3. Navigate to Channels ā†’Ā Digizuiteā„¢ Media Manager. Right click on Digizuiteā„¢ Media Manager and select Edit folder rights. Give read access to Guest_be to all menus and submenus.

3.2 Template user

The Digizuiteā„¢ Media Manager requires a backend template user that defines roles when creating new users from self-signup. This user must be set in the ConfigManager of the Digizuiteā„¢ Media Manager in parameter User Template for Self Signup users.

  • Create a new backend user - we recommend template_user.Ā 
  • Put the new user in the "Contributor" group or alternatively another group with MediaPortal_CollectionĀ and MediaPortal_UserĀ roles.

Note: If using No verificationĀ sign up mode, make sure to check the ApprovedĀ checkbox on the template user. Likewise, the checkbox should be left unchecked for the other verification configurations.

3.3 Template user for collection sharing

The Digizuiteā„¢ Media Manager requires a template user that defines roles when auto generating users for collection sharing. This user must be set in the ConfigManager of the Digizuiteā„¢ Media Manager in parameter Template for auto created collection users.

  • Create a new user - we recommend Social_media_user. However, notice that this is not for sharing towards social sites.

3.4 User for social sharing

If configured (Sharing enabled), the application offers social sharing of assets and collections. The system needs a specific backend user to define rights and roles for that material. The system generates a time limited access key (Access key timeout for social sharing) from that user and distributes that key in sharing links.

Ā By default, the system defines a user called Social_media_userĀ which has very limited access. To edit this user, in Digizuiteā„¢ DAM Center, navigate to System tools ā†’Ā Local users and groups ā†’Ā UsersĀ and locate the Social_media_user.

Note:Ā The social media user must have read access to the Digizuiteā„¢ Media Manager product (right-click ConfigManager ā†’Ā Digizuiteā„¢ Media Manager).

Note:Ā The social media user must be different from the configured Guest user (web.config).

If configured (Embed code enabled), the application offers creation of embed code. The system needs a specific backend user to define rights and roles for that material.Ā 

By default, the system defines a backend user called Guest_beĀ which has very limited access.

3.6 Search

The search xml definitions under Digizuiteā„¢ Media Manager config must enable Solr usage.

If you should choose to change the metadata setup of the filtering functionality, you must ensure that all searches deliver the same filtering definitions.

In the ConfigManager, navigate to the SearchĀ tab and locate the Digizuite_System_Framework_SearchĀ definition.

  1. Enable Solr
  2. Save
  3. Start repopulating the search cache by clicking the gear icon of the search definition.

3.7 Filters

Filters inside Digizuiteā„¢ Media Manager are completely configurable based on the client's needs.

To add a new filter you have to:

Go to System tools ā†’Ā ConfigManager ā†’Ā Digizuiteā„¢ Media ManagerĀ and select the version to which you want to add a new filter. Select Searches tab and thenĀ Digizuite_System_Framework_Search and edit it.


  • The searchField will be treated as a filter if visible is set to true and has specified renderTypes. The following renderTypes are possible:
  • String ā€“ renders a standard input field
  • Combo ā€“renders as a classic dropdown box
  • Tree ā€“renders as a classic tree control
  • Multicombo ā€“ renders as a classic dropdown box with multiple selections possible
  • Bool ā€“ renders as a classic checkbox
  • Assettype ā€“ renders as a classic dropdown box with multiple selections possible
  • Datebetween ā€“ renders with 2 date pickers.

When finishing altering the search XML, copy the new version back inside ConfigManager. The same filters have to be copied to the following searches:

  • Digizuite_System_Framework_My_Favorites
  • Digizuite_System_Framework_My_Videos

Note: In order for the changes to be propagated, you will have to press Save and repopulate the search by pressing on the gear icon next to the title of the search.

  • Add a new label for the searchField
  • Navigate to System tools ā†’Ā ConfigManager ā†’Ā Digizuiteā„¢ Media ManagerĀ and make sure you select the active version. Navigate to the Labels tab and create a new label. The constant name should be the same as the ID of the searchField

3.8 Roles

The application defines roles that controls functionality in the Digizuiteā„¢ Media Manager. A role attaches to a backend user or user group. The following roles apply:

Role

Description

MediaPortal_User

Gives access to the application. Without this role, user will only be allow to access certain public previews (e.g. social media sharing).

MediaPortal_Collection

Gives access to collections view (right panel).

MediaPortal_Uploader

Allows user to upload new assets.

MediaPortal_Admin_StartScreen

Gives access to administer the splash screen.

MediaPortal_Asset_Replacer

Allows the user to replace or restore assets

MediaPortal_Asset_Unpublisher

Allows the user to remove(unpublish) assets

MediaPortal_Member_Viewer

Allows the user to see other members of the portal (e.g. during sharing process as autocompletion suggestions)

3.9 Download qualities

You can assign different download qualities to suit the company's solution. Navigate to System tools ā†’Ā Local users and groups ā†’Ā GroupsĀ and select Contributor. In the left panel it can be noticed that the information about the group has been loaded. Select Download qualities tab.

Make sure the desired qualities are present and they will automatically be available in the Digizuiteā„¢ Media Manager website.

3.10 SMTP setup

The Digizuiteā„¢ Media Manager uses SMTP functionality for various tasks like sharing links, notifications etc.

Navigate to System tools ā†’Ā Digizuiteā„¢ Configuration and locate the following constants:

  • SMTPDELIVERYMETHOD ā€“ configure the delivery method of the e-mail
  • SMTPPASSWORD ā€“ update with SMTP server password
  • SMTPPICKUPDIRECTORY ā€“ configure the pick-up directory of the e-mail
  • SMTPSERVER ā€“ update with SMTP server name
  • SMTPSERVERPORT ā€“ update with the SMTP server port
  • SMTPUSERNAME ā€“ update with the SMTP server username

Note: For detailed information on how to configure the e-mail feature, consult the DAM Center documentation.

3.11 Meta tags (SEO)

You can control the http meta tags (name, content pair) that the default page renders. Notice that this is only for global entry level tagging. More granular content specific SEO control will be available in a later release.

You may specify any number of meta tags that will be automatically rendered in the page. However, take a notice on SEO best practices as having vast amount of tags might turn out to be counterintuitive.

The system is pre-configured with some common meta tags that you probably want to edit to match the usage of the Digizuiteā„¢ Media Manager.

3.12 EmailĀ templates

The application defines mail templates for sending out emails like confirmation and download links. You may change these to fit your organization.

Navigate to System Tools ā†’Ā ConfigManager ā†’Ā Digizuiteā„¢ Media ManagerĀ and select the correct version.Ā Select the Config parametersĀ tab and Mail templatesĀ section.

3.13 Facet Search Configuration

The application allows the configuration of the results obtain from a faceted search.

3.13.1 Facet Result Sorting Order

To configure the order of the facet results, navigate to System Tools ā†’Ā ConfigManager ā†’Ā Digizuiteā„¢ Media Manager and select the correct version. Select the Config parametersĀ tab and change the following configuration:

  • SolrSortTypeĀ 
    • Possible options:Ā 
      • count ā€“ by the number of occurrencesĀ 
      • index ā€“ alphabetically.

3.13.2 Facet Result Limit

To configure the limit of the facet results, open the folder <WebsiteFolder> and find the file web.config. Open it in a text editor, find the appSettings group and add or change the following configuration key:

<add key="solrSearchLimit" value="{value}" />

Replace {value} with an integer representing the number of results you want to limit the facet search to. Use -1 in order to disable the limit.


Note

If the key does not exist or it doesn't have a value, the default value of 100 will be used.


Note

In version 4.7.0 and earlier, the key configuration was misspelled as sorlSearchLimit. As of 4.8.0, the typo is fixed. In order to insure backwards compatibility, the code will check the value of sorlSearchLimit, in case solrSearchLimit is not defined. It is strongly recommended that in installations of 4.8.0 or later to use the correctly spelled key name.