Video the Institution Hosts, Inside the Moodle It Runs
Moodle is downloaded, not bought. The institution's own team installs it, patches it, and reshapes it with plugins and a theme until it matches how that institution teaches, which is much of why it carries so much of further education and of teaching outside North America. Nexus joins on the same terms, as the portal behind the Enterprise Video Platform (EnterpriseTube) solution. It connects over two open standards, LTI 1.3 and SCORM, and it can run on the institution's own servers next to Moodle.
How it connects
Registration comes first, and Moodle starts it. It registers itself through the LTI 1.3 dynamic registration flow, validated by a one-time token against an allowlist of domains, so the administrator who runs the Moodle server owns the connection. Roles map at the same time, which is what makes an instructor arrive in Nexus as an instructor. Setup is documented for Moodle specifically.
After that the traffic runs into the course. An instructor building a unit browses the Nexus library from inside Moodle through deep linking, and the item she selects returns to the course as a launchable link. A learner who opens it stays in Moodle while the video streams from Nexus, and the viewing accrues where the recording lives. A quiz on that recording reports its score to the Moodle gradebook automatically on submission, with manual grading where an answer needs a human read, which depends on Moodle exposing the LTI Assignment and Grade Service.
SCORM runs the other way. Content is packaged out of Nexus as SCORM 1.2 or 2004 and imported into Moodle, which then owns the item and tracks it, reporting interaction-level results including time spent. The online package form streams from Nexus and keeps portal analytics, while the offline form is self-contained and carries none. Nexus also imports packages an institution already owns, reporting participants and attempts, average score, attempts and questions overviews, and time spent.
What you can do together
Build the course without leaving Moodle
Deep linking puts the Nexus library inside the course an instructor is building, so she picks a recording and it lands in the unit as a launchable item.
Let the gradebook do the grading
A quiz placed at a point in the video returns its score to the Moodle gradebook on submission, so completion is evidenced where the institution already looks for it.
Hand Moodle a package it owns
Content exports as SCORM 1.2 or 2004 where Moodle has to track completion itself, and packages already licensed import the other way. The online form keeps Nexus analytics, the offline form stands alone.
Keep all of it on your own hardware
Nexus runs on the institution's own servers beside a self-hosted Moodle, so recordings stay on the network the same team already administers.
A scenario
- Registration dayThe college's Moodle administrator registers Nexus through the dynamic registration flow with a one-time token.
- Course build, TuesdayA welding instructor assembles this year's unit. From inside Moodle he browses the Nexus library, picks four recorded workshop demonstrations, and each returns into the unit as a link.
- First week of termAn apprentice opens the unit and the demonstration plays inside Moodle, streaming from the server in the college's own building. He answers the safety check embedded in it, and the score posts to the Moodle gradebook on submission.
- Compliance weekThe awarding body wants proof that every apprentice completed manual handling. That course leaves Nexus as a SCORM 2004 package in its online form and is imported into Moodle, which records attempts and time spent while views still count in Nexus.
- Year endThe training manager reads completion in Moodle and watch-through in Nexus, then applies the college's retention rule once, where it reaches every unit linking to those recordings.
What stays where
Moodle stays the institution's own
Enrollment, course structure, plugins, theme and the upgrade schedule are run by the team that has always run them. Connecting a video library asks one registration of them.
Nexus keeps the recordings
Storage, access rules, retention and viewing analytics live in the library. Over LTI the course reads from it, and over SCORM it hands Moodle a package to own.
The standards are the whole connection
LTI 1.3 and SCORM are open standards, with setup documented for Moodle, so neither system depends on the other's release cycle.
Processing runs where you put it
Nexus is offered as shared SaaS, a dedicated instance, in your own cloud or on your own servers, where a self-hosting institution usually puts it.
Products and solutions
Next step
See it on your own Moodle instance. We will show the connection made, the data moving and the output, then size it for your deployment.
Request a demonstration or write to sales@vidizmo.ai
sales@vidizmo.ai · vidizmo.ai/integrations/catalog/moodle