Grass Valley Schedule Importer - Manual (Page 8)

Cobalt XML Schedule Import User Manual - document version: 1.28 – Page 8
Asset
Specifies the Event’s main asset.
Asset Record Mandatory Specifies the Event’s main asset.
Contains:
• type_metadata (0 or 1)
• custom_metadata (0 or 1)
If an asset reference (InternalID, see below) does
not exist in the TX/MAM database, a new asset is
created using information from the attributes and
records below.
Asset attributes:
InternalID
Attribute Optional, but
recommended
Reference to the asset. Other systems may call
this reference ”House ID” or “Material ID”. Stored
in the TX/MAM database as "external ref".
ID Attribute Optional Direct reference to an asset (if the asset already
exists). Not often used.
AssetType Attribute Mandatory for
new assets
Asset type, as defined in TX/MAM.
TcIN Attribute Optional Timecode in in format hh:mm:ss:ff.
Used for partial playout of assets.
TcOut Attribute Optional Timecode out in format hh:mm:ss:ff.
Used for partial playout of assets.
type_metadata
type_metadata info is used to create new assets, or to update asset info [see also chapter 6].
The asset (type)’s base type fixed fields.
type_metadata Record Optional, used if
a new asset has
to be created or
to update asset
info
Used if a new asset is created, or to update asset
info. The asset type’s base type fixed fields.
Contains: Field (0 or more).
FIELD Record Optional Note that the type metadata fields have to match
the fixed fields for asset types as defined in
TX/MAM.
Example:
value
custom_metadata
custom_metadata info is used to create new assets, or to update asset info [see also chapter 6].
The asset (type)’s custom fields, if any.
custom_metadata Record
Optional, used if
a new asset has
to be created or
to update asset
info
Used if a new asset is created, or to update asset
info.
Contains: Field (0 or more).
FIELD Record Optional Name of the custom metadata field, as defined in
TX/MAM. Fields that are not found in the asset
type definition will be ignored.
Example:
Usher