rank order questions

[dckc]

@leithaus suggests this is straightforward to support and notes there was such a question in last year's ballot (from @steverosstalbot ).

[dckc]

Impact on the tally algorithm #58 is also important here.

[SteveHenley]

Dan suggestions to have REV address that states rank one, then rank two and so on. Using dust is not a good idea.

Jim suggests dust is a good and too many REV addresses is bad.

[9rb]

Design:

1. Use dust for relative ranking (this is especially helpful when we have a large number of options to rank order, so that we do not need a separate REV address for each option - if we choose 1,2,3 type ranking, each option would need a separate REV address).

2. Relative dust can be used ONLY within a particular user to deduce that user's relative ranking - one person may use 1 rev, 2 rev etc. another may use .01 rev, .02 rev etc..Separately, we may need to check to make sure each dust amount given is different, so that one does not rank for e.g. every option as 1 etc.

3. Once individual user's relative ranking is deduced, we need to use the inverse of the rank to use total votes got by each option -- e.g. rank 1 is 1, rank 2 is 1/2, rank 3 is 1/3 etc.

[dckc]

@9rb a handful of test cases would be really handy... perhaps in a spreadsheet or something?

[dckc]

https://www.qualtrics.com/support/survey-platform/survey-module/editing-questions/question-types-guide/standard-content/rank-order/

B and C same ranking? let's not.

[jimscarver]

I suggest we need one rev address for each option and can send the amount of dust corresponding to the rank chosen.

@dckc if you still have the sample json for a rank order question from today's meeting please enter it here.

[dckc]

  "Flavors": {
    "shortDesc": "Office Space",
    "choices": [
      { "label": "buy", "addr": "111..." },
      { "label": "rent", "addr": "111.2.2.2.2" },
      { "label": "no property", "addr": "111.2.2." }
    ],
    "abstainAddr": "111.1.1."
  },

[jimscarver]

work is on the https://github.com/rchain-community/rv2020/tree/rank-order branch led today by @fabcotech and to be led by @TheoXD at thursday workstudy. Coordination will be in the colab https://discord.com/channels/257555930173014017/578571638321446913

• short desc missing - add at top of rank choices
• rank status html not processed
• rank status not updated when rank is changed
• rholang update to include count of revlettes to transfer for each account.
  

[dckc]

good progress.

I suggest using a checkbox for Abstain.

[dckc]

postponed indefinitely in today's meeting