Ingest Services
From AMWA
Note: The media file(s) discussed in this document refer to one of three possible cases:
- Single file containing a single media essence
- Single file representing a container format like MXF, containing media essences, metadata, etc.
- Multiple files representing a complex graph of interrelated media contents (of the kind described in MXF, or in “Compound Information Objects: The OAI-ORE Perspective” – see http://www.openarchives.org/ore/documents/CompoundObjects-200705.html )
We assume that all these cases can be represented by a URI that uniquely identifies the file(s) and also provides a mechanism for accessing them.
Media File Copy Service
Request Copy from File
Given a set of media files at a particular location (and optionally a separate set of metadata), initiates the operation of copying the set of media files (and optionally metadata) to a specified target file storage location for later use. It is assumed that any necessary technical configuration setups have already been performed.
The fact that SOAP is used to submit this request does not imply that the media files are also transferred using SOAP. In fact, this interface does not specify which transport is used by the service to actually transfer the files.
The request returns a synchronous acknowledgement as soon as it is received. At the time the processing of the request is completed, an asynchronous response is returned. Before completion, the original requester can ask for the status of the Copy operation using Get Copy Status, or can abort the operation using Cancel Copy.
- Inputs:
Source media file(s) URI
Metadata (or metadata URI)
Destination URI
Project ID
Delivery time constraints
Security requirements on delivery
- Outputs (synchronous):
Operation ID
- Outputs (asynchronous):
Success/failure
Request Copy from Removable-Media
Given a set of media files on a removable media (and optionally a separate set of metadata), initiates the operation of copying the set of media files (and optionally metadata) to a specified target file storage location for later use. It is assumed that any necessary technical configuration setups have already been performed.
The fact that SOAP is used to submit this request does not imply that the media files are also transferred using SOAP. In fact, this interface does not specify which transport is used by the service to actually transfer the files.
The request returns a synchronous acknowledgement as soon as it is received. At the time the processing of the request is completed, an asynchronous response is returned. Before completion, the original requester can ask for the status of the Copy operation using Get Copy Status, or can abort the operation using Cancel Copy.
- Inputs:
Source removable-media UMID
Media file(s) identification
Metadata (or metadata URI)
Destination URI
Project ID
Delivery time constraints
Security requirements on delivery
- Outputs (synchronous):
Operation ID
- Outputs (asynchronous):
Success/failure
Request Copy from Tape
Given some A/V media content on a tape (and optionally a separate set of metadata), initiates the operation of copying the corresponding media files (and optionally metadata) to a specified target file storage location for later use. It is assumed that any necessary technical configuration setups have already been performed.
The fact that SOAP is used to submit this request does not imply that the media files are also transferred using SOAP. In fact, this interface does not specify which transport is used by the service to actually transfer the files.
The request returns a synchronous acknowledgement as soon as it is received. At the time the processing of the request is completed, an asynchronous response is returned. Before completion, the original requester can ask for the status of the Copy operation using Get Copy Status, or can abort the operation using Cancel Copy.
- Inputs:
Source tape UMID
Media contents identification
Metadata (or metadata URI)
Destination URI
Project ID
Destination file format
Delivery time constraints
Security requirements on delivery
- Outputs (synchronous):
Operation ID
- Outputs (asynchronous):
Success/failure
Get Copy Status
- Inputs:
Operation ID
- Outputs:
Status
Cancel Copy
- Inputs:
Operation ID
- Outputs:
Success/failure
Check for viruses
Given a set of media files at a particular location, check them for viruses
- Inputs:
Media file(s) URI
- Outputs:
Scan report
Check for technical compliance
Given a set of media files at a particular location, check them for compliance with particular standards
- Inputs:
Media file(s) URI
Compliance type
- Outputs:
Compliance report
Check for technical quality
Given a set of media files at a particular location, check them for technical quality
- Inputs:
Media file(s) URI
Quality-check type
- Outputs:
Quality report
Check for editorial value
Given a set of media files at a particular location, check them for editorial value
- Inputs:
Media file(s) URI
Editorial value type
- Outputs:
Editorial value report
Extract metadata
Given a set of media files at a particular location, extract any metadata contained therein
- Inputs:
Media file(s) URI
Metadata destination URI
- Outputs:
Success/failure
Manually enter metadata
Prompt the user to enter metadata for the given media file(s)
- Inputs:
Media file(s) URI
- Outputs:
Metadata
Transform
Given a set of media files at a particular location (and optionally a separate set of metadata), generate new formats for the same assets by transcoding, de-multiplexing, splitting at scene/shot boundaries, etc. (and optionally adding metadata)
- Inputs:
Media file(s) URI
Metadata URI
Transformation type and parameters
Destination URI
- Outputs:
Success/failure
Register media in asset management system
Given a set of media files at a particular storage location (and optionally a separate set of metadata), register the assets (and associated metadata) within an asset management system
- Inputs:
Media file(s) URI
Metadata URI
Target DAM URI
- Outputs:
Success/failure
Asset ID
Update media in asset management system
Given a set of media files at a particular storage location, update existing corresponding assets in an asset management system
- Inputs:
Media file(s) URI
Target DAM URI
Asset ID
- Outputs:
Success/failure
Update asset metadata in asset management system
Given a set of metadata and a reference to the assets they refer to, update the corresponding asset's metadata within an asset management system
- Inputs:
Metadata URI
Target DAM URI
Asset ID
- Outputs:
Success/failure
Notify user
Send notifications to specified recipients
- Inputs:
User URI
Message
- Outputs:
Success/failure
Log activities
Record various activities in a process log
Illustrations
Ingest File Pull Illustration
Get Media and Metadata Illustration
Save Media and Metadata Illustration
Exception Illustration