MM5.10 Copyright notification before download

Enabling this feature will enable one to show copyright messages upon the download of one or more assets (custom quality downloads included).

Specifically, you get the option to control the following:

  • Who gets to see the copyright disclaimer

  • Make copyright presets, and assign them to multiple assets quickly

  • Make custom copyright messages for individual assets (which will override the copyright presets)

How to set up predefined messages (aka. preset messages)

First of all, you need to make at least one new metadata field; a predefined or a custom message. Please skip this part, if you only want custom copyright messages.

The field for predefined messages can be of the metadata types: string, note, or combovalue. Itā€™s advised that you go with combovalue, as this allows for messages to be reused and updated or deleted easily.

If you choose instead to use node or string, you can skip the next part, as it only pertains to combovalue.

You need to manually define some presets in your combovalue. For the purpose of this guide, weā€™ll show how it works for media licensed from HBO GO and Netflix:

In the image above, you see the ā€œTextā€œ and ā€œValueā€œ fields. The ā€œTextā€ field is the one that is visible for selection in the UI, whereas the ā€œValueā€œ is the message thatā€™s shown when a user tries downloading an asset.

This means that as an admin/editor - I know that a certain asset has been licensed by HBO GO, and to this, I have to show a disclaimer every time a user downloads it. I edit the asset from the MMā€™s asset editor, select HBO GO in the list, and press save. Now, all users that download the asset will be met with the message ā€œUsage needs to be approved by anā€¦ā€œ.

The users that are to be prompted with a predefined message must, as a minimum, have read access to the metafield.

How to set up a custom message

The custom notification message will always ā€œgo firstā€. So, in the case where you have both predefined and custom messages set up (which technically is non-sensical to have), the user will be met with the custom message, not the predefined one.

Usually, one would set up the metadata field for custom notification messages to be either a string or a note field. The way it works is that an admin or editor edits an assetā€™s metadata, fills out the custom notification message field, and saves. Now, users who download the asset will be met with the custom message.

The users that are to be prompted with a custom message must, as a minimum, have read access to the metafield.

Configuring MM to use the new metadata fields

Once youā€™ve created a predefined notification field, a custom field, or both - you need to configure the MM to use them.

Go to Portal Config Manager ā†’ [your portal].

In here, expand the ā€œCopyright Notificationā€œ control.

Check the ā€œEnable copyright notificationā€œ, in the ā€œPredefinedā€¦ā€œ field, you, of course, enter your predefined field, and likewise for the ā€œCustomā€¦ā€ field.

Now press ā€œSaveā€, and you should be good to go.

If no custom or predefined message has been set up for a given asset, the asset will simply download.

The bypass role

Some users might be well aware of the copyrights of the individual assets and therefore desire to opt out.

To address this, a new role has been added, called: Copyright_Notification_Bypass

Simply add this to your user or a group your user is a part of, and you should never encounter the copyright messages again.