SQL group loaders currently support a single like string value. That means it can't support multiple options, and can't use regular expressions in databases that support it. In some cases, it means organizing basis groups in ways that aren't natural, if multiple loaders put things in a common folder.

If we don't want a new field for like string type, maybe add a special tag that wouldn't be in a normal like string? Or maybe json? Some possibilities:

regexpLike:base:sis:course:(2024|2025):.*
json:'OR':[

{'like': 'base:sis:course:2024:%:instructor'}

,

{'like': 'base:sis:course:2025:%}

']
list:base:sis:course:%, regexpNotLike:base:sis:course:(201\d):.*:instructor$