Different recording platforms push metadata to the EVS VocieAI platform that is specific to that platform. As a result, this metadata will differ by recording platform and customer. Table 1 captures all of the metadata within one json object (see clientdata field definition in Table 1).
Table 4 extracts the metadata within the clientdata json object to make it more readily accessible.
Table 4 can get large and data scientists may find it more economic to extract selected parameters from the json file in Table 1 or load only part of Table 4 rather than all of Table 4.
Field | Type | Description |
|---|---|---|
company | String | Corresponds to the Company field in Wordbench. Refer to Wordbench Management Guide which can be found in the Media Library on the website. |
field_name | String | Name of the metadata |
field passed to the EVS platform. | ||
folder | String | Corresponds to the Folder field in Wordbench. Refer to Wordbench Management Guide which can be found in the Media Library on the website. |
insert_time | value | Date and time the database was populated. |
insertid | String | Unique identifier to link the tables together within the database. |
organisation | String | Corresponds to the Organization field in Wordbench. Refer to Wordbench Management Guide which can be found in the Media Library on the website. |
value | Varies | Value of the metadata field corresponding to the field_name. |