Curator version supported from this article: 3.0
This guide explains how to create placeholder assets and ingest a large number of files from a single AWS S3 bucket (folder).
Bulk ingesting is helpful when you want to bring in all your assets at once and prefer to wait until everything is compiled in one location. This is especially useful for camera cards and multi-file assets.
Learn more about how to Prepare for AWS S3 for bulk ingest.
Ingesting the Manifest File
- From the Dashboard, open the S3 Bulk Ingest application.
NOTE: If you do not see the application in your dashboard, please contact IPV support.
- Enter the required information, including both mandatory and optional metadata. Any optional fields can be completed if you wish. The metadata you provide will be applied to all assets created during the ingest.
If you’d like to change which metadata fields are available for tagging assets in an S3 Bulk Ingest, see Managing asset metadata.
S3 Bulk Ingest mandatory metadata:
- S3 Bucket: Enter the bucket in which your manifest file was placed earlier.
- S3 Manifest File Path: Enter the file name and extension of your Manifest file.
- When you’re ready, select Submit.
- Your placeholder assets will now be created.
Process Monitoring S3 Bulk Ingest
- Open the Process Engine application from the Dashboard.
- Navigate to the Processes tab.
- Search for the Plug-in - Send to GenericV4 workflow.
- Find the workflow that corresponds to your placeholder. Expanding the parent process using the drop-down arrows will display the child processes.
- Ensure that this matches the time you selected the Submit button.
- The process status will turn from yellow to green when complete.
- Once complete, navigate to the Clip Link application from the Dashboard. You should be able to see your assets in a placeholder state.
- Once a placeholder is created, a scavenge should gather the placeholder assets to process for the remaining ingest steps such as Proxy and Mediainfo.