Allow me to chime in. As announced earlier [1], Entwine is working on a service for structured annotations for ETH Zurich and other Swiss universities. Together with earlier (and current?) work from Osnabruck, Greg's thesis work and Carlos' latest announcement, this makes it an issue we should probably coordinate more formally to avoid overlaps and problems. How about a meeting next week, Wednesday, November 14th (same time as developers' meeting)?
O [1] http://opencast.3480289.n2.nabble.com/Opencast-Question-re-quot-Learning-Analytics-amp-Matterhorn-quot-td7284391.html#a7292690 >-----Ursprüngliche Nachricht----- >Von: [email protected] [mailto:matterhorn-users- >[email protected]] Im Auftrag von Carlos Turro Ribalta >Gesendet: Donnerstag, 8. November 2012 09:40 >An: Matterhorn Users >Betreff: Re: [Matterhorn-users] About the Annotation Service > >Thanks Greg, I'm going to look at your code > >Carlos > >-----Mensaje original----- >De: [email protected] [mailto:matterhorn-users- >[email protected]] En nombre de Greg Logan Enviado el: miércoles, >07 de noviembre de 2012 23:45 >Para: [email protected] >Asunto: Re: [Matterhorn-users] About the Annotation Service > >On 12-11-07 12:30 PM, Carlos Turro Ribalta wrote: >> Hello all, >> >> As most of you know, UP Valencia has developed the HTML5 Paella Player for >Opencast Matterhorn [1]. We have just finished up with the bulk of having >everything >OK for this semester recordings and we are going to put some effort in adding >features to Paella. >> >> Our users have asked us to put the annotation service in Paella. Our idea is >> just >adding the controls to create and read annotations from the Matterhorn 1.4 >Service. >I think that some of you are working on that feature for the Engage Player, >and I >don't want to break anything, so I am writing this mail to see if there is >anything I >have to know before going on. >> >> One issue that I have found is that there are two very different use cases >> for >annotations, public annotations in which students create annotations, the >teacher >can validate/delete it and everybody can see all annotations from all students >and >teachers, and private annotations, in which a user can only see his >annotations. As >far as I know today only private annotations are supported, so we should write >some code for public annotations or maybe it should be better to have two >different >services, to have both features. > >I believe it's actually the opposite. While the annotation components are >mainly the >work of the team from Osnabruck, my thesis project needed private annotation >features so that students could choose to make an annotation visible only to >themselves. The annotation service currently has them all public by default, >so I >added that as part of my project. >I haven't quite sent that code back to Osnabruck yet for inclusion in their >work, but >it's on my todo list :) > >My thesis project is up in the MH-8060 branch on the Matterhorn SVN server if >you >want to take a look and see how I implemented the private annotation code. > >G > >> Comments will be very welcomed >> >> >> Carlos Turro >> >> Head of Media Services >> Universitat Politècnica de Valencia >> >> [1] http://paellaengage.webs.upv.es >> _______________________________________________ >> Matterhorn-users mailing list >> [email protected] >> http://lists.opencastproject.org/mailman/listinfo/matterhorn-users >> > > >_______________________________________________ >Matterhorn-users mailing list >[email protected] >http://lists.opencastproject.org/mailman/listinfo/matterhorn-users _______________________________________________ Matterhorn-users mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
