With the Artificial Intelligence Functionality Module, Curator connects with services to extract and transform automatic metadata.
Amazon Web Services - Transcribe
Connect with AWS Transcribe to offer speech to text capabilities in Curator.
Import AWS Transcribe ZIP file
Use the Modules tab on the Process Engine monitor to load the AWS Transcribe Functionality Module Zip file.
| Browse to Modules page | Browse to: http://localhost/ProcessEngineMonitor/Modules
|
 |
|
| Open the Workflows-AWS Transcribe-vx.x.x.x.zip file | Click Choose File. In the file explorer that appears, find and open the provided Workflows-AWS Transcribe-x.x.x.x.zip: 
|
 |
|
| Press Install |  |
 |
|
Confirm System Setup Completes Successfully |
 |
Set AI Media Stores
Use the MediaStores tab to configure the AWS options.
| Updated the AWS Media? | If the AWS MediaStore has already been updated with valid information through a different functionality module, this page can be skipped. |
 |
|
| Browse to the MediaStores tab | Browse to: http://localhost/ProcessEngineMonitor/MediaStore |
 |
|
| Open AWS MediaStore | Under Custom MediaStores, click AWS:
|
 |
|
| Click Edit | Click Edit:
|
 |
|
| Fill Out AWS Information | Fill out all the required information, remembering to tick the Encrypt option for the AWSSecretKey: 
|
 |
|
| Press Save Changes | When finished, click Save Changes:
|
 |
|
| Check System Setup has started | The changes to the MediaStore will not be active until a System Setup workflow is successfully run. A process should start automatically after saving changes to a MediaStore; if a process isn't spawned, create one manually.   For a brief reminder on how to run the System Setup Workflow, click here. |
Send To Destination Option
Added an option to send files for transcribing with the Send to Destination Plugin.
| Open the SendToDestination configuration file |
Browse to the %INSTALL_PATH%\IPV\Curator\Server\Config folder and navigate to the appropriate user group and web application folder. For example, administrators for Clip Link can be configured in the following file: %INSTALL_PATH%\IPV\Curator\Server\Config\w[System Administrators]-u[]-win[]-m[]\WebApplications\CuratorClipLink\Plugins\SendToDestination.config Open the file in a text editor. |
 |
|
| Find the <Destinations> section | <Destinations> <!-- User --> <Destination name="Deliver file to third party" locationPath="THIRDPARTY-FILE-DELIVERY" /> <Destination name="Retrieve the Hi-Res file" locationPath="DELIVER-HI-RES" /> <Destination name="Retrieve the proxy" locationPath="DELIVER-PROXY" /></Destinations> |
 |
|
| Add a Destination name and locationPath value for Transcribe |
The Destination name value is what the user will see displayed in the plugin dropdown. The value in locationPath needs to be the MediaStore name: <Destinations> <!-- User --> <Destination name="Deliver file to third party" locationPath="THIRDPARTY-FILE-DELIVERY" /> <Destination name="Retrieve the Hi-Res file" locationPath="DELIVER-HI-RES" /> <Destination name="Retrieve the proxy" locationPath="DELIVER-PROXY" /> <Destination name="Send for Transcribe" locationPath="AWS-TRANSCRIBE" /> </Destinations> |
 |
|
| Save the File | When finished, save and close the file. |
Xfer Device
Create an XFer AWS S3 device if one does not exist already.
| Does an XFer AWS S3 Device exist? | If an S3 device is already configured this page can be skipped.
|
 |
|
| Navigate to Devices Tab | Browse to: http://localhost/DeviceDirector/Device/List 
|
 |
|
| Click Create Device | Under Actions, click Create Device:
|
 |
|
| Select XFer AWS S3 | From the Type dropdown list, select the XFer AWS S3 option:
|
 |
|
| Enter Name and Address |
Both of the following are required fields:
|
 |
|
| Click Continue | Click Continue to confirm device creation. |
Add Required Curator Metadata
Use Curator System Administrator to add the required metadata names.
| Do the metadata names already exist? | Some of these metadata names may already exist, they may have been created during AWS Rekognition installation; skip those sections if they are already present. There are some fields exclusive to Transcribe mentioned here. |
 |
|
| Navigate to Curator System Administrator and select the MetadataNames tab | Browse to: http://localhost/CuratorSystemAdministrator/MetadataName 
|
 |
|
| Click Create | Click Create:
|
 |
|
| Create CuratorAISource Metadata Name |
Create a CuratorAISource metadata field with the following properties:
|
 |
|
| Create a CuratorClosedCaption Metadata Name |
Click Create again and make a CuratorClosedCaption metadata field with the following properties:
|
Click Save after entering these values.
Click Save after entering these values.Amazon Web Services - Rekognition
Enable advanced video analysis within Curator using AWS Rekognition.
Import Process Engine Module
Use Process Engine Monitor to import the provided Module zip file.
| Browse to Modules page | Browse to: https://localhost/ProcessEngineMonitor/Modules 
|
 |
|
| Select the Workflows-Edit and Publish-Adobe-v.zip file |
Click Choose file and navigate to the provided zip file. Select it and click Open: |
 |
|
| Install the Functionality Module | Click Install to complete the installation of the Functionality Module. |
 |
|
| The System Setup workflow will run | When installation is complete, the following message will be displayed.
|
Update AWS MediaStores
Add credentials to the AWS MediaStore which will configure Device Director Profiles and Devices; if this has already been configured by another functionality module then this step can be skipped.
| Updated the AWS Media? | If the AWS MediaStore has already been updated with valid information through a different functionality module, this page can be skipped. |
 |
|
Browse to the MediaStores tab |
Browse to: http://localhost/ProcessEngineMonitor/MediaStore 
|
 |
|
| Open AWS MediaStore | Under Custom MediaStores, click AWS:
|
 |
|
| Click Edit | Click Edit:
|
 |
|
| Fill Out AWS Information | Fill out all the required information, remembering to tick the Encrypt option for the AWSSecretKey: 
|
 |
|
| Press Save Changes |
When finished, click Save Changes:
|
 |
|
| Check System Setup has started | The changes to the MediaStore will not be active until a System Setup workflow is successfully run. A process should start automatically after saving changes to a MediaStore; if a process isn't spawned, create one manually.   For a brief reminder on how to run the System Setup Workflow, click here. |
Add Options to Send To Destination Plugin
For each Rekognition MediaStore, create a new entry in the Send To Destination plugin config file.
| Open the SendToDestination configuration file |
Browse to the %INSTALL_PATH%\IPV\Curator\Server\Config folder and navigate to the appropriate user group and web application folder. For example, administrators for Clip Link can be configured in the following file: %INSTALL_PATH%\IPV\Curator\Server\Config\w[System Administrators]-u[]-win[]-m[]\WebApplications\CuratorClipLink\Plugins\SendToDestination.config Open the file in a text editor. |
 |
|
| Find the <Destinations> section | <Destinations> <!-- User --> <Destination name="Deliver file to third party" locationPath="THIRDPARTY-FILE-DELIVERY" /> <Destination name="Retrieve the Hi-Res file" locationPath="DELIVER-HI-RES" /> <Destination name="Retrieve the proxy" locationPath="DELIVER-PROXY" /></Destinations> |
 |
|
| Add destinations for all three job types |
The Destination name value is what the user will see displayed in the plugin dropdown. The value in locationPath needs to be the MediaStore name. Add one for each of the Rekognition jobs: <Destinations> <!-- User --> <Destination name="Deliver file to third party" locationPath="THIRDPARTY-FILE-DELIVERY" /> <Destination name="Retrieve the Hi-Res file" locationPath="DELIVER-HI-RES" /> <Destination name="Retrieve the proxy" locationPath="DELIVER-PROXY" /> <Destination name="Scan File for Celebrities" locationPath="AWS-REKOGNITION-CELEBRITY" /> <Destination name="Scan File for Labels" locationPath="AWS-REKOGNITION-LABEL" /> <Destination name="Scan File for Appropriate Content" locationPath="AWS-REKOGNITION-MODERATION" /> </Destinations> |
 |
|
| Save the File | When finished, save and close the file. |
Xfer Device
Create an XFer AWS S3 device if one does not exist already.
| Does an XFer AWS S3 Device exist? | If an S3 device is already configured, this section can be skipped. 
|
 |
|
| Navigate to Devices Tab | Browse to: http://localhost/DeviceDirector/Device/List 
|
 |
|
| Click Create Device | Under Actions, click Create Device:
|
 |
|
| Select XFer AWS S3 | From the Type dropdown list, select the XFer AWS S3 option:
|
 |
|
| Enter Name and Address |
Both of the following are required fields:
|
 |
|
| Click Continue | Click Continue to confirm device creation. |
 |
|
| Confirm Device Creation | When the device has been created, a green tick icon will appear in Status:
|
Create Required Metadata Names
Using Curator System Administrator, create new metadata names and set their permissions.
| 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:
|
 |
|
| Create ContentLabels Metadata Nam | Click Create again and make a ContentLabels metadata field with the following properties.
|
 |
|
| Create Celebrities Metadata Name |
Click Create again and make a Celebrities metadata field with the following properties:
|
 |
|
| Create ComplianceLabels Metdata Name |
Click Create again and make a ComplianceLabels metadata field with the following properties:
 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. Under No Permission, tick the groups that require access. When done, click Save before moving onto the next metadata name: 
|
Click Save after entering all the values.
Click Save after entering these values.