Enable episode ID roles by default

[dennis531]

While integrating the function ‘Episode ID roles’ into the OC-Stud.IP plugin, we noticed that the related config is disabled by default and that this cannot be queried by other tools such as the OC-Stud.IP plugin.

We would like to see this config enabled by default in order to reduce errors when configuring OC servers and to ease the migration to these roles.

[gregorydlogan]

@JulianKniephoff Since you guys are (presumably) getting paid to add the feature, do you want to quickly add this to the org config blob somewhere?

[JulianKniephoff]

We can expose it there, but most/all of the stuff in there is from the organization config, and this is not. We could add it somewhere else in /info/me.json of course.

What bugs me is that this is kind of ad-hoc. Wouldn't it be gerat if we could generally query Opencast for (some of) its settings? 🤔 Static File Authorization is another one that external applications could use for example (to determine whether or not they will work lol) or is that exposed somewhere already? 🤔

[gregorydlogan]

I would absolutely love to be able to query for some settings. Feel free to implement that :D

[JulianKniephoff]

Maybe something for a mini Rüdiger-money project? 🤔 What does @lkiesow think? Anyway, this is getting OT. 🫥

[LukasKalbertodt]

I don't think Tobira is particularly interested in whether it's enabled or not, simply because there is no workaround if it's disabled. Some features will simply not work then. So the only reason Tobira might want to know about this is to print a nice warning. But this doesn't warrant adding a new API for.

So from my view, we can just go ahead and enable it by default, preferably for OC18.

[lkiesow]

On topic, I think it's a good idea to enable it by default. Note that this technically needs an index rebuild. But you can ignore it if you don't need that feature.

Off-topic, there are a lot of settings you wouldn't want to expose, plus exposing service settings may not always be that easy. Also, as a tool/integration, you can also just require something to be enabled. For example, I don't think the Stud.IP plugin working around the setting by taking over and updating all ACLs in Opencast is great. It's doing the same thing the setting in Opencast does, just way less effective. It's basically just a bad work-around. Simplify the plugin and make it a requirement is what I would argue for.

This brings me back to exposing settings. It may still make sense occasionally, but I think that's a more special case and I would treat it as such. Exposing everything and handling every setting is a lot of work for very little gain.