feat: extra settings for ranking question type

[sharko789]

Nextcloud:

• Nextcloud-Version: N/A
• Forms-Version: 5.3.0-alpha.0

Is your feature request related to a problem? Please describe.
I am regularly holding a vote through Nextcloud Forms where users have to rank a subset from a list of options. The results are then weighted using a Borda count. (n points for the first/top choice, 1 point for the last/lowest choice)

Describe the solution you'd like
The new ranking question type is great and almost exactly what I need. The only problem is, that it forces the user to rank all available options. There already exists the extra setting optionsLimitMax for the multiple question type, so could that be implemented for the ranking as well? (and optionsLimitMin should probably be implemented alongside it)
The Borda count code would have to be modified as well to be based on the amount of actually submitted options instead of all available options.

Describe alternatives you've considered
I am currently working around this limitation by using multiple dropdown inputs (one for each choice), exporting the submissions as CSV and pipe them through some python code to sort out potential duplicates and do the actual weighted counting.

Additional context
#1278
#3262
@datapumpernickel would you be willing to work on this or should someone else take a look at it?

[datapumpernickel]

Hi @sharko789,

thanks for the interest! Glad to hear other will also benefit from this question-type! Unfortunately work has been a little crazy, hence I cannot really commit to making these adjustments. I´d be happy to hand-off to whoever is willing to implement this!

We would also have to think through a smart default - what would be the expected behavior if the question is mandatory but no options limit given vs. non-mandatory question, but with a minimum of 3 ranked options, etc.

But definitely understand the use-case and how that would be useful!

[Chartman123]

I had a quick look at Microsoft Forms: they also don't have an option to only rank a few options.

Calculating the Borda count would falsify the result then. If you have 10 elements (e.g. colors) and red is your favorite color, it would get 10 points if you rank all options, but only 3 if you rank only 3 of them. No problem for single submission results, but for the totals.

So I'm against implementing this.

[sharko789]

I see you point @Chartman123. I hadn't considered that because in my scenario all the users would max out the limit and hence have the same amount of options.
So maybe we don't reuse optionsLimitMax/optionsLimitMax and just introduce a single setting that forces the ranking of exactly n options?

[Chartman123]

We could still use the existing ones and set them to the same value in the backend. But what's the problem with ranking all options in the first place? Why do you really need the subset?

[sharko789]

My usecase is basically about choosing what to do. E.g. there is 10 things the group wants to do, but there is only time to do 5, so everyone gets 5 votes.