diff --git a/articles/create-manage-projects/filters/a-guide-to-filter-inside-of-annotation-results-object.md b/articles/create-manage-projects/filters/a-guide-to-filter-inside-of-annotation-results-object.md new file mode 100644 index 0000000..0079f44 --- /dev/null +++ b/articles/create-manage-projects/filters/a-guide-to-filter-inside-of-annotation-results-object.md @@ -0,0 +1,107 @@ +--- +author_id: 15914823752205 +category_id: 39646615083277 +created_at: '2025-01-09T16:24:44Z' +labels: [] +locale: en-us +position: 0 +section_id: 39649211977869 +title: A Guide to Filter inside of annotation.results object +updated_at: '2025-09-17T18:44:48Z' +zendesk_article_id: 33346631335565 +--- + +# Understanding Annotation Results + +  +A Label Studio annotation consists of regions, stored as a list in the `annotation.result` field. For instance: + +``` + "annotations": [ + { + "id": 44553935, + "result": [ + { + "id": "zLSY-XLk64", + "type": "choices", + "value": { + "choices": [ + "yes" + ] + }, + "origin": "manual", + "to_name": "query", + "from_name": "understand" + }, + { + "id": "uh87CbF1k3", + "type": "choices", + "value": { + "choices": [ + "no" + ] + }, + "origin": "manual", + "to_name": "query", + "from_name": "consistency" + }, + { + "id": "Yd_BW-pLht", + "type": "choices", + "value": { + "choices": [ + "other" + ] + }, + "origin": "manual", + "to_name": "query", + "from_name": "consistency_reason" + }, + ... + ] +``` + +  +In most cases, regions have a `from_name` field, which links to the control tag from your labeling config. Each region's `value` stores the control's response. +  + +# Building the filter + +  +As follows from annotation result understanding, our can identify your answers using a pair `(from_name, value)`.  +  +Based on the `annotation.result`, you can identify answers using a `(from_name, value)` pair. The `annotation.result` is stored as a JSON string in the Label Studio database, allowing us to search like a simple string. To construct a filter let's consider this region: + +``` +{ + "id": "uh87CbF1k3", + "type": "choices", + "value": { + "choices": ["no"] + }, + "origin": "manual", + "to_name": "query", + "from_name": "consistency" +} +``` + +  + +1. Keep only the part that has value and control tag name. +2. Remove `\n` and spaces that surround `{` and `}`. + +  +As the result we have:  + +``` +["no"]}, "origin": "manual", "to_name": "query", "from_name": "consistency" +``` + +  + +# Use the filter in the Data Manager + +  +Now, copy this filter into the **Data Manager.** Go to **Filter** → **Annotation Result** → **Contains** and paste `["no"]}, "origin": "manual", "to_name": "query", "from_name": "consistency"`: +  +![](https://labelstudio.zendesk.com/attachments/token/BDMVDE9r5o05xmlHxm66kCIJB/?name=image.png) diff --git a/articles/create-manage-projects/label-interface/audio-wave-doesn-t-match-annotations.md b/articles/create-manage-projects/label-interface/audio-wave-doesn-t-match-annotations.md new file mode 100644 index 0000000..5db74f4 --- /dev/null +++ b/articles/create-manage-projects/label-interface/audio-wave-doesn-t-match-annotations.md @@ -0,0 +1,18 @@ +--- +author_id: 18127715992333 +category_id: 39646615083277 +created_at: '2024-01-30T01:22:16Z' +labels: [] +locale: en-us +position: 0 +section_id: 39649206773773 +title: Audio wave doesn't match annotations +updated_at: '2025-09-17T17:46:42Z' +zendesk_article_id: 23638672221325 +--- + +If you find that after annotating audio data, the visible audio wave doesn’t match the timestamps and the sound, try converting the audio to a different format. For example, if you are annotating mp3 files, try converting them to wav files. + +``` +ffmpeg -y -i audio.mp3 -ar 8k -ac 1 audio.wav +``` diff --git a/articles/create-manage-projects/label-interface/how-do-i-get-all-choice-items-to-render-in-a-single-line.md b/articles/create-manage-projects/label-interface/how-do-i-get-all-choice-items-to-render-in-a-single-line.md new file mode 100644 index 0000000..7170236 --- /dev/null +++ b/articles/create-manage-projects/label-interface/how-do-i-get-all-choice-items-to-render-in-a-single-line.md @@ -0,0 +1,23 @@ +--- +author_id: 16760288545421 +category_id: 39646615083277 +created_at: '2023-12-07T17:24:16Z' +labels: [] +locale: en-us +position: 0 +section_id: 39649206773773 +title: 'How do I get all Choice items to render in a single line? ' +updated_at: '2025-09-17T17:46:20Z' +zendesk_article_id: 22052885933325 +--- + +To display the choices in a single line, you can use the `showInline="true"` attribute within your `` tag. This will render the choices horizontally instead of vertically. Here's how you can modify your existing `` tag: + +``` + + + + +``` + +By adding `showInline="true"`, the choices "yes" and "no" will be displayed in a single line, achieving the layout you're looking for. diff --git a/articles/create-manage-projects/label-interface/how-do-i-limit-the-max-width-of-taxonomy-fields.md b/articles/create-manage-projects/label-interface/how-do-i-limit-the-max-width-of-taxonomy-fields.md new file mode 100644 index 0000000..48d5af9 --- /dev/null +++ b/articles/create-manage-projects/label-interface/how-do-i-limit-the-max-width-of-taxonomy-fields.md @@ -0,0 +1,46 @@ +--- +author_id: 16760288545421 +category_id: 39646615083277 +created_at: '2024-06-24T16:23:59Z' +labels: [] +locale: en-us +position: 0 +section_id: 39649206773773 +title: How do I limit the max width of taxonomy fields? +updated_at: '2025-09-17T17:45:28Z' +zendesk_article_id: 27845825489677 +--- + +### Summary + +This article provides guidance on using CSS adjustments to limit the maximum width of taxonomy fields in Label Studio. By setting the `maxWidth` attribute, users can control the width of taxonomy dropdowns to ensure that long texts do not overflow or cause layout issues. This is particularly useful for maintaining a clean and readable interface when dealing with extensive taxonomy options. + +### Troubleshooting steps + +1. **Identify the Taxonomy Field:** Locate the taxonomy field in your labeling interface configuration. It will look something like this: + + ``` + + ``` +2. **Add the `maxWidth` Attribute:** To limit the maximum width of the taxonomy field, add the `maxWidth` attribute with a desired value. For example, to set the maximum width to 300 pixels: + + ``` + + ``` +3. **Adjust the Dropdown Width (if necessary):** If the dropdown list is too narrow, you can also set the `dropdownWidth` attribute to ensure it fits the content. For example, to set the dropdown width to 500 pixels: + + ``` + + ``` +4. **Test the Changes:** Save your changes and reload the Label Studio interface to ensure that the taxonomy field and dropdown now adhere to the specified width constraints. +5. **Fallback to Old Version (if needed):** If the new taxonomy settings do not meet your requirements, you can revert to the previous version by using the `legacy` attribute: + + ``` + + ``` + +### More resources + +- [Label Studio Taxonomy Tag Documentation](https://docs.humansignal.com/tags/taxonomy) + +By following these steps, you can effectively manage the width of taxonomy fields in Label Studio, ensuring a better user experience and interface layout. diff --git a/articles/create-manage-projects/label-interface/how-to-display-long-texts-in-a-separate-static-text-field.md b/articles/create-manage-projects/label-interface/how-to-display-long-texts-in-a-separate-static-text-field.md new file mode 100644 index 0000000..7a28c6c --- /dev/null +++ b/articles/create-manage-projects/label-interface/how-to-display-long-texts-in-a-separate-static-text-field.md @@ -0,0 +1,66 @@ +--- +author_id: 16760288545421 +category_id: 39646615083277 +created_at: '2024-06-17T16:38:33Z' +labels: [] +locale: en-us +position: 0 +section_id: 39649206773773 +title: How to Display Long Texts in a Separate Static Text Field +updated_at: '2025-09-17T17:44:43Z' +zendesk_article_id: 27641232245517 +--- + +## Summary + +This article provides a step-by-step guide on how to display long texts in a separate static text field within Label Studio. This approach helps prevent long texts from spreading outside the labeling interface and ensures that users can view the entire text without scrolling issues. Follow these troubleshooting steps to implement this solution effectively. + +## Troubleshooting Steps + +### Step 1: Modify the Labeling Configuration + +To display long texts in a separate static text field, you need to adjust the labeling configuration in your project. Use the `` and `` tags to create a static text field. + +1. Open your project’s labeling configuration. +2. Add a new `` tag to wrap the text field. +3. Use the `` tag to display the long text within the `` tag. + +``` + +
+ + + +
+