ACLs of a series (of a Moodle course) are not set by using schedule-and-upload workflow

[mwuttke]

I'm not sure whether the error is in the new admin ui, but I'm just going to assume that it's in the right place. When scheduling scheduled lecture recordings using the schedule-and-upload workflow, my colleague and I noticed that the assignment of a series (Moodle course ID) does not work correctly and the access rights for the Moodle course (Learner & Instructor) are not set. This means that at the end of the dialogue for setting up a planned lecture recording, the assignment of the planned recordings to the access rights (ACLs) for the selected Moodle course is simply missing.

To Reproduce
Steps to reproduce the behavior:

1. Create a new Event
2. Select Schedule single event or Schedule multiple events
3. Select workflow Process upon upload and schedule
4. Select Straight to publishing
5. See the error (screen shot)
   

Expected behavior
The workflow should run through without errors, i.e. the ACLs for the series should be set acording to the Moodle course and the ACLs there.

Server environment:

• OS: Debian 12/Bookworm
• Opencast Version: 15.3 (deb packages)
• Separate nodes for adminpresentation & 4 workers
• using Extron SMP

[Arnei]

Thanks for the report. This should be fixed by #300 in the next release, but I have not actually tested if it fixes your particular problem.

This is also likely not a problem with the schedule-and-upload workflow, as the "Zugriffsrichtlinie"-Tab is already not showing the correct roles and the workflow does not start until after you hit "Anlegen" on the last tab.

[mwuttke]

Sorry @Arnei, but I didn't get it. Do you see the difference between the behaviour of the new admin ui and the old one?

Piri gave me the hint to the patch from you. I tried it yesterday by using a new jar file for opencast-admin-ui-interface form the newest branch (admin-ui-picard) built by Piri. The error still occurred.

[Arnei]

Sorry @Arnei, but I didn't get it. Do you see the differenc between the behaviour of the new admin ui and the old one?

What in particular did you not understand?
Yes, I do see the difference in behaviour.

Piri gave me the hint to the #300 from you. I tried it yesterday by using a new jar file for opencast-admin-ui-interface form the newest branch (admin-ui-picard) built by Piri. The error still occurred.

So #300 does not fix your issue, good to know at least.

[mwuttke]

Thanks Arne for your answer.

What in particular did you not understand? Yes, I do see the difference in behaviour.

In the "Zugriffsrichtlinie"-Tab in the old Admin UI the correct roles are shown but not in the new Admin UI. I don't understand why. Therefore my question to you.

[Arnei]

In the "Zugriffsrichtlinie"-Tab in the old Admin UI the correct roles are shown but not in the new Admin UI. I don't understand why. Therefore my question to you.

The new Admin UI should definitely show the correct roles, so that's a bug. As for why that bug occurs I do not know.