[Feature request]: Allow re-rating of specific events.

[dreirund]

Feature request: Allow to change ratings. Globally, or by search string for event titles.

[top-on]

@dreirund : i am currently using the workflow of exporting a CSV (with dump) and change ratings directly in the CSV and import it again (with load).

is that a workflow that would work for you, too?

[dreirund]

i am currently using the workflow of exporting a CSV (with `dump`) and change ratings directly in the CSV and import it again (with `load`). is that a workflow that would work for you, too?

Yesterday I tried export, modify the score, save, re-import. `optimal congress next` did still show an event that I set to low score of 1. I checked `optimal congress ratings` and that was updated. I did not check further. Anyway, if it worked that workflow could be OK-ish, nut not really convenient if you just made a mistake and want to revert. Anyway, I run into more and more issues that are hard to discuss via github. E.g. Sessions already started but open to drop-in like `Next events: - Wed 27 10:00-17:00 ................Software Defined Radio Capture The Signa..https://events.ccc.de/congress/2023/hub/en/event/software-defined-radio-capture-the-signal-sdr_k2o4´ are not shown. Also, I miss the option to define the "minimum rating" that the `next` command uses. And I use it as the only tool for offline congress information -- `confy` does not have all the small events -- and in the CSV export I miss complete information (time, room, abstract, description, other meta information). Especially missing time is not good. So I actually cannot see a whole-congress overview. It looks in the end the tool actually is not what I thought it was for (and now I am a bit "lost" because I spend all my work into rating via this tool and it does not give out me the information). Regards! (3134)

[top-on]

hi @dreirund , thanks for having alpha-testing this CLI. sad that it's not what you expected, but your testing has been very helpful.

while i started this project with the narrow scope of "just" schedule optimization, your and my own experience tells me that its scope could as well be broadened to a more complete tool for keeping an overview of the entire schedule and favorite events.

in order for rating to require less effort from the user, i have the strong feeling that the rating logic would need be to be re-modeled. i have boiled down my currently favorite idea in the README's roadmap section. basically: instead of exactly rating all events, we could quickly mark our favorites (as in the other schedule apps), or even import them from the halfnarp - and if we want to run an optimization, we would only have a rank conflicting favorites.

this being said, i will develop this CLI much slower, now. i think it can be adapted and improved quite quickly before future chaos events start.