Overview
OpenTV Platform requires certain fields to have values for its recommendation functionality to work properly.
This is true whether the entities are ingested as XML files or via API calls.
These are listed for each entity below.
editorialContent
|
Field |
Notes |
Example |
|---|---|---|
|
In order of precedence:
|
|
JSON
|
|
|
|
JSON
|
|
|
|
JSON
|
|
|
|
N/A |
technicalContent
|
Field |
Notes |
Example |
|---|---|---|
|
|
|
N/A |
|
|
|
N/A |
|
|
|
N/A |
editorialChannel
|
Field |
Notes |
Example |
|---|---|---|
|
|
|
N/A |
|
|
|
N/A |
|
|
|
N/A |
|
|
|
N/A |
|
|
|
N/A |
|
|
Defaults to TV |
JSON
|
|
|
|
JSON
|
|
|
|
JSON
|
technicalChannel
|
Field |
Notes |
Example |
|---|---|---|
|
|
For STCU |
N/A |
event
|
Field |
Notes |
Example |
|---|---|---|
|
|
|
N/A |
|
|
|
N/A |
|
|
|
N/A |
|
|
Only required for episodic content |
N/A |
|
|
N/A |
contentGroup
The following fields are required for both series and season content groups.
|
Field |
Notes |
Example |
|---|---|---|
|
|
|
N/A |
|
|
|
N/A |
|
|
|
N/A |
|
|
|
N/A |
|
|
|
JSON
|
|
|
|
|
|
|
|
|
|
|
|
JSON
|
|
|
|
JSON
|