[Unicode]   Common Locale Data Repository : Bug Tracking Home | Site Map | Search
 
Modify

CLDR Ticket #10973(accepted tools)

Opened 7 weeks ago

Last modified 5 weeks ago

Emoji keywords disputes due to additional keywords

Reported by: kristi Owned by: mark
Component: annotations Data Locale:
Phase: dsub Review:
Weeks: Data Xpath:
Xref:

ticket:10980

Description

We have a large number of disputes for emoji keywords
Here's a scenario:

  1. Most of the existing data is in Approved state
  2. Vetter A is the first to come and vote by adding one new keyword. This become a suggestion
  3. Vetter B likes A's suggestion, but also want to add a new keyword. This becomes yet another suggestion
  4. Until Vetter A goes back to vote again for Vetter B's suggestion, the Approved data does not change.

Problem:
This causes one of the vetters to redo their voting work all over again.
This causes increased number of disputes for Emoji keywords.

Attachments

Change History

comment:1 Changed 6 weeks ago by fredrik

  • Xref set to 10980

Long-term "blue sky" idea filed as bug:10980

comment:2 Changed 5 weeks ago by mark

While talking to Kirill and Chiara, I had a thought.
We could change the VoteResolver — without modifying the UI — to just modify the way it treats "sets" like annotations.
Treat a vote of 4 for {A, B, C} to be a vote for each of the components. So if we had

{A, B, C, F} 8 votes
{A, B, E} 6 votes
{A, E} 4 votes

We would treat in VR as votes:

A18
B12
C 8
E10
F 8

We accept anything with > 1/2 the top vote count as the top, so we would end up with:

{A, B, E}

(We can play with the proportions/rule. This is just blue-skying.)

Note that what we end up with might not be a input option. Ideally, we'd just introduce a new one. But in the meantime maybe we can take the largest subset, and failing that the smallest superset, or something like that.

Last edited 5 weeks ago by mark (previous) (diff)

comment:3 Changed 5 weeks ago by mark

  • Status changed from new to accepted
  • Component changed from unknown to annotations
  • Priority changed from assess to critical
  • Milestone changed from UNSCH to 34
  • Owner changed from anybody to mark
  • Type changed from unknown to tools
View

Add a comment

Modify Ticket

Action
as accepted
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.