Hi Greg, It seems to me like creating your own service (inkluding your very own rest api) would make sense instead of trying to make your data fit into search. Generally speaking: The fact that some piece of data is shown in engage doesn't necessarily imply that it needs to live in search.
Are you intending to allow users to create individual clip shows? If so, you might even consider storing these clips in its own datastructure, as the mediapackage doesn't provide per-user-storage. Does that make sense? Tobias On 23.09.2011, at 00:23, "Greg Logan" <[email protected]> wrote: > Hi folks, > > I'm adding a set of plugins to the engage UI which allow the viewer to > create 'clipshows' of the presentation and then share those clips with > others. An example use case is studying (boiling down a lecture from an > hour to minutes). To do this I need a way to store these clipshows on > the core, and this is proving to be somewhat difficult. I intended to > add the relevant services into the Search service, but those services do > not have a Workspace pointer which makes it very difficult to add files > to the mediapackage! > > I'm assuming we want to continue to keep the separation between Engage > and Workspace (and processing in general), so I don't quite see a clean > way of doing this. Does anyone (Tobias? Josh?) have any suggestions here? > > Thanks, > G > > _______________________________________________ > Matterhorn mailing list > [email protected] > http://lists.opencastproject.org/mailman/listinfo/matterhorn > > > To unsubscribe please email > [email protected] > _______________________________________________ _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
