Follow the end to end walkthrough below to learn how to set up a custom Label Editor configuration based on client metadata. This End-to-end example assumes you configure the Label Editor so that two files are displayed at a given time.
This end-to-end example assumes that your files are stored in cloud storage.
Use the Encord SDK to import a metadata schema into Encord. The fields encord-LayoutGroup
and encord-EditorGridPosition
are the key client metadata used later for configuring the Label Editor layout. If you need to add additional client metadata to your schema, include them in the script below.
Read more about metadata schemas here.
Before registering your cloud data to Encord you must first create a JSON file specifying the files you want to register.
When the audioMetadata
, imageMetadata
, or videoMetadata
flags are 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. It is crucial that the metadata you provide is accurate. For most applications these flags can be omitted.
All of the following examples import 4 objects with the following client metadata:
encord-EditorGridPosition
: Can take the values A
or B
. A
and B
are the two possible positions inside the Label Editor.encord-LayoutGroup
: Files with the same encord-LayoutGroup
values are displayed concurrently in the Label EditorAll files in Encord must be stored within folders. Therefore, you need to create a folder before registering any data with Encord. To create a folder:
Give the folder a meaningful name and description.
Click Create to create the folder. The folder is listed in Files.
Using the JSON file you created you can import or register your audio data, using the UI or the SDK.
Import data using in the UI
Register data using in the SDK
To use your data in Encord, it must be uploaded to the Encord Files storage. Once uploaded, your data can be reused across multiple Projects and contain no labels or annotations themselves. Files stores your data, while Projects store your labels. The following script creates a folder in Files and uses your AWS integration to register data in that folder.
The following script creates a new folder in Files and initiates uploads from AWS. It works for all file types.
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.Ensure that you:
<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.The script has several possible outputs:
Create a Dataset
Select the folders containing the files you want to attach to the Dataset. To select individual files, double-click a folder to see its contents, and select the files you want to add to the Dataset.
Click Attach data to attach the selected files to the Dataset.
Create an Ontology
Give your Ontology a meaningful title and description. A clear title and description keeps your Ontologies organized.
Click Next to continue.
To add objects:
To add attributes to an object:
You can add attributes to objects that define the object’s characteristics. For example the object “Apple” can have an attribute “Color”.
Click the arrow icon next to an object to add attributes to the object.
Give the attribute a name. For example “Color”.
Click the attribute type to change the attribute type. The default attribute type is a text field.
Click Add option to add an option, if you have chosen a radio button or checklist attribute.
Enter a name for the attribute option. For example, the attribute “Color” can have the options “Red”, “Green”, and “Yellow”.
Click the Back to parent button to return the Ontology creation view.
To add a classification:
Configure classifications:
You can configure classifications to change the classification type, and to add classification options to radio buttons and check lists.
Create a Project
If you are part of an Organization, an optional Project tags drop-down is visible. Project tags are useful for categorizing and finding your Projects. Select as many tags as are relevant for your Project.
Click the Attach ontology button.
Select the Ontology you created previously from the list using the Select button.
Click OK to attach the Ontology to the Project.
Click the Attach datasets button.
Select the Dataset you created previously from the list using the Attach button.
Select the template you want to use and click Load template.
Click Create project to finish creating the Project.
Give your Ontology a meaningful title and description. A clear title and description keeps your Ontologies organized.
Click Next to continue.
To add objects:
To add attributes to an object:
You can add attributes to objects that define the object’s characteristics. For example the object “Apple” can have an attribute “Color”.
Click the arrow icon next to an object to add attributes to the object.
Give the attribute a name. For example “Color”.
Click the attribute type to change the attribute type. The default attribute type is a text field.
Click Add option to add an option, if you have chosen a radio button or checklist attribute.
Enter a name for the attribute option. For example, the attribute “Color” can have the options “Red”, “Green”, and “Yellow”.
Click the Back to parent button to return the Ontology creation view.
To add a classification:
Configure classifications:
You can configure classifications to change the classification type, and to add classification options to radio buttons and check lists.
After creating your Project, import a custom layout for the Label Editor. Start by creating a JSON file that determines the layout.
Common layouts for two tasks displayed simultaneously are Side by Side and Stacked (On top of one another).
The Side By Side layout:
The Stacked layout: