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

CLDR Ticket #11150(closed: fixed)

Opened 6 months ago

Last modified 6 weeks ago

Transfer old votes for all versions

Reported by: tbishop Owned by: tbishop
Component: survey-backend Data Locale:
Phase: dsub Review: fredrik
Weeks: Data Xpath:



There is a tool for transferring old votes from one user to another:


Each user has a button "Transfer Old Votes". Currently it only works on the most recent old version. It should be extended to work on all the available old vote tables, going back to version 25.


Change History

comment:1 Changed 6 months ago by tbishop

The transfer tool currently only operates on the last vote table, currently v33. That is, rows in the table CLDR_VOTE_VALUE_33, representing old votes for one user, are copied to new rows in the same table, representing old votes for a different user. No change is made to the new vote table (CLDR_VOTE_VALUE_34), and the votes for the first user are not removed.

The plan is to do the same thing for each version from 25 up to 33 (the last vote table) independently. That is:

  • rows in the table CLDR_VOTE_VALUE_25 are copied to new rows in CLDR_VOTE_VALUE_25
  • rows in the table CLDR_VOTE_VALUE_26 are copied to new rows in CLDR_VOTE_VALUE_26
  • rows in the table CLDR_VOTE_VALUE_27 are copied to new rows in CLDR_VOTE_VALUE_27
  • rows in the table CLDR_VOTE_VALUE_28 are copied to new rows in CLDR_VOTE_VALUE_28
  • rows in the table CLDR_VOTE_VALUE_29 are copied to new rows in CLDR_VOTE_VALUE_29
  • rows in the table CLDR_VOTE_VALUE_30 are copied to new rows in CLDR_VOTE_VALUE_30
  • rows in the table CLDR_VOTE_VALUE_31 are copied to new rows in CLDR_VOTE_VALUE_31
  • rows in the table CLDR_VOTE_VALUE_32 are copied to new rows in CLDR_VOTE_VALUE_32
  • rows in the table CLDR_VOTE_VALUE_33 are copied to new rows in CLDR_VOTE_VALUE_33

Actually some of those tables are absent or empty and will effectively be skipped.

comment:2 Changed 6 months ago by tbishop

Reference email discussion on cldr-dev list, subject "[cldr-dev] transferring old votes?".

comment:3 Changed 5 months ago by kristi

  • Priority changed from major to critical
  • Milestone changed from UNSCH to 34

comment:4 Changed 5 months ago by tbishop

I've committed the changes to trunk in changeset [14249].

comment:5 Changed 5 months ago by tbishop

Testing on smoketest. Sample output for View Old Vote Stats:

Apple #1023
old votes: {v30:[[5171,en_GB,English (United Kingdom)]],v32:[[7514,en_GB,English (United Kingdom)]],v33:[[6767,en_GB,English (United Kingdom)]],v25:[[3873,en_GB,English (United Kingdom)]],v26:[[4380,en_GB,English (United Kingdom)]],v28:[[4688,en_GB,English (United Kingdom)]]}

Transfer Old Votes:

Import FROM English (United Kingdom) @ u_1023@apple.example.com TO English (United Kingdom) @ mauiclinguist.lzwakh2qg@ougl.apple.example.com


MauiCLinguist_TESTER_Apple #2031
{"tables":"cldr_vote_value_33, cldr_vote_value_32, cldr_vote_value_30, cldr_vote_value_28, cldr_vote_value_26, cldr_vote_value_25","to_locale":"en_GB","to_user_id":2031,"from_locale":"en_GB","result_count":32393,"from_user_id":1023}

Looks OK! "result_count":32393 means that 32,393 votes were transferred.

Then View Old Vote Stats for the new user:

old votes: {v30:[[5171,en_GB,English (United Kingdom)]],v32:[[7514,en_GB,English (United Kingdom)]],v33:[[6767,en_GB,English (United Kingdom)],[4720,fi,Finnish]],v25:[[3873,en_GB,English (United Kingdom)]],v26:[[4380,en_GB,English (United Kingdom)]],v28:[[4688,en_GB,English (United Kingdom)]]}

Last edited 5 months ago by tbishop (previous) (diff)

comment:6 Changed 5 months ago by tbishop

  • Status changed from new to reviewing
  • Review set to fredrik

comment:7 Changed 5 months ago by fredrik

Looks good on smoketest. Let's push to production.

comment:8 Changed 5 months ago by kent.karlsson14@…

When voting for "old loosing votes", one is presented with several old values for each item.

1) It does not say for which version each of the values are picked from.
2) It does not seem to vote for the value selected, but may pick another version's value for that item.
3) It is not clear that the values presented are only for loosing votes.
4) Current winning value for Emojis are not given (though given for all other kinds of values).
5) When going through the (rather long) list, login timeout is too likely.

In addition, there seems to be no way not to import winning votes *every time* ST is started. Just once (as before) would be better.

comment:9 Changed 6 weeks ago by fredrik

  • Status changed from reviewing to closed
  • Resolution set to fixed

Basically it works, but has flaws that Kent pointed out. We should probably move back to a more manual process like in the past. Will create new ticket for that.

comment:10 Changed 6 weeks ago by fredrik

  • Xref set to 11468

Add a comment

Modify Ticket

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

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

Note: See TracTickets for help on using tickets.