As we move towards building an analytics or tracking platform for Matterhorn we run into the issue where we might want to get the list of users who have access to particular lectures but we don't actually care about the content of the lecture itself. Right now we can't do this, since all permissions metadata are stored directly on the resource.
So if I wanted to write a query that, say, returned a list of all of the users who had access to series1 but never watched anything in series1 I can't do that (even if I know who did watch series1). I think harmonizing this metadata (and perhaps more down the line, but that's a digression) into the DB where we can make quick queries is good, and we can propogate to solr for performance tuning only. wdyt? Chris On Mon, 16 Jan 2012 13:19:17 +0100 Rubén Pérez <[email protected]> wrote: > Tobias, > > I think it's pretty much the same approach used (at least it was used > a while ago) with Series. When the system would start, the SOLR index > was dropped and re-created with the info contained in the database. > Should a new series be added, it would be put in the index, but also > in the DB for persisting. The searches are done with the SOLR index, > though, the DB being merely a "backup". > > This is not so detailed, but I believe that is more or less what > Chris is proposing. > > Regards > > 2012/1/16 Tobias Wunden <[email protected]> > > > Hi Chris, > > > > I would love to get some more details on this idea. I have you seen > > going back and forth on it, but never fully understood what that is > > needed. Replication of data is mostly useful for performance tuning > > and most often also a pain… Thank you in advance for taking the > > time to make me understand. Maybe discuss at a developer meeting? > > > > Tobias > > > > On 14.12.2011, at 03:06, Christopher Brooks wrote: > > > > > Any objections to the idea of putting ACLs in the DB using > > > persistence and replicating them to solr on update? So we have > > > some ACL service that wraps a DB and also injects results into > > > solr as appropriate (or at least has a listener model to get the > > > updates towards solr). > > > > > > If its not a problem with anyone, we might look at scheduling > > > this work for 1.4, though we are open to collaboration on it! > > > > > > Chris > > > _______________________________________________ > > > 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] > > _______________________________________________ > > -- Christopher Brooks, BSc, MSc ARIES Laboratory, University of Saskatchewan Web: http://www.cs.usask.ca/~cab938 Phone: 1.306.966.1442 Mail: Advanced Research in Intelligent Educational Systems Laboratory Department of Computer Science University of Saskatchewan 176 Thorvaldson Building 110 Science Place Saskatoon, SK S7N 5C9 _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
