...
Expand | ||
---|---|---|
| ||
|
Data Objects
When ingesting Data Objects, the analysis step will be called in the context of the original representation, whereas the get insights step will be called in the context of the data object itself.
API
Common
For all methods the following HTTP header is provided:
...
The input is a JSON body with the following properties
Property | Type | Description |
---|---|---|
| Object | The standard JSON representation of the metadata as used in the MediaHaven REST API: MediaHaven sidecar format |
| Object | The custom properties configured on the plugin |
, as described above: https://mediahaven.atlassian.net/wiki/spaces/CS/pages/ |
Response / Output
The HTTP response
202 Accepted
204 No Content
when the analysis was successfully started
...
Expand | |||||
---|---|---|---|---|---|
| |||||
|
...
POST insights/
Returns the list of available insights on the object
...
The input uses the following HTTP parameters
...
JSON properties
Property | Type | Description |
---|---|---|
| String | The record ID of the object in question |
| Boolean | Whether to include the raw data, by default false. |
<mapping> | Object | The custom properties configured on the plugin are passed as a sequence of parameters → , as described above: https://mediahaven.atlassian.net/wiki/spaces/CS/pages/44388843954652335133/Module+Plugins#Custom-propertiesInsights+Connector+Contract#Configuration |
Response / Output
200 OK
with the response409 Conflict
when the analysis is still pendingThe output is a JSON array of JSON objects with the following properties
Property | Type | Description |
---|---|---|
| The standard JSON representation of the metadata as used in the MediaHaven REST API: MediaHaven sidecar format. | The generated insights, converted into metadata as instructed by the provided configuration. |
| String | The full raw data of the analysis; as a base64 encoded string. |
Example
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
Input
Output
|