Supported Operations

19.4.1.16 GetAssetListByAllTableFullTextWithSuppInfo

DESCRIPTION: Allows an authenticated user to retrieve the key asset data (id, code, description, type, duration, marks and audio data) of all assets with at least one field partially/completely matching a given keyword, also including media info (Device, File, SOM, Duration, etc.) on playout files linked to retrieved assets.

Please refer to the Etere tables > Assets repository chapter for information on fields returned by this function.


It's worth mentioning that the given keyword is searched across the following asset data tables: assets (filmati), season (season), artists (artist), genres (generic), interruptions (interruzioni), metadata (smpte), roles (ruoli), segments (mam), documents (doma) and subtitles (sottotitoli).

INPUT:

_user: Login name of the executor.

_pwd: Password of the executor.

_searchString: Keyword to be searched.

_codUser: Number of the station to which the asset is related.

Note: The full-text search supports using the following wildcards on the _searchString keyword:

apple - Match fields containing the entire word apple;

apple or banana - Match fields containing at least one between the entire words apple and banana;

Apple and banana - Match fields containing both entire words, apple and banana;

Note: If two words are entered without operators (e.g. apple banana), the AND operator will be considered present (e.g. apple AND banana).

apple and not banana: Match fields containing only the entire word apple, not the word banana;

" apple* ":  Match fields containing a word starting with apple (e.g. apple, the apples, Appleton);

NB: The asterisk (*) must be preceded by at least one character (e.g. a).

"apple banana": Match fields containing the exact phrase apple banana (e.g. apple banana juice);

apple near banana: Match fields containing the entire word apple, rating the result lower if it also includes the word banana;

***: Match all assets in the database.

WARNING: The three asterisks (***) must be entered without other characters.

OUTPUT: 

The following fields are returned for each retrieved asset:

idAsset: Asset's unique identification number in Etere

Example: 26

Code: Asset's identification code string

Example: CLIP0000000026

Description: The asset's title

Example: Wonderwall

NewType: Asset's related programming type

Example: CLIP

DurationLogical duration of the asset

Example: 5511

TCINLogical mark in of the asset

Example : 0

TCOUTLogical mark out of the asset

Example: 5511

Audio_Language: Each character specifies the language of up to 16 audio track pairs (1&2, 3&4, 5&6...31&32).

Example: XX

Audio: Each character specifies the audio type of up to 16 audio track pairs (1&2, 3&4, 5&6...31&32).

Example: SS

MEDIAContains all files linked to the asset. For each linked file, one FILE tag will be returned containing the following information:

▪Supp_IdCloud-device

▪Supp_MetadeviceDesc

▪Supp_IdMetafile

▪Supp_CodecType

▪Supp_SOM

▪Supp_DUR

WARNING: Support fields (Supp_IdMetafile, Supp_MetadeviceDesc...) are valued only if the asset has at least one playout file. Otherwise, they are 0 (numeric) or blank (string).

Example: --

Supp_IdCloud-device: Identification number of the device in which the file is stored

Example: 101

Supp_MetadeviceDesc: Description of the device in which the file is stored

Example: MATROX MTX1

Supp_IdMetafile:  Identification number of the playout file linked to the asset. If the asset has no playout files, this field is "0".

Example: 1817

Supp_CodecType: Codec related to the file

Example: MPG

Supp_SOM: Physical mark in the file

Example: 100

Supp_DUR: Physical duration of the file

Example: 5611

WARNING: A playout file is a codec (e.g. MPG) that is enabled for being played by the automation system.

Here below is an example of an output message:

  <AssetMetadata> 
<Asset> <!-- Asset with multiple files -->
    <id>6</id> <code>CLIP0000000006</code> <desc>Stir it up</desc> 
    <newtype>CLIP</newtype> <duration>4709</duration> <TCIN>0</TCIN> 
    <TCOUT>4708</TCOUT> <AUDIO_LANGUAGE /> <AUDIO /> 
    <MEDIA> 
      <File> 
 <SUPP_IDMETADEVICE>111</SUPP_IDMETADEVICE> 
      <SUPP_METADEVICEDESC>MATROX MTX3</SUPP_METADEVICEDESC> 
      <SUPP_IDMETAFILE>1921</SUPP_IDMETAFILE> 
      <SUPP_CODECTYPE>MPG</SUPP_CODECTYPE> 
      <SUPP_SOM>0</SUPP_SOM> <SUPP_DUR>4709</SUPP_DUR> 
      </File> 
      <File> 
 <SUPP_IDMETADEVICE>71</SUPP_IDMETADEVICE> 
 <SUPP_METADEVICEDESC>OMNEON1</SUPP_METADEVICEDESC> 
 <SUPP_IDMETAFILE>1924</SUPP_IDMETAFILE> 
 <SUPP_CODECTYPE>MPG</SUPP_CODECTYPE> 
      <SUPP_SOM>10</SUPP_SOM> <SUPP_DUR>4710</SUPP_DUR> 
      </File> 
    </MEDIA> 
</Asset>
<Asset> <!-- Asset with one file -->
    <id>7</id> <code>CLIP0000000007</code> <desc>Like a rolling stone</desc> 
    <newtype>CLIP</newtype> <duration>8025</duration> <TCIN>0</TCIN> 
    <TCOUT>8024</TCOUT> <AUDIO_LANGUAGE /> <AUDIO /> 
    <MEDIA> 
      <File> 
 <SUPP_IDMETADEVICE>124</SUPP_IDMETADEVICE> 
      <SUPP_METADEVICEDESC>MATROX MTX125</SUPP_METADEVICEDESC> 
 <SUPP_IDMETAFILE>1906</SUPP_IDMETAFILE> 
 <SUPP_CODECTYPE>MPG</SUPP_CODECTYPE> 
      <SUPP_SOM>100</SUPP_SOM> <SUPP_DUR>8124</SUPP_DUR> 
      </File> 
    </MEDIA> 
</Asset> 
<Asset> <!-- Asset without files -->
    <id>3163</id> <code>CLIP0000003333</code> <desc>Falling down</desc> 
    <newtype>CLIP</newtype> <duration>1126</duration> <TCIN>0</TCIN> 
    <TCOUT>1502</TCOUT> <AUDIO_LANGUAGE /> <AUDIO /> 
    <MEDIA> 
      <File> 
 <SUPP_IDMETADEVICE>0</SUPP_IDMETADEVICE> 
      <SUPP_METADEVICEDESC> </SUPP_METADEVICEDESC>      <SUPP_IDMETAFILE>0</SUPP_IDMETAFILE> 
      <SUPP_CODECTYPE> </SUPP_CODECTYPE> 
      <SUPP_SOM>0</SUPP_SOM> <SUPP_DUR>0</SUPP_DUR> 
      </File> 
    </MEDIA> 
</Asset> 
</AssetMetadata>

From the previous example, it can be noted that three assets matched the full-text search:

▪The first asset (6) has two media stored on playout devices

▪The second asset (7) has only one media stored on playout devices

▪The third asset (3163) has no linked media stored on playout devices

 XSD (XML Schema Definition)

<?xml version="1.0" encoding="utf-8"?>
  <xs:schema id="AssetMetadata" xmlns=""    xmlns:xs="http://www.w3.org/2001/XMLSchema" 
    xmlns:msdata="urn:schemas-microsoft-com:xml-data"> 
  <xs:element name="AssetMetadata" msdata:IsDataSet="true" msdata:Locale="en-US"> 
    <xs:complexType> 
      <xs:choice minOccurs="0" maxOccurs="unbounded"> 
        <xs:element name="ASSET"> 
          <xs:complexType> 
             <xs: sequence> 
              <xs:element name="id" type="xs:string" minOccurs="0" /> 
 <xs:element name="code" type="xs:string" minOccurs="0" />
 <xs:element name="desc" type="xs:string" minOccurs="0" />
 <xs:element name="newtype" type="xs:string" minOccurs="0" />
 <xs:element name="duration" type="xs:string" minOccurs="0" />
 <xs:element name="tcin" type="xs:string" minOccurs="0" />
 <xs:element name="tcout" type="xs:string" minOccurs="0" />
 <xs:element name="audio_language" type="xs:string" minOccurs="0" />
 <xs:element name="audio" type="xs:string" minOccurs="0" />
 <xs:element name="MEDIA" minOccurs="0" maxOccurs="unbounded"> <xs:complexType>
  <xs:sequence>
  <xs:element name="FILE" minOccurs="0" maxOccurs="unbounded">
  <xs:complexType>
    <xs:sequence>
    <xs:element name="Supp_IdCloud-device" type="xs:string" minOccurs="0" />
    <xs:element name="Supp_MetadeviceDesc" type="xs:string" minOccurs="0" />
    <xs:element name="Supp_IdMetafile" type="xs:string" minOccurs="0" />
    <xs:element name="Supp_CodecType" type="xs:string" minOccurs="0" />
    <xs:element name="Supp_SOM" type="xs:string" minOccurs="0" />
    <xs:element name="Supp_DUR" type="xs:string" minOccurs="0" />
           </xs:sequence> 
        </xs:complexType> 
        </xs:element> 
        </xs:sequence> 
        </xs:complexType> 
        </xs:element> 
            </xs:sequence> 
          </xs:complexType> 
        </xs:element> 
      </xs:choice> 
    </xs:complexType> 
  </xs:element> 
</xs:schema>