Using opencast-studio with the Esup-Pod plateform

[ptitloup]

Hello all,

We are a french university association who use Esup-Pod video plateform to manage video.

We discover your project and we would to use it with our platform. We would like to use it with no or less modification as possible. After reading documentation and some source code, we have some question :

• we saw the /ingest/* is required, can you give us some example of information returned ?
• Same question for /info/me.json, what kind of information is returned ?
• Finally, LTI is used to get user information, can you give us more information ?

Don't hesitate to ask us if you want more information

Thanks a lot for yours answers !

Regards

Nicolas

[lkiesow]

Hi Nicolas, since it integrates with Opencast, its API documentation should hopefully answer most questions you have about these APIs: https://develop.opencast.org/rest_docs.html

If you log-in before on https://develop.opencast.org, you can also try and see the results of most APIs.

[ptitloup]

Hello, Thanks a lot for your answer ! unfortunately yours links are broken :'( (502 bad gateway)

[ptitloup]

Is-it the same information that https://stable.opencast.org/rest_docs.html ?

[lkiesow]

Sorry, bad luck. Yes, it is. …and I guess I have to investigate why the test server broke

[lkiesow]

It was my own fault that the server was broken. Sorry about that. The links should now work. But the API Studio uses should be identical to the one on stable.

[ptitloup]

At this time, we have two choice: change our platform to copy the API rest of Opencast OR purpose some changes to the studio. For example, we need only the user logged in and the smil with video files and data associated to. Is-it possible to add some parameters to change the default behaviour of the studio to escape some API request ? For example, we don't need some dublin core request and other things like that (or perhaps we miss something)

[ptitloup]

In our platform, we use SSO CAS authentication to log in user. We wan't to allow only logged user to access to the studio. Is-it possible ? Then, we would like to hide the header (with logo and menu), is-it already possible or should we purpose a new parameter ? Thanks and regards

[LukasKalbertodt]

Hi there!

If I understand you correctly, your video management system is not Opencast-based at all, right? In that case I would certainly recommend you to fork Opencast Studio and change the networking code to use your own APIs. Emulating Opencast APIs in your system is not a good idea in my opinion.

Is-it possible to add some parameters to change the default behaviour of the studio to escape some API request ?

Opencast Studio (this repository) will not support multiple different APIs for uploading the video. We assume a fully functioning Opencast server. So managing your own copy (fork) of Opencast Studio seems like the best solution.

Then, we would like to hide the header (with logo and menu), is-it already possible or should we purpose a new parameter ?

No, it's not possible. Another reason to create your own fork IMO.

[ptitloup]

Hello, indeed, our video platform is completly different to opencast but not against, additional ! We forked your repo to study it. We don't want to change your flow but complete it. We also plan to change/improve our API to work with the Studio. Our video platform is used by more than 40 university in France. We just purposed a PR for the header, please consider it because it's not only for our platform but if you want to use studio inside another web site, add a parameter to hide the header could be usefull. Thanks a lot Regards

[LukasKalbertodt]

As you see in the PR, we unfortunately had to reject it.

In general, we want our repository to be focused on Opencast. Sure, through configuration, one could make it work with other video management solutions, but this would drastically increase maintenance cost for us. And since there hasn't been much development activity in Studio for over a year now, maintaining a fork is likely very easy.

In any case, I will close this issue now as there is nothing Opencast Studio will do to work with other platforms. I'm sure this is not the answer you were hoping for, and I'm sorry about that. I wish you the best of luck changing Studio to your liking and integrating it into your own platform. Of course, if you have any questions about Studio, feel free to always ask me!

[ptitloup]

Ok, thanks for your feedback