Ok, interesting. But that is then a "bug" (or maybe not fully implemented backend function of steering) in the Django App. It seems that in the Django backend the show is always updated together with the schedules. But through the REST API that is not necessary. I can just update the show object and then edit/add/delete other schedules or vice versa.
Then the question is if that should be a priority. Because through the dashboard it is possible to edit show and schedules separately. And in general we would like to have everything we need to edit being able to edit in the dashboard.
Just get rid of it and don't expect the Django backend to behave in the same way as the API does, when programming schedules.
I stopped the implementation after it was clear that our usecases and requirements of a UI were not realizable through the standard Django backend back then (don't know if it would be possible by now?).
In the end we decided to modularize everything, make a real handy UI (=dashboard) instead of this clunky admin interface, but also consequently use the API instead.
@ingo That would be great if you could clean-up, as @nnrcschmdt is now back diving into PV/Steering :-)
Maybe you also have some helpful hints for Ernesto like what the major changes since his version of PV where?