| Make the minimal config changes to get Curator Connect up and running on-premises. Create a storage directory and set the path. |
|
|
|
| Note on configuring optional settings below | To configure the optional settings shown below, please follow the first three steps in the Basic Settings link as these are accessed from the same area in CSA. |
| S3 Settings | Make the minimal config changes to get Curator Connect up and running on-premises. Create a storage directory and set the path following the first three steps in the Basic Configuration link. You will need to add an S3 Ingest Destination with the following details:  In addition to this, you will need to configure the S3 settings section (example configuration shown below): Please note that the Use accelerate endpoint? option should only be ticked in cases where this has been successfully set up on the bucket.The details of the S3 storage section must match the details of the bucket declared in the AWS Media Store in Process Engine configuration (example AWS Media Store configuration details are shown below): 
|
| In-Place Paths | Optionally, you may wish to configure an in-place path. This enables users to ingest from the specified path without moving the original hi-res files. A proxy will be created in Curator, with an asset describing it. To add in-place paths, first make the minimal config changes to get Curator Connect up and running on-premises. Create a storage directory and set the path following the first three steps in the Basic Configuration link. You will then need to enter details for a Folder Path in the In-Place Paths section, under File Settings. Example path configuration is shown below: 
|
For Macs, the CURATORCONNECT-INGEST MediaStore needs to be adjusted to allow for transfers. |
|
|
|
Curator Connect can also transfer files via FTP and FTPS. An FTP server must be accessible to the Client Application for this capability. |
