View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004890 | Composr | points | public | 2022-08-16 17:42 | 2022-10-05 00:58 |
| Reporter | Chris Graham | Assigned To | Patrick Schmalstig | ||
| Severity | Feature-request | ||||
| Status | resolved | Resolution | fixed | ||
| Product Version | |||||
| Fixed in Version | |||||
| Summary | 0004890: Show voting power on the leader-board block | ||||
| Description | Add a new block option to show the following on the leader board block: 1) voting power 2) control (percentage control based on voting power relative to total voting power of all members) (2) will be particularly computational intensive (it has to evaluate over all members), however as it is running inside Cron (thanks to 0002737) this should be okay, for now at least. Both '1' and '2' should show actual derivations just like the voter display does on topic polls. | ||||
| Tags | AutonomousOrganisation, Roadmap: v11 | ||||
| Time estimation (hours) | 2 | ||||
| Sponsorship open | |||||
| related to | 0002737 | resolved | Patrick Schmalstig | Composr | Rewrite leader-board functionality |
|
|
We also need an option for the leaderboard to be calculated for points currently held, rather than lifetime points. |
|
|
In terms of computational requirements, this should not be much of an issue. As points are already calculated via the leader-board and stored in the database, there is a simple arithmetic API that takes the number of points as a parameter and turns it into a voting power. The bulk of the load will come from querying for those points for every member. For consistency, since points are stored, we should probably also calculate voting power and control upon generation of the leader-board and store alongside points in the database. That way, these values reflect voting power as they were at the time of leader-board generation and do not fluctuate when the voting power calculation settings are changed. Furthermore, while this will slightly increase load for leader-board generation, it will offset by not requiring any additional load when viewing leader-boards (since these values were already computed). I will further enhance the efficiency by only calculating voting power once we have determined who will be on that leader-board, and only for the members who made it to the leader-board. (EDIT: can't do that; we need to know the voting power of every member to calculate voting control) |
|
|
agreed |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-08-16 17:42 | Chris Graham | New Issue | |
| 2022-08-16 17:42 | Chris Graham | Status | non-assigned => assigned |
| 2022-08-16 17:42 | Chris Graham | Assigned To | => Patrick Schmalstig |
| 2022-08-16 17:42 | Chris Graham | Tag Attached: AutonomousOrganisation | |
| 2022-08-16 17:42 | Chris Graham | Tag Attached: Roadmap: v11 | |
| 2022-08-16 17:43 | Chris Graham | Relationship added | related to 0002737 |
| 2022-08-16 18:05 | Chris Graham | Description Updated | View Revisions |
| 2022-08-17 00:51 | Chris Graham | Note Added: 0007464 | |
| 2022-10-04 17:32 | Patrick Schmalstig | Note Added: 0007538 | |
| 2022-10-04 17:34 | Patrick Schmalstig | Note Edited: 0007538 | View Revisions |
| 2022-10-04 17:39 | Patrick Schmalstig | Note Edited: 0007538 | View Revisions |
| 2022-10-04 17:49 | Chris Graham | Note Added: 0007539 | |
| 2022-10-05 00:58 | Patrick Schmalstig | Status | assigned => resolved |
| 2022-10-05 00:58 | Patrick Schmalstig | Resolution | open => fixed |
