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

CLDR Ticket #4629(closed defect: duplicate)

Opened 6 years ago

Last modified 6 years ago

"What do I need to do" view in ST

Reported by: mark Owned by: mark
Component: design Data Locale:
Phase: Review:
Weeks: 1 Data Xpath:
Xref:

Description

For the Vetting phase, what we need is a view such that:

a) translators can walk through at all and only the items that need vetting.
b) translators can see a summary so that they can verify that they are done.
c) admins can see a summary so that they can verify when all the translators are done.

Items needing vetting are:

  1. Errors
  2. Losing items (my org is losing)
  3. Unsync'ed (where English changed, but native didn't)
  4. Warnings (without votes*)
  5. Disputed items (we didn't vote, and item is contested by others)
  • For some class of warnings, we'd like to be able to suppress the warning once it has been "confirmed" as being ok, so that translators can focus on _new_ warnings.

We've been doing this with the Vetting Viewer. We can either get that to work again, or have a separate View control that filters on each page. We need a summary page so that admins can verify when all of the above are done for each of the locales we care about.

Next Release: Data Submission Phase

For us to be able to use the ST for data submission (next cycle), we need to have a view so that:

a) translators can walk through at all and only the items that need data submission.
b) translators can see a summary so that they can verify that they are done.
c) admins can see a summary so that they can verify when all the translators are done.

Items that need data submission:

  1. Errors
  2. Missing items (at our coverage level)
  3. Unsync'ed (where English changed, but native didn't)
  4. Warnings (without votes)

Attachments

Change History

comment:1 Changed 6 years ago by emmons

  • Owner changed from anybody to mark
  • Priority changed from assess to medium
  • Status changed from new to assigned
  • Component changed from unknown to design
  • Milestone changed from UNSCH to 22

comment:2 Changed 6 years ago by emmons

  • Cc srl added

comment:3 Changed 6 years ago by emmons

  • Priority changed from medium to critical

comment:4 Changed 6 years ago by mark

  • Weeks set to 1

comment:5 Changed 6 years ago by mark

  • Status changed from assigned to closed
  • Resolution set to duplicate
View

Add a comment

Modify Ticket

Action
as closed
Next status will be 'new'
Next status will be 'closed'
Author


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

 
Note: See TracTickets for help on using tickets.