Creating Required Metadata Names for 3.3

Updated on December 12th, 2022

Do the metadata names already exist? Some of these metadata names may already exist, they may have been created during AWS Transcribe installation; skip those sections if they are already present. There are some fields exclusive to Transcribe mentioned here.

Browse to Curator System Administrator Metadata tab Browse to: http://localhost/CuratorSystemAdministrator/MetadataName. Log in if prompted:

Click Create Click Create:

Create CuratorAISource Metadata Name

Create a CuratorAISource metadata field with the following properties:

  • Name: CuratorAISource
  • Display name: Curator AI Source
  • Asset type: Sub Clip
  • Data type: TextClick Save after entering all the values.

Create ContentLabels Metadata Nam Click Create again and make a ContentLabels metadata field with the following properties, make sure to tick multi-value:
  • Name: ContentLabels
  • Display name: Content Labels
  • Asset type: Sub Clip
  • Data type: Text
  • Multi-value: TrueClick Save after entering all the values.

Create Celebrities Metadata Name

Click Create again and make a Celebrities metadata field with the following properties, make sure to tick multi-value:

  • Name: Celebrities
  • Display name: Celebrities
  • Asset type: Sub Clip
  • Data type: Text
  • Multi-value: True
Click Save after entering all the values.

Create ComplianceLabels Metdata Name

Click Create again and make a ComplianceLabels metadata field with the following properties, make sure to tick multi-value:

  • Name: ComplianceLabels
  • Display name: Complaince Labels
  • Asset type: Sub Clip
  • Data type: Text
  • Multi-value: True
Click Save after entering all the values.

Set Metadata Name Workgroups
For each created metadata name, set permissions by selecting the metadata name in the left hand list and under No Permissions tick the groups that require access.
When done click Save before moving onto the next metadata name:
Was this article helpful?