Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Super low priority, for version 2 - Instead of editing manually the results, come up with a solution that will allow the user to go back and make more pairwise assessments #185

Open
GriffGreen opened this issue Nov 9, 2023 · 1 comment
Labels
question Further information is requested

Comments

@GriffGreen
Copy link
Member

Editing manually right now makes it so the user can't go back and play our fun game.

This is a tragedy.

We need to make their manual edits happen in another way... there are dozens of solutions, but the most obvious would be to allow the user to Boost or Slash a project and just letting them add some OP to that project, then that boost/slash could stay there on the side and the pairwise "score" could also stay on the other side and if a user wants to do more assessments, they are adjusting the pairwise score, but the boost/slash remains.

In every solution there are a lot of details to work out... (like where does the boost come from?) but the end goal is clear.... people should be able to continue playing the pairwise game!

@kristoferlund
Copy link
Collaborator

kristoferlund commented Nov 13, 2023

I guess we in theory could allow them to continue doing the pairwise thing even after edit, as long as the ranking algorithm can handle it and we can communicate it to the user. The result has to be somewhat predictable.

@GriffGreen, do you have an idea on how this plays out?

After pairwise voting:

proj 1: 100
proj 2: 100
proj 3: 100

After manual adjustment:

proj 1: 200
proj 2: 50
proj 3: 50

Going back to pairwise voting:

Choose proj 2 over proj 1

What is the end result?

proj 1: ?
proj 2: ?
proj 3: ?

@kristoferlund kristoferlund added the question Further information is requested label Nov 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants