Adobe ConnectContent Management and Web
Every Recorded Session, Searchable Long After It Ends
Nothing is prebuilt for Adobe Connect, and what would be built is narrower than the name suggests. Adobe Connect runs the live room, and this is not about the live room but about what it leaves behind, the recorded class or webinar nobody can find three months later. The path that would be built is the generic one, an embed code and a JavaScript widget placed on the page learners already use, with scope agreed per engagement. Nexus, the portal behind the Enterprise Video Platform (EnterpriseTube) solution, would hold the recordings under one access and retention policy.
What you can do together
Find a session by its subject
Recordings held in Nexus would be reachable through the library and search widgets, so a learner looks for the topic rather than the date.
Put the recording where learners already are
The player widget would sit on the course page or the training intranet, with the transcription widget beside it, instead of sending people to another address.
Hold every session under one policy
Access rules, retention and the audit of who watched would be set in Nexus rather than left in the meeting tool's storage.
Ask a question afterwards
The quiz and survey player widgets would sit below the recording on the same page, so a check on understanding follows the session.
See what gets watched
Nexus embed analytics would name the sites that embedded a session, the view count for each and the last playback.
How it connects
Start with what would not happen. Nothing would reach into Adobe Connect to collect recordings. A session recording would leave Adobe Connect the way it does today and be added to the library like any other file, by the person who owns the training program. Adobe Connect would go on hosting and recording sessions with nothing changed about the room.
From the library outward, the connection the catalog names is the JavaScript widget. A player would be placed on the course page or the training intranet, and the documented widgets go further than playback: audio, image, document, collection and playlist players, media library gallery and detail views, insights, transcription, maps, carousel and collage, quiz and survey players and a mashup filter. A single page could therefore hold a searchable set of past sessions, the transcript beside the player, and a question at the end. No module would be installed on either side. This is the same path the shipped WordPress and SharePoint integrations run on.
Configuration would live in Nexus. Embedding is restricted to approved domains, so the learning site would be named and every other host refused, and content URLs are signed and expire. Each embed would resolve against the viewer's identity, so a session limited to one cohort in Nexus would stay limited on any page that carries it.
Adobe ConnectContent Management and Web
A scenario
- ScopingThe engagement would settle which pages carry the widgets, which domains may embed, and how cohorts map to access rules in Nexus.
- Tuesday, 10:00The instructor would run the class in Adobe Connect and record it, exactly as now.
- Tuesday afternoonThe program coordinator would add the recording to the Nexus library, file it with earlier sessions, set the cohort that may view it, and apply the district's retention rule.
- WednesdayThe coordinator would place the player, transcription and search widgets on the staff development page of the district site, which is on the approved domain list.
- Two weeks laterAn adjunct who missed the class would search that page for the topic, open the session, and read the transcript alongside it. What she can open is decided by her permissions in Nexus, not by the page.
- End of termEmbed analytics would show which sessions were watched, on which site, and when each was last played.
What stays where
Adobe Connect would keep the live room
Hosting, running and recording a session stay there, and nothing about the class changes.
Nexus would hold the recording once it exists
Access rules, retention, search and analytics live in the library, and a page would read from it through the widget.
Nothing would be replaced, and nothing would be collected automatically
The recording would be added by a person, and the standard widgets and embed codes would be the whole connection.
Processing would run where you choose
Nexus is offered as shared SaaS, a dedicated instance, in your own cloud or on your own servers.
Products and solutions
Next step
See it on your own Adobe Connect instance.
We will show the connection made, the data moving and the output, then size it for your deployment.
Contact VIDIZMO
sales@vidizmo.ai
+1 571-969-2180
vidizmo.ai