Overview: Below is information pertaining to how IRIS.TV’s Contextual Video Marketplace integrates with a publisher's content management system (CMS) via a content feed or API.
Setting
...
Up Video Asset Metadata Ingestion
IRIS.TV supports a wide range of feed formats and data typesformats to handle content feed ingestion. Below are lists of accepted importing ingest methods and metadata requirements for adding contextual segments to your video content.
Accepted Methods for
...
Video Asset Metadata Ingestion
IRIS.TV supports the following feed formats for video data importingasset library ingest:
MRSS
RSS
XML
JSON
API
Once the publisher has your have sent IRIS.TV a content feed or API to access their video datayour assets, IRIS.TV will ingest your video data into a secure account for the publisher. Content feed integrations typically take . Integration typically takes less than one week.
Recommendations for Feed Pagination
If the publisher is you are providing a content feed (rather than an API) for content ingestion, IRIS.TV recommends using pagination so that your full library can be imported ingested for contextual segmentation. IRIS.TV supports the following pagination methods:
Offset parameter: Feed parameters that allow for calling a specific number of assets and an offset for how far to go into the feed.
Next Link pagination: a link for the next page is included in the current page.
...
IRIS.TV recommends that feeds are ordered by a "updated_at" field on the assets. That ensures that all asset updates are imported ingested into the system.
Metadata Requirements
IRIS.TV has ranked metadata requirements in three sections:
Required – these are this data is necessary to create contextual segments on for your contentassets.
Preferred – this data will likely improve the contextual segments on segmentation for your contentassets.
Optional – this data will help IRIS.TV parse the publishers feed and understand the state of their contentcan improve the contextual segmentation for your assets with some data partners.
| Excerpt |
|---|
Required Meta Data
Preferred Meta Data
Optional Meta Data
|
...
|
Sample Asset from a Publisher
| Code Block | ||
|---|---|---|
| ||
{
"id": 5331690110001,
"name": "Lorem ipsum dolor sit amet, consectetur adipiscing elit",
"shortDescription": "Donec congue orci vel ante posuere consectetur. Vestibulum vel eros velit. In suscipit arcu nec lectus posuere sagittis.",
"creationDate": 1487717574502,
"publishedDate": 1487717955852,
"lastModifiedDate": 1487717955969,
"startDate": 1487717955969,
"endDate": null,
"tags": [
"alex rodriguez",
"new york yankees",
"mlb"
],
"videoStillURL": "http://xxx/2157889318001_5331738223001_5331690110001-vs.jpg?pubId=2157889318001",
"thumbnailURL": "http://xxx/2157889318001_5331738224001_5331690110001-th.jpg?pubId=2157889318001",
"length": 30805,
"economics": "AD_SUPPORTED",
"categories": [
"Baseball"
],
"itemState": "ACTIVE",
"SourceURL": "http://xxx/2157889318001_5331740038001_5331690110001.mp4"
}, |
After the Initial
...
Ingest
Once the initial import ingest is complete, IRIS.TV will provide you with credentials to start the Context Script or Context API integration. These credentials include:
Client Token: used to authenticate your content asset library. Required for both the Context Script and Context API integrations.
Access Token: used to authenticate with the API. Required for the Context API integration.
The integration will also require the use of a “platformplatform_id”id. The platform_id is mapped in from the unique ID field during the importthe ingest. Once you have received the above credentials from IRIS.TV, please move to Retrieving Contextual Data.