MM5.3.0 4 Configuration

3.0 Guest user access

The Digizuite™ Media Manager requires a user for accessing the API to collect configuration. The user you define will also be the one that guests use when they access the MM without logging in (not if your site set up to be "login required").

By default, this user has already been set up. The user is named "guest" and can be located in Users and groups → Users → System users. 

This user has been born with the following Groups: Anonymous and Guest, and with the following roles: Asset_Can_Download and MediaPortal_User.

If you want to change your site to use another user instead, you will have to do the following:

1. Locate and open your MM's appsettings.json file placed in the root of your site folder (Usually in C:/Webs/[your MM's folder]/appsettings.json)
2. Change the value for guestUsername to be the new username.
3. Change the value for guestPassword to be the corresponding password written in md5. (This you can generate yourself, or you can find it in the databse in the member table)

The guest user must have the role MediaPortal_User to function correctly.

3.1 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.2 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.3 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).

3.4 User for embedded links

If configured (Embed code enabled), the application offers the 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.5 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.6 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.6.1 Allow for spaces to be shown in filters

Per default, a filter will split on spaces " ", menaing that e.g. if you have an EditMultiComboValue metadata field like "Keywords", where a keyword is "Queen of Denmark", said keyword will be split to "Queen", "of", and "Denmark".

In order to combat this, you need to modify the search. Please follow these steps to do so:

1. Make the changes you need to do, and publish the search (like normally)
2. Wait until the publish has finished (Find the search versionId)
3. Stop SOLR
4. Delete everything in the data folder(C:\Services\SolrService\CORENAME\Data) under the core you just created
5. Edit the managed-schema file in (C:\Services\SolrService\CORENAME\Conf)
6. Find the fieldType name="text_general"
7. Under this tag there are two tokenizer classes, they are set to "solr.StandardTokenizerFactory"
8. Change those two to: "solr.KeywordTokenizerFactory"
9. Start SOLR
10. Repopulate the SOLR cache by the following command to the API:

https://URL/apiproxy/JobService.js?accessKey=xxx&method=PopulateSearchCache&force=true&search_versionId=XXX&dataVersionId=!/0/0/0/

(Enter URL, accessKey and serach_versionid and doublecheck dataVersionId)

3.7 Roles

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

Can_Edit_Automation_Workflow

Can_View_Logs

Can_View_Automation_Workflow_Status

Can_Live_Export_Assets_And_Metadata

Can_Live_Export_Asset_Only

Can_Live_Export_Metadata_Only

3.8 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.9 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 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.12 Facet Search Configuration

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

3.12.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 Server Side Rendering

It is possible to use server side rendering to make the Media Manager work better with sharing to external portals. Server Side Rendering (SSR) can be enabled by changing the "enablePrerendering" flag to "true" in the appsettings.json file. To support SSR the server where Media Manager is installed needs to have NodeJS installed. We recommend  LTS Version: 10.16.0, though newer should also work. 

There are a couple of limitations you should be aware of with this however:

• The guest user should be able to access all sharable assets. This means both files that has a "share" dialog in Media Manager, but also when people copy-paste urls.
• Using configuration modes like "introscreens" is not supported, as they override all data on the page, which means Facebook and co cannot see the actual file, as they can't pass the intro screen. 
• Both the Media Manager and Dam Center site has to be available externally for Facebook and such to be able to load the data they need to generate previews.