With this release, we continue the commitment to listen to our customers, focus on performance, and quickly respond with new features and fixes. This update offers features that add more depth to how you can create and manage metadata and new tools to enable the management and publishing of your content.
Temporal Metadata
We have extended our asset model to support temporal metadata mapped to timelines in MAM. A timeline enables you to mark an event when it occurs during a video, and enter metadata to describe that event.
For example: you have a video of a soccer match. Every time a goal is scored, you could place a marker or range which contains metadata to describe the details of the goal such as: the player who scored it, the goalkeeper, the team, and so on.
Dynamic Timelines
With Dynamic timelines you can have multiple timelines for a single asset, each with its own defined Metadata, this allows the creation of timelines for specific elements in an assets lifecycle, event specifics, scene descriptors, soundtrack, product placement, legal, etc. that can be managed by separate teams. These timelines are configured using the Metadata Designer and are available in MAM and Reviewer. To configure a timeline in the Metadata Designer, you must do the following:
Object Hierarchy Management
We have added the ability to manage user defined hierarchical structures in MAM. This allows you to: view, navigate, and create metadata instances which reflect data structures in a visual / interactive panel for advanced business reporting.
Note: Hierarchy / object definitions and configurations should be done in the Ooyala Flex interface. MAM allows a user to manage the instances of the metadata.
Plugins
REST API
These are as follows:
Resource | Endpoint | Method |
---|---|---|
timelines: | /timelines | get / post |
timelines: | /timelines{timelineId} | get / put / delete |
These are as follows:
Resource | Endpoint | Method |
---|---|---|
assets: | /assets/{assetId}/reviews | get |
assets: | /assets/{assetId}/reviews/{reviewId} | get / delete |
assets: | /assets/{assetId}/reviews/{reviewId}/actions | get / post |
assets: | /assets/{assetId}/reviews/{reviewId}/comments | get |
assets: | /assets/{assetId}/reviews/{reviewId}/statuses | get |
assets: | /assets/{assetId}/reviews/{reviewId}/statuses/{reviewer} | get / put |
assets: | /assets/{assetId}/reviews/{reviewId}/annotations | post |
assets: | /assets/{assetId}/reviews/{reviewId}/annotations/{annotationId} | put |
Resource | Endpoint | Method |
---|---|---|
userDefinedObjectTypes: | /userDefinedObjectTypes | get / post |
userDefinedObjectTypes: | /userDefinedObjectTypes/{udotId} | get / put |
userDefinedObjectTypes: | /userDefinedObjectTypes/{udotId}/hierarchy | get |
Members: We have added the group matrix parameter to the /assets//members. This parameter enables you to retrieve a list of group members and exclude all of the items in the group such as any media assets, image assets, and so on. Examples:
In order to retrieve just the group members, you would do the following- api/assets/members;group=true.
In order to only list the group items, you would do the following- api/assets/members;group=false.
Publish API
An endpoint has been added to the Publish API, which retrieves group hierarchies. This is as follows:
/public/api/assets/<groupId>/hierarchy
Keywords and Metadata
MAM
Please note the following known issues in MAM:
Reviewer
SDKs
getUserDefinedObjects()
now requires a context parameter, whose value can be null
or all
. The value all
returns a list of all UDOs, including children in the hierarchy. This change will be backward compatible from the 6.1.0 release.Reindexing
Reindexing by account ID does not work.
Resolution
This will be fixed in the 6.0.2 release.
Expression Language
The expression event/mioObject
will be deprecated, and should only be used when the event only includes mioObject
.
event.flexManagedObject
can be used for both mioObject
and mioJob
.
Therefore, the following changes have been made to configuration of expressions:
event.flexManagedObject
instead of event.mioObject
.event.flexManagedObject
instead of event.mioObject
.Job Searchability
Jobs are no longer searchable from Global Search. Nor do jobs support a full text search. Instead, they are searchable by specific filters, such as owner, deleted, and status.
For those upgrading from previous versions, upgrade instructions can be found here.
Service | Version | Required Instructions |
---|---|---|
flex-admin-app | 2.0.456 | |
flex-authentication-service | 7.5.292 | |
flex-authorisation-service | 2.3.293 | |
flex-dataagreggation-service | 1.4.377 | |
flex-divarchive-service | 2.1.325 | |
flex-events-service | 2.7.339 | |
flex-fastobject-service | 3.3.350 | |
flex-forms-service | 0.0.139 | |
flex-imageproxy-service | 3.2.284 | |
flex-indexelastic-service | 5.9.345 | |
flex-job | 6.0.0.6 | |
flex-mam-app | ||
flex-master | 6.0.0.6 | |
flex-metadatadesigner-app | 2.2.917 | |
flex-metadatamerge-service 2.2.335 | ||
flex-outboundtransfer-service | 2.0.219 | |
flex-publish-service | 9.3.370 | Upon upgrade, you must move KV from flex/flex-publish-service/url to flex/shared/urls/flex-publish-service.This requires reindexing ElasticSearch indexes. Use the following api: /api/accounts//elastic/reindex |
flex-reviewer-app | 3.1.433 | |
flex-searchelastic-service | 4.2.458 | |
flex-streamprocessor-service | 1.1.93 | |
flex-tag-service | 1.0.699 | |
flex-thesaurus-service | 0.1.797 | |
flex-webtransfer-app | 7.0.480 | |
flex-workflowdesigner-app | 7.1.219 |