Build new requirements selection experience #85

New Issue

2026-09-24T16:37:30Z

BobdaFett commented

2026-09-24 16:37:30 +00:00

(Migrated from github.com)

Providers currently have the option to select a series of hard boolean requirements. This means that the students that are returned from the comparisons must have all that information, with no movement room. Instead, we would like to have a both more intuitive and more flexible requirements selection process.

For example, a scholarship last year had a hierarchy of requirements, where students were not actually required to have any specific information. The scholarship had a series of requirements, but did not want to exclude anyone. It basically wanted people that had one or many of these requirements, rather than all of them.

This is likely possible, but requires more thought into what really makes up a requirement and whether this feature is really needed.

Providers currently have the option to select a series of hard boolean requirements. This means that the students that are returned from the comparisons *must* have all that information, with no movement room. Instead, we would like to have a both more intuitive and more flexible requirements selection process. For example, a scholarship last year had a hierarchy of requirements, where students were not actually required to have any specific information. The scholarship had a series of requirements, but did not want to exclude anyone. It basically wanted people that had one or many of these requirements, rather than all of them. This is likely possible, but requires more thought into what really makes up a requirement and whether this feature is really needed.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: r15-software-dev/scholarships-rs#85