-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
docs: DOC-256: Comments page rewrite (#6533)
Co-authored-by: caitlinwheeless <[email protected]> Co-authored-by: Jo Booth <[email protected]>
- Loading branch information
1 parent
73a2aaa
commit 352f98d
Showing
6 changed files
with
102 additions
and
164 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,234 +1,172 @@ | ||
--- | ||
title: Comments and notifications | ||
title: Comments and notifications | ||
short: Comments and notifications | ||
type: guide | ||
tier: enterprise | ||
section: "Create & Manage Projects" | ||
section: "Review & Measure Quality" | ||
order: 0 | ||
order_enterprise: 146 | ||
meta_title: Comment and notification systems in Label Studio | ||
meta_description: The Comments and Notifications feature defines how annotators, reviewers and administrators communicate and receive updates on projects and tasks. | ||
order_enterprise: 306 | ||
meta_title: Comment in Label Studio Enterprise | ||
meta_description: The comments and notifications features define how annotators, reviewers and administrators communicate and receive updates on projects and tasks. | ||
--- | ||
|
||
Annotators, reviewers, and administrators can use comments to do the following: | ||
|
||
- Speed up the labeling process | ||
- Increase the annotation quality | ||
- Build more solid labeling and review processes | ||
|
||
Users can discuss task issues and other problems during labeling and reviewing processes using Comments and Notifications in Label Studio Enterprise. | ||
|
||
|
||
## Workflow overviews | ||
|
||
The following two workflows are flexible and can be combined. For example, in Figure 1A, Annotators don’t have access to the Data Manager and they would only use the Label Stream. They can write comments there, resolve them, and see notifications. Meanwhile, other roles like Managers or Administrators can filter tasks by “Unresolved comments” in the Data Manager and use the second workflow (see Figure 1B). | ||
|
||
<center> | ||
<br> | ||
<img src="/images/workflow-notifications.png"/> | ||
<br><i>Figure 1A. The workflow based on notifications</i><br> | ||
|
||
<br> | ||
|
||
<img src="/images/workflow-data-manager.png" style="max-width: 17rem;"/> | ||
<br><i>Figure 2B. The workflow based on the Data Manager</i><br> | ||
</center> | ||
|
||
### Notification workflow | ||
|
||
This approach is centered on the notification panel (see figure 1A). The entry point here is the notification link, it allows going into editing or review mode (depending on your role). Note that label or review streams are deactivated there, only a task from a notification link is shown. | ||
|
||
#### Annotators | ||
|
||
##### Write comments | ||
|
||
1. Annotator starts the labeling stream. | ||
2. Annotator sees a new task and writes a comment. | ||
3. Who will see the notification about this comment? | ||
* a. If this comment is the first in a task draft or an annotation, then it will be shown: | ||
- To all reviewers on the current project. | ||
- To all administrators on the current project. | ||
* b. If this comment is not the first one, then it will be shown. | ||
- To all users who were involved in the initial comment thread only. | ||
|
||
##### Read other’s comments | ||
|
||
Annotators will see notifications from reviewers and other users when another user’s comment is added to the annotator draft or annotation | ||
|
||
!!! note | ||
An annotator must be added to the project or workspace to see associated comments. | ||
|
||
#### Reviewers and other higher roles | ||
Comments are a Label Studio Enterprise feature that allows communication between reviewers and annotators: | ||
|
||
##### Write comments | ||
<div class="noheader rowheader"> | ||
|
||
Reviewers (or other higher roles) can write comments during the review stream. It is especially useful when a reviewer rejects an annotation. | ||
<table> | ||
<thead> | ||
<tr> | ||
<th>Annotators</th> | ||
<th>Reviewers</th> | ||
</tr> | ||
</thead> | ||
<tr> | ||
<td> | ||
|
||
1. Reviewer starts the review stream | ||
2. Reviewer sees a task with an annotation and writes a comment | ||
3. Who will see the notification about this comment? | ||
1. Annotator who created this annotation | ||
2. Other commentators who wrote comments in this comment thread | ||
**Annotator to reviewer communication** | ||
|
||
##### Read comments | ||
|
||
1. Reviewers will see notifications from annotators and other users when: | ||
- Ask for clarification on a task | ||
- Provide reasoning or context for their annotation | ||
|
||
</td> | ||
<td> | ||
|
||
- The comment is the first one in a task draft or an annotation | ||
- There is a new comment in an annotation that were reviewed by this reviewer previously | ||
**Reviewer to annotator communication** | ||
|
||
!!! note | ||
A reviewer must be added to the project or workspace to see associated comments. | ||
- Answer questions | ||
- Give feedback to help the annotator improve | ||
|
||
### Submitted annotations vs postponed drafts | ||
</td> | ||
</tr> | ||
</table> | ||
|
||
The standard labeling workflow is to submit an annotation. This action affects statistics, agreement, and annotator performance scores. In some cases where annotators want to avoid submitting (e.g. while they wait for their comment to be resolved), they can use to postpone draft functionality by clicking blue arrow button in the labeling stream: | ||
</div> | ||
|
||
<br> | ||
<img src="/images/comments-notifications/postpone.png" class="gif-border"> | ||
<br> | ||
This annotator-reviewer feedback loop is an important tool in your review workflow, allowing you to: | ||
|
||
It’s helpful to combine postponed drafts with comments, because users can clarify some questions without affecting a dataset labeling state. Annotators can access their postponed drafts in the following ways: | ||
|
||
- Postponed drafts will be re-queued at the end of the labeling stream after the annotator completes all tasks | ||
- Using the Data Manager | ||
- Using task history navigation <img src="/images/comments-notifications/history.png" clas="gif-border" style="height:25px"> | ||
Note: If the user refreshes the page, the navigation history will be lost. This inconvenience will be fixed soon in upcoming releases. | ||
- Using notification links when somebody answers to comments | ||
- Speed up the labeling process | ||
- Increase the annotation quality | ||
- Build more solid labeling and review processes | ||
|
||
![Screenshot of comments](/images/review/comments.png) | ||
|
||
|
||
### Data manager workflow | ||
## Permissions | ||
|
||
You can add comments to tasks independent of annotation and action such as **Skip** or **Accept**. | ||
|
||
1. In the Label Studio UI, navigate to your Data Manager. | ||
All users have the following commenting permissions for any annotations that they would otherwise have access to view: | ||
|
||
2. Click on the **Columns** drop-down to filter the columns based on the following: | ||
- View the **Comments** panel and read previous comments. | ||
- Add new comments. | ||
|
||
<br> | ||
<img src="/images/comments-notifications/columns.png" class="gif-border"/> | ||
<i>Figure 2: Columns drop-down.</i> | ||
Additional permissions are as follows: | ||
|
||
- **Comments**: Total number of comments for a particular task. | ||
- **Unresolved comments**: Comments that are not yet resolved. The total number of unresolved comments are displayed in this column. | ||
- **Commented at**: The date and time at which the comment was made. | ||
- **Commented authors**: Users who wrote comments. | ||
|
||
<br> | ||
<img src="/images/comments-notifications/commented-at.png" class="gif-border"/> | ||
<i>Figure 3: Commented at.</i> | ||
| Action | Annotator | Reviewer and higher roles| | ||
|-----------------|:---------:|:--------:| | ||
| Add comment | true | true | | ||
| View comment | true | true | | ||
| Resolve/unresolve own comment | true | true | | ||
| Resolve/unresolve other comments | false | true | | ||
| Delete own comment | true | true | | ||
| Delete other comments | false | false | | ||
| Link/unlink own comment | true | true | | ||
| Link/unlink other comments | false | false | | ||
|
||
|
||
Now, you can also filter by the number of comments and comments added or by the authors using the **Filter** drop-down located next to the **Columns** drop-down. You can add more filters to display tasks based on your filtering requirements. | ||
## Add a comment | ||
|
||
<br> | ||
<img src="/images/comments-notifications/comment-by-author-filter.png" class="gif-border"/> | ||
<i>Figure 4: Filter to comment by author.</i> | ||
You can add comments from the **Comments** panel when viewing an annotation. All users have access to the **Comments** panel. | ||
|
||
To resolve comments, click on a task and on the right side of the window you will see the **Comments** section where you can add a comment or click the three dots (**...**) to resolve or unresolve comments. | ||
![Screenshot of comments](/images/review/comment_panel.png) | ||
|
||
<br> | ||
<img src="/images/comments-notifications/resolve.png" class="gif-border"/> | ||
<i>Figure 5: Resolve comments.</i> | ||
### Link comments to regions and fields | ||
|
||
When you click **Resolve**, you will see a green color check mark next to your comment. This represents a resolved comment. | ||
You can link your comment to a specific area within an annotation. | ||
|
||
<br> | ||
<img src="/images/comments-notifications/resolved-comment-green-tick-mark.png" class="gif-border" style="max-width: 300px!important;"/> | ||
<br/> | ||
<i>Figure 6: Green color check mark for resolved comments.</i> | ||
This can be a region (for example, a bounding box or a span of text) or it can be a field (for example, a classification). | ||
|
||
![Gif of linking a comment](/images/review/comment_links.gif) | ||
|
||
To unresolve comments, click the three dots (**...**) >> **Unresolve** button. | ||
Note the following: | ||
|
||
<br> | ||
<img src="/images/comments-notifications/unresolve.png" class="gif-border"/> | ||
<i>Figure 7: Unresolved comments.</i> | ||
* You can link comments to fields within the labeling configuration. However, if the field is a classification, choice, or taxonomy, you can only attach a comment if there is already a selection. | ||
* You can only link comments to an entire text area. You cannot link comments to regions within text areas. | ||
* Linking is not supported for [Ranker](/tags/ranker) or [Pairwise](/tags/pairwise) fields. | ||
|
||
There is a special pink icon that appears on comments attached to annotations or drafts in the dropdown menu that indicates unresolved comments: | ||
## Comment actions | ||
|
||
<br> | ||
<img src="/images/comments-notifications/comment-pink.png" class="gif-border"> | ||
</br> | ||
<i>Figure 8: Pink color check mark for unresolved comments.</i> | ||
The actions you can perform depend on [your user role permissions](#Permissions) and whether it's your comment. You can access comment actions from the overflow menu: | ||
|
||
![Screenshot of comment action menu](/images/review/comment_actions.png) | ||
|
||
## Comments | ||
|
||
The **Comments** feature allows Annotators Reviewers and other higher roles to communicate and discuss queries on Label Studio Enterprise. Users will be notified of comments if they are associated with the task, and new comments will show up in the **Notifications** panel for a quick reference. Users can also filter and sort tasks by **Comments** status in the **Data Manager** view, such as finding tasks with unresolved comments from a particular user. | ||
## Filter for comments | ||
|
||
### Roles and Capabilities | ||
The Data Manager has several columns to display comment information: | ||
|
||
#### All users | ||
| Column | Description | View permissions | | ||
|-----------------|:---------:|:--------:| | ||
| **Comment texts** | The text in the comment. | All user roles | | ||
| **Comments** | Total number of comments for a particular task. | All user roles | | ||
| **Unresolved comments** | Total number of comments that are not yet resolved. | All user roles | | ||
| **Commented at** | The date and time at which the comment was made. | All user roles except Annotator | | ||
| **Commented authors** | User who wrote comments. | All user roles except Annotator | | ||
|
||
All users with access to Label Studio UI can do the following: | ||
!!! note | ||
Users in the Reviewer or Annotator role must be granted access to view the Data Manager. You can grant access in the [project settings](project_settings_lse). | ||
|
||
- Edit and delete own comments in a task. | ||
- By default, you can see the comment section while annotating tasks. | ||
- Add a comment by clicking on the input field and then typing your comment. | ||
- Send and save the comment by clicking on the send (>) icon. | ||
|
||
#### Annotators | ||
## Require comments | ||
|
||
As an **Annotator**, you can do the following: | ||
You can configure the project so that annotators and reviewers are required to leave comments after taking specific actions: | ||
|
||
- See comments from your annotations and drafts. | ||
- Resolve your own comments. | ||
* [**Annotation > Annotating Options > Annotators must leave a comment on skip**](project_settings_lse#Annotation) | ||
* [**Review > AReviewers must leave a comment on reject**](project_settings_lse#Review) | ||
|
||
#### Reviewers and higher roles | ||
## Comment notifications | ||
|
||
As a **Reviewer**, you can do the following: | ||
To see notifications, click your user profile icon in the upper right. | ||
|
||
- See comments added by **Annotators** and other users. | ||
- Resolve and unresolve own comments. | ||
- Resolve and unresolve comments by others. | ||
Use the overflow menu to mark notifications as read or unread. | ||
|
||
!!! note | ||
|
||
- Comments added will trigger notifications. | ||
- Comments are created in context of an annotation. | ||
- All users with access to a project will receive notifications when a comment is added. | ||
![Screenshot of notifications](/images/comments-notifications/notifications.png) | ||
|
||
|
||
### Permissions | ||
!!! note | ||
Notifications that have already been read are denoted with a gray background. | ||
|
||
Table 1 displays the three key user actions on the **Comments** feature. | ||
### Annotators | ||
|
||
<i> Table 1: User permissions.</i> | ||
Annotators can write comments on their own annotations. | ||
|
||
| Action | Annotator | Reviewer and higher roles| | ||
|-----------------|:---------:|:--------:| | ||
| Add comment | true | true | | ||
| View comment | true | true | | ||
| Resolve comment | false | true | | ||
**Sent notifications** | ||
|
||
### Project settings | ||
When an annotator writes a comment, the users who are notified depend on whether it is the first comment on the annotation: | ||
|
||
You can make it mandatory to write comments when annotators click Skip on annotations. You can find it in Project Settings on the Annotation tab: | ||
<br><img src="/images/comments-notifications/annotator-skip.png" class="gif-border"><br> | ||
* If this is the first comment on an annotation, then all users within a project that have the role of Reviewer or higher see the comment in their [notification list](#Notifications). | ||
* If this comment is in response to an ongoing discussion within the comments panel, then only users who are have added comments to the annotation will see a notification. | ||
|
||
A similar option is available for reviewers. You can find it in Project Settings on the Review tab: | ||
<br> | ||
<img src="/images/comments-notifications/reviewer-reject.png" class="gif-border"> | ||
<br> | ||
**Received notifications** | ||
|
||
An annotator receives a notification any time another user leaves a comment on one of their annotations. | ||
|
||
## Notifications | ||
### Reviewers and other users | ||
|
||
To see the notifications, navigate and click the user profile icon on the top-right of the Label Studio UI. The **Notifications** pane opens with a bell icon next to it. The blue color bell icon indicates unread notifications and the grey color bell icon indicates read notifications. | ||
Reviewers can write comments on annotations that they are reviewing. This applies to users with the Reviewer, Manager, Admin, and Owner role. | ||
|
||
<br> | ||
<img src="/images/comments-notifications/notifications.png" class="gif-border"/><br/> | ||
<i>Figure 9: Notification panel.</i> | ||
**Sent notifications** | ||
|
||
When a reviewer writes a comment, then the users who are notified depend on their role and whether they have also left comments: | ||
|
||
1. Navigate and click the user profile icon on the top-right of the Label Studio UI. | ||
2. The **Notifications** pane opens on the right side of the Label Studio UI. | ||
3. To mark an individual notification as an unread notification, click on the three dots (**...**) >> **Mark as Unread** option. | ||
4. To mark all the notification as a read notification, click on the three dots (**...**) >> **Mark All as Read** option. | ||
* Annotators get a notification for all comments on the annotations they created. | ||
* If other users have also left comments on the annotation (for example, if multiple users are reviewing the annotation), then they will also be notified when a new comment appears. | ||
|
||
!!! note | ||
The read notification has a gray color background which means a user has already read this notification. | ||
**Received notifications** | ||
|
||
A reviewer receives a notification when: | ||
|
||
* If the comment is the first comment on an annotation, then all users within a project that have the role of Reviewer or higher see the comment in their [notification list](#Comment-notifications). | ||
* If you have already left a comment on an annotation, you receive a notification when any user, regardless of role, adds a new comment. |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.