Can I update and interact with another document and its template variables?

As usual, I’m not sure how to explain this, but here goes...

I work for a university with a fairly popular YouTube channel (1,000 subscribers, 200+ videos). I’ve been asked to create a catalog of these videos (in MODx). This part is easy -- I’m thinking each video will just be a resource in MODx and will contain basic video info like YouTube ID#, YouTube playlist ID#, title, description, etc. Basic cataloging stuff. Here’s where it gets complex: the real purpose of this site will be to function as a video "jukebox," and any given video can be tied to any number of different projects, and each project can have its own video "player" that could be embedded in other sites as a widget.

For example, we may interview a student and log his video. Then, there will be a place in MODx where an editor can create a resource containing information on the student, such as his name, demographic information, year in school, etc. When entering this information, I’d like to be able to connect this person’s info with any video that’s been entered. The important part is that the video and the student have to be kept separate, since we may want to connect the same video to a completely separate project down the road.

What I’ve figured out so far is to create a drop-down TV on the user’s page with a @SELECT binding pointing to the folder of videos. This works great (thank you, bindings!), and if the video editors have to edit two different resources to make that connection, so be it. However, ideally, I don’t just want a connection through the drop-down: I want the editor to select a video and have all of its data appear in TVs on the user info page, and have it be editable on that page. That way, they can add/edit/delete video information (or switch to a different video) all in one place, even though the videos are technically being stored somewhere else. Sort of a one-to-many issue, MODx style.

Can this be done? I’m thinking that with some clever ManagerManager use and possibly some @SELECT bindings in the appropriate default fields, this could work. Any suggestions, or has anyone done something similar?

Thanks!