Skip to content

Enhancement: Add a scheduling score #4

Description

@walrii

I was thinking about not wanting to go to the highest scoring location every week, yet now wanting to have to login and change my scores all the time to avoid it. Also, I'd like to occasionally visit even the less popular places.

I suggest having two scores:

  1. A popularity score which is a combination of ratings, location, and perhaps more.
  2. A scheduling score which is used for finding the next place(s) for lunch. This score would use the popularity score, but also weigh in how recently it'd been scheduled. Negatively if it had been selected and positively if it had been a long time. Something like (indexed by weeks since scheduled). -20, -20, -20, -20, -10, -5, -3, -1, 0, 1, 2, 3, 4, 5, 6, 7, .... There may need to be a threshold--if the popularity is below X, the scheduling add-on will never be cause it to be scheduled.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions