Roles

These are the roles that are needed:

  • Power user
  • Can delete metadata fields
  • Can write metadata fields
  • Can read metadata fields

API Links

Fields for Blocking API Link

Metadata Fields for Blocking

It is possible to setup a metadata field for blocking downloads and sharing of an asset. This can be useful to quickly drive functionality from metadata.

Only Yes/No (Boolean) fields can be used as blocking fields.

Only one blocking field should be used per metadata view.

Setting up a Blocking

To setup a blocking field:

  1. Start creating a Metadata Field as covered under Adding Metadata Fields.
  2. In the attributes select Block assets
  3. Add this Blocking Field to a Metadata View. The Metadata View you add it to should be one that will be used on the assets that you wish to block assets for.

At this point it is optional, but you may wish to add ACLs to the View so that only certain users have the ability to write to the view that contains the blocking field. If this is the case, it might be easier to create a separate view - one view for general users, and another for users that can edit this field.

Using the Blocking Field

Once you have a Blocking Field, you can then use it to set a download and sharing block on an asset.

  1. Go to an asset that you wish to block downloads or sharing.
  2. Open the Metadata tab
  3. Select the view that allows you to edit the block
  4. Set the field to Yes

Clearing the Blocking Field.

  1. Go to an asset that you wish to remove the block from
  2. Open the Metadata tab
  3. Select the view that allows you to edit the block field.
  4. Set the field to No