Explore dataset (Text Project)
Go to Explore to search documents in Text Projects using more specific criteria than just file names. The fields and values entered in the query bar match the JSON format.
How does it work?
Explore works in two ways: you can type the queries yourself or use autosuggestions. Autosuggestion makes it easier for you to generate the queries.
To generate a query:
- Go to the Explore tab.
- If the data isn't synced, click Sync data. If the dataset is synced, skip to Step 3.
- Click the input bar.
- Choose the suggested fields and operators or type the query yourself.
- To run the query, press Enter on the keyboard.
- If your permission to use Explore was disabled and then enabled, then you’ll have to sync the data again.
- If you're experiencing issues with the dataset, you can click Resync the dataset.
- Hover over the information icon next to the query bar to see the distribution of the query results by status.
Display folder content
In the drop-down list in Explore, you can select a folder to display its items in Explore.
- Select All items to display all the project’s items.
- Select Root items to display all the project’s root items.
- Select any other folder to display its content.
Example queries
Function | Query |
---|---|
To search for items that have the In Progress status and are where assigned to the annotator whose email is [email protected] | metadata(status = InProgress AND annotatorEmail = [email protected] ) |
To search for items that are in progress and have at least one instance that has the tag Negative | instance(type = tag AND className = Negative ) AND metadata(status = InProgress ) |
To search for items that have the annotation status QualityCheck | metadata(status = QualityCheck ) |
To search for items that contain tags | instance(type = tag) |
To search for items that contain more than 4 tags | instanceCount(type = tag ) > 4 |
To search for items that contain the following text: Reviews from the website | freeText = Reviews from the website |
To search for items whose assigned annotator has the following email address: [email protected] | metadata(annotatorEmail = [email protected]) |
To search for items that don't have the NotStarted and InProgress annotation statuses | metadata(status NOT IN [NotStarted, InProgress]) |
To search for items that have the Completed and Skipped annotation statuses and are located in Folder 1 | metadata(status IN [Completed, Skipped]) AND folder = Folder 1) |
Click on the query bar to see the last 3 unique queries.
Grid view
Columns
Choose how many items there are per row. The number of items per row is 3 by default.
Display settings
- Check the Information box to show the item name and item status.
- Check the Tags box to show the tags.
Fields and values
Metadata
You can search the metadata (metadata
) by the following fields:
Field | Description | Value |
---|---|---|
status | Item status | NotStarted InProgress QualityCheck Returned Completed Skipped |
approvalStatus | Item's approval status | true (Approved) false (Disapproved)null (None) |
lastAction.email | Email address of the project contributor who made the last change to the item. | The value is an email address. |
name | Item file name | The value is a name. |
annotatorEmail | The assigned annotator’s email address. | The value is an email address. |
qaEmail | The assigned QA’s email address. | The value is an email address. |
priority | Priority score | Numeric value |
Instance and instance count
You can search instances (instance
) and instance counts (instanceCount
) by the following fields:
Field | Description | Value |
---|---|---|
type | Instance type | entity tag |
className | Class name | The value is a class name. |
attributes.name | Attribute name | The value is an attribute name. |
attributes.groupName | Attribute group name | The value is an attribute group name. |
createdBy.email | Email address of the project contributor who created the instance. | The value is an email address. |
createdBy.role | Role of the project contributor who created the instance. | Annotator QA Admin |
updatedBy.email | Email address of the project contributor who made the last change to the instance. | The value is an email address. |
updatedBy.role | Role of the project contributor who made the last change to the instance. | Annotator QA Admin |
createdAt | Date when the instance was created. | The value is a date with this format YYYY-MM-DD. |
updatedAt | Date when the instance was last updated. | The value is a date with this format YYYY-MM-DD. |
About class names
If the class name contains an operator (and, or, in, not in, contains), the query will handle them as operators, not as words in class names. For example, if the class name is
Happy and excited
, the query will handle the wordhappy
and the wordexcited
separately. Instead, you can use symbols, such as underscores, to separate the words. SoHappy and excited
would be changed tohappy_and_excited
.
Folder
You can search folders by the following fields:
Field | Description | Value |
---|---|---|
folderName | Folder name | The value is a name. |
folderStatus | Folder status | NotStarted InProgress Completed OnHold Undefined |
To search for root folders:
folder [insert operator here] root
Example: folder = root
If the status of a folder has been changed, refresh the Explore tab for the queries to work correctly.
Free text
You can search free texts (freeText
) this way:
freeText [insert operator here] text
Example: freeText = Product descriptions.
Random
To get a randomized subset of data:
Operator | Description | Value |
---|---|---|
random | Used to get a randomized subset of data | Numeric value. |
When you run a query with random
, you’ll get a randomized subset of data. This will help you increase efficiency in checking the quality of the annotations and the dataset’s health.
So, if the query is metadata(status = InProgress ) random 50
, 50 random items from the project that have the in In Progress
status will be returned.
Custom metadata
You can search by custom metadata (customMetadata
) this way:
Field | Description | Value |
---|---|---|
customMetadata | Custom metadata | Depending on the field type. Please check this page for more information. |
Operators
Operator | Description |
---|---|
= | Equal |
!= | Not equal |
> | Greater than |
< | Less than |
>= | Greater than or equal to |
<= | Less than or equal to |
() | Query parentheses |
[] | Array |
AND | Returns True if both statements are true |
OR | Returns True if either statements are true |
IN | Set of values to consider |
NOT IN | Set of values to not consider |
CONTAINS | Used to search for a substring and returns the results containing that substring |
When the attribute has a numeric type, the following operators will be supported for
attributes.name
: > < =< !=
Sort list
You can sort the list in Data by:
Field | Description | Value |
---|---|---|
metadata.name | Item name | ASC (ascending) DESC (descending) |
metadata.status | Item status | ASC (ascending) DESC (descending) |
metadata.lastAction.date | Date when the item was last updated. | ASC (ascending) DESC (descending) |
metadata.qaEmail | Email address of the assigned QA. | ASC (ascending) DESC (descending) |
metadata.annotatorEmail | Email address of the assigned annotator. | ASC (ascending) DESC (descending) |
instanceCount | The number of instances the item has. | ASC (ascending) DESC (descending) |
Metadata status order
The order is the following:
Not Started
,In Progress
,Quality Check
,Returned
,Complete
, andSkipped
.
Save query
To save a query:
- Type a query in the query bar.
- Click on the star at the right edge of the query bar.
- In the popup, type a query name.
- Click Save.
- The maximum number of characters for a query is 60.
- You can save up to 50 queries.
- If you’ve successfully saved the query, you'll see this message: “You’ve successfully saved the query.”
- If the query can’t be saved, you'll see this message: “Oops! Something went wrong.”
Rename query
To rename a query:
- Click on the star in the query bar.
- Click the three dots next to the query you want to rename.
- Select Rename.
- Type a new query name.
- Click Rename.
If you’ve successfully renamed the query, you'll see this message: “You’ve successfully renamed the query.”
If the query can’t be renamed, you'll see this message: “Oops! Something went wrong.”
Delete query
To delete a query:
- Click on the star in the query bar.
- Click the three dots next to the query you want to rename.
- Select Delete.
- If you’ve successfully deleted the query, you'll see this message: “You’ve successfully deleted the query.”
- If the query can’t be deleted, you'll see this message: “Oops! Something went wrong.”
Subsets
Add items to a subset
To add an item or multiple items to a subset:
- In Explore, select an item or multiple items.
- Click Add to subset.
- Choose an existing subset or create a new one. To create a new subset, type a non-existing name in the search bar and click Create subset.
- Click Save.
Copy items to a subset
To copy an item or multiple items from one subset to another:
- Go to the subset.
- Select an item or multiple items.
- Click the Copy/Move items button.
- Choose the subset where you want to copy the item(s).
- Click Copy.
Messages
- If you’ve successfully copied the items, you’ll see this message:
You added [number of items] item(s) to the selected subset(s).
- If the items are taking too long to be copied, you’ll see this message:
You added [number of added items]/[number of total items] item(s) to the selected subset(s).
- If something goes wrong, you’ll see this message:
Oops! Something went wrong.
Move items from one subset to another
To move an item or multiple items from one subset to another:
- Go to the subset.
- Select an item or multiple items.
- Click the Copy/Move items button.
- Go to the Move tab.
- Choose the subset where you want to copy the item(s).
- Click Move.
Messages
- If you’ve successfully moved the items, you’ll see this message:
You successfully moved [number of items] item(s).
- If the items are taking too long to be moved, you’ll see this message:
[number of updated items]/[number of total items] item(s) moved
- If something goes wrong, you’ll see this message:
Oops! Something went wrong.
View subset
To view all your subsets, click on Display Settings next to the search bar. You’ll find all your subsets under Subsets.
Delete a subset
To delete a subset:
- Find the subset you want to delete under Subsets in the left panel.
- Click on the three dots > Delete.
- In the popup, select Delete.
Delete items from a subset
To delete items from a subset:
- Select items in a subset.
- Click Remove From Subset.
You can perform the following bulk actions in a subset: change the status of items, approve/disapprove items, set priority scores, and download a dataset.
Change status in bulk
You can change the status of the item(s) that appear as a result of your query.
To change the status of an item or multiple items:
- Run a query.
- Select an item or multiple items.
- Click Change Status.
- Choose a status.
- Click Change.
Assign items in bulk
To assign one or multiple items:
- Select one or multiple items/instances.
- Click Assign in the menu at the bottom of the page.
- Choose an Annotator and/or a QA.
- Click Assign.
- When you successfully make the assignment, you’ll see this message:
You’ve successfully assigned the selected items.
- If there’s an error, you’ll see this message:
Oops! Something went wrong.
To unassign one or multiple items:
- Select one or multiple items/instances.
- Click Assign in the menu at the bottom of the page.
- In the drop-down list(s) under Annotator and/or QA, choose Unassigned.
- Click Assign.
If there’s an error, you’ll see this message:
Oops! Something went wrong.
Approve/Disapprove items in bulk
To change the approval status of an item or multiple items:
- When in Grid View, select one item or multiple items.
- Click the Approve/Disapprove items button at the bottom menu.
- Choose the status: Approve, Disapprove, or None.
- Click Change.
- If the status was changed successfully, you’ll see this message:
You changed the approval status of [number of items] item(s).
- When it takes a while to change the approval status, you’ll see this message:
[number of updated instances]/[total number of instances] instances updated.
- In case of any errors, you’ll see this message:
Oops! Something went wrong.
Set priority scores in bulk
To set the priority scores in bulk:
- Select multiple items.
- Click Priority scores.
- Choose a value.
- Click Set.
Annotators will receive the items with a higher priority score first.
Add tags in bulk
To add tags to one or multiple items:
- When in Grid View, select multiple items by clicking their checkbox or clicking Select all.
- Click Add/Remove tags.
- Click on Add tag.
- Select a tag from the dropdown.
- Select or input attributes, if applicable.
- Click Add.
- If the tags are added successfully, you’ll see the following message:
You’ve successfully added a tag on [number of items] item(s).
- If the tags were not added successfully, you’ll see this message:
Oops! Something went wrong.
To remove tags from one or multiple items:
- When in Grid View, select multiple items by clicking their checkbox or clicking Select all.
- Click Add/Remove tags.
- Click on Remove tag.
- Select a tag from the dropdown.
- Click Remove.
- If the tag was removed successfully, you’ll see this message:
You’ve successfully removed [tag_name] from [number of items] item(s).
- If the tag was not removed successfully, you’ll see this message:
Oops! Something went wrong.
Download items
To download items from the selected items in the results:
- Go to the Explore tab.
- Select the items you want to download.
- Click Download.
- When the download is ready, you’ll be redirected to the Download page. Find your dataset and click the download button to download it.
If you want to send the dataset to someone, click the link button and copy the link. Anyone who has the link can access the data.
Download limitations
A user can generate up to 50 downloads per day and per project. Only up to 50 downloads can be available. If you have 50 downloads in a project and create a new one, the oldest download will be deleted to make space for the new project.
The download package contains:
- A folder that contains the classes in JSON files.
- A folder that contains the annotations in JSON files.
If some of the items are inside folders, then their corresponding files will be located inside folders in the download package as well. The folder structure is kept the same.
Updated about 3 hours ago