Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve Slur Annotation Experience #424

Closed
aatmanvaidya opened this issue Oct 18, 2023 · 2 comments
Closed

Improve Slur Annotation Experience #424

aatmanvaidya opened this issue Oct 18, 2023 · 2 comments

Comments

@aatmanvaidya
Copy link
Collaborator

aatmanvaidya commented Oct 18, 2023

Is your feature request related to a problem? Please describe.

In the latest release of Uli v0.1.14 - https://github.com/tattle-made/Uli/releases/tag/v0.1.14

In the crowdsource feature users can now crowdsource slur's and its relevant metadata using Uli. A user can select and right-click on a word to crowdsource it.

The metadata helps in providing better context to slur words. Metadata that can be crowd sourced for a slur is:

  1. Level of Severity
  2. Casual
  3. Appropriated
  4. If Appropriated, is it by community or others?
  5. What makes it problematic?
  6. Category of Abuse

More details about the feature can be found in this issue - #389

We want to now improve the annotation experience of the annotators by helping the better understand what each metadata field means and stands for

Screen Shot 2023-10-18 at 12 45 24 PM

While we have a detailed annotation guideline that explains what all the fields mean, we should also make it very simple for a new user to access these guidelines, as they are annotating.

The scope of this issue is to make the annotation guideline easy to understand and available within the extension itself.

Describe the solution you would like

written above

Describe alternatives you've considered

No response

Additional Context

No response

Copy link

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Dec 30, 2023
Copy link

This issue was closed because it has been inactive for 14 days since being marked as stale.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant