video.description
, while team B could use audio.description
. Another example could be TeamName.MetadataKey
. This approach maintains clarity and avoids key collisions across departments.add_scalar
to add a scalar key to your metadata schema.
Scalar Key | Description | Display Benefits |
---|---|---|
boolean | Binary data type with values “true” or “false”. | Filtering by binary values |
datetime | ISO 8601 formatted date and time. | Filtering by time and date |
number | Numeric data type supporting float values. | Filtering by numeric values |
uuid | UUIDv4 formatted unique identifier for a data unit. | Filtering by customer specified unique identifier |
varchar | Textual data type. Formally string . string can be used as an alias for varchar , but we STRONGLY RECOMMEND that you use varchar . | Displaying data correctly in custom Label Editor layouts and filtering by string. |
text | Text data with unlimited length (example: transcripts for audio). Formally long_string . long_string can be used as an alias for text , but we STRONGLY RECOMMEND that you use text . | Storing and filtering large amounts of text. |
add_enum
and add_enum_options
to add an enum and enum options to your metadata schema.
Key | Description | Display Benefits |
---|---|---|
enum | Enumerated type with predefined set of values. | Facilitates categorical filtering and data validation |
add_embedding
to add an embedding to your metadata schema.
Key | Description | Display Benefits |
---|---|---|
embedding | 1 to 4096 for Index. 1 to 2000 for Active | Filtering by embeddings, similarity search, 2D scatter plot visualization (Coming Soon) |
clientMetadata
to ensure they display correctly in custom Label Editor layouts.
"encord-layout-group"
key determines which files are shown together — files with the same "encord-layout-group"
value are displayed simultaneously. Both files in the example appears in the Label Editor simultaneously since they have the same "encord-layout-group"
value.
"encord-editor-grid-position"
key, set to either A
or B
, specifies the exact position of each file within the label editor.
audioMetadata
and one does not.
audioMetadata
with each audio file when importing your audio files at scale. Including audioMetadata
significantly improves the import speed of data when importing data at scale. When the audioMetadata
flag is present in the JSON file, we directly use the supplied metadata without performing any additional validation, and do not store the file on our servers. To guarantee accurate labels, it is crucial that the metadata you provide is accurate.Upload is still in progress, try again later!
is returned, use the
script to check the upload status to see whether the upload has finished.<private_key_path>
with the path to your private key.<integration_title>
with the title of the integration you want to use.<folder_name>
with the folder name. The scripts assume that the specified folder name is unique.path/to/json/file.json
with the path to a JSON file specifying which cloud storage files should be uploaded.A folder to store my files
with a meaningful description for your folder."my": "folder_metadata"
with any metadata you want to add to the folder.2
and Q
, but for you they might be different.2
to select the Winner Classification.
The options for the Classification appear.
Q
to select Yes.
N
to save the Classifications on the audio file.
Q
to select Yes.
N
to save the Classifications on the audio file.
N
to approve the Classifications on the audio file.
N
to approve the Classifications on the audio file.
B
to reject the Classifications on the audio file.
A dialog appears.
B
to reject the Classifications on the audio file.