Automatically import votes

Description

Should we just import votes automatically? My impression is that people don't walk through all of their votes, they just pull them in.

If that is the case, it is just more error-prone to ask them (see outstanding bug about how this fails), and so we should just import them. It could be that we have some filter, such as:

  • Only import for on first login when submission starts. (Not for completely inactive voters).

  • Downgrade the votes if the user is not truly active (doesn't make XX submissions)

  • Drop votes if a path doesn't exist (known problem now)

  • Drop votes if the committee made changes to the item in resolution.

  • //may be others...//

xpath

None

locale

None

Activity

Show:
TracBot
May 9, 2019, 10:02 PM
Trac Comment 10 by —2019-04-19T16:20:08.524Z

CLDR-dev work scope for v36 are scoped to performance, datasync, and critical/blocking production issues.

TracBot
May 9, 2019, 10:02 PM
Trac Comment 6 by —2018-10-17T15:37:57.932Z

CLDR 34 BRS closing item, move all open 34 → upcoming

TracBot
May 9, 2019, 10:02 PM
Trac Comment 3 by kent.karlsson14@0885cc00c95d6cd9—2018-02-07T18:17:12.864Z

(And by "import" I of course mean both vote import and bulk data import.)

TracBot
May 9, 2019, 10:02 PM
Trac Comment 2 by kent.karlsson14@0885cc00c95d6cd9—2018-02-07T09:16:43.055Z

There should be a rotating (per CLDR version) scheme for having sections where import is not permitted, only manual votes.

That is because import is too often used indiscriminately, to the extent that it even barrs reviews and corrections.

Fixed by Other Ticket

Priority

assess

Assignee

Unassigned

Reporter

Mark Davis

Labels

Fix versions

Phase

dsub