[Building Sakai] Capturing real time data

[Alan Berg]

Hi fellow hard workers,

The University of Amsterdam Central Computer Services are working with
Unicon (Aaron) to bake in Tincan api support to Sakai CLE. We see that as a
key enabler for production ready Learning Analytic projects, especially
when an LA dashboard works with BasicLTI across a range of delivery
platforms.

Having an external Learning Record Store allows us to potentially track
outside an LMS specific implementation. Loose coupling is always good for
migrations etc. We live in a dynamically changing Universe. Keeping the LRS
separate and specialised simplifies.

You can review progress at:
https://jira.sakaiproject.org/browse/KNL-1042<https://webmail.uva.nl/owa/14.2.342.3/scripts/premium/redir.aspx?C=IoAnIoM-qEKFDZHJXXROemsDrEgkFdAI6VlnVlVxtnlTDa6abOARua-7y-EJsytSZB5mbMYRt28.&URL=https%3a%2f%2fjira.sakaiproject.org%2fbrowse%2fKNL-1042>

The work should be available by the conference. There is more that can be
done, so we are definitely interested in combining efforts/resources if any
one else wants to push in the same direction.

Aaron and I will present our experiences at the Apereo conference.

Further, as a Proof of Concept partially subsidised by SURF, UvA built a
BasicLTI LA dashboard backing off to the database of PIWIK (an opensource
Google Analytics variant). We tested against BlackBoard for enhanced
tracking, but the methodology works for Sakai as well. The tracking work is
superseded by the TinCan API efforts. The BasicLTI work just reinforced the
validity of the approach.

We have the pieces and are starting to look at the whole.

Regards,
           Alan


Alan Berg

Innovation working group
On the use of ICT in Education & Research
University of Amsterdam


On 25 April 2013 06:55, Steve Swinsburg <steve.swinsburg at gmail.com> wrote:

> I hope everyone is adding this event listening code in a different thread
> or you are going to have a performance issues at some stage since the code
> is run in series.
>
> SiteStats listens for all events and parses the ones it needs in order to
> collect its data, but spawns a separate thread for doing the heavy lifting
> (db work). Adding more event listeners is going to be problematic if any
> amount of work is run in the same thread since there are a huge number of
> events being fired with many concurrent users.
>
> To answer the original question, you could listen for the event, get the
> reference then go and figure out what the data was since most tools should
> fire events after the data is written. But I'd be looking at extending one
> of the existing implementations that does this already, like Dashboard or
> LOI's system.
>
> cheers,
> Steve
>
>
> On Thu, Apr 25, 2013 at 7:10 AM, John Bush <john.bush at rsmart.com> wrote:
>
>> in the use cases we have, you only need to have at least the identity
>> then your external application can make call back to collect extra
>> data using soap, rest, I guess direct database access, etc.  At least
>> in this way you avoid having to deploy this code into the core CLE.
>>
>> On Wed, Apr 24, 2013 at 11:16 AM, Thomas Amsler <tpamsler at ucdavis.edu>
>> wrote:
>> > John,
>> >
>> > How do you get the event associated data if the event data doesn't
>> include
>> > everything that you need?
>> >
>> > Best,
>> > -- Thomas
>> >
>> >
>> > On Wed, Apr 24, 2013 at 11:10 AM, John Bush <john.bush at rsmart.com>
>> wrote:
>> >>
>> >> We do this via the messageservice and jms.  There is an event
>> >> publisher in trunk that can capture sakai events and publish them as
>> >> jms messages.
>> >>
>> >>
>> >>
>> https://source.sakaiproject.org/contrib/messageservice/trunk/impl/src/java/org/sakaiproject/messageservice/jms/activemq/EventPublisher.java
>> >>
>> >> On Wed, Apr 24, 2013 at 8:36 AM, Thomas Amsler <tpamsler at ucdavis.edu>
>> >> wrote:
>> >> > Hello,
>> >> >
>> >> > We are trying to find a method to capture Sakai data as it is
>> created,
>> >> > in
>> >> > real time, and send it to an external system.
>> >> >
>> >> > e.g.
>> >> > Instructor creates a new announcement. As the announcement is
>> created,
>> >> > we
>> >> > want to capture that data/event and send it to an external system.
>> >> >
>> >> > Possible solutions:
>> >> >
>> >> > 1. Write a component that listens on Sakai events and extracts the
>> >> > needed
>> >> > data as the events occur.
>> >> >
>> >> > 2. Write DB triggers on selected tables, e.g. Announcements, and
>> capture
>> >> > and
>> >> > send the data that way.
>> >> >
>> >> > Has anybody in the Sakai community tried doing something like this?
>> >> >
>> >> > Best,
>> >> > -- Thomas
>> >> >
>> >> >
>> >> >
>> >> > _______________________________________________
>> >> > sakai-dev mailing list
>> >> > sakai-dev at collab.sakaiproject.org
>> >> > http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>> >> >
>> >> > TO UNSUBSCRIBE: send email to
>> >> > sakai-dev-unsubscribe at collab.sakaiproject.org
>> >> > with a subject of "unsubscribe"
>> >>
>> >>
>> >>
>> >> --
>> >> John Bush
>> >> 602-490-0470
>> >
>> >
>>
>>
>>
>> --
>> John Bush
>> 602-490-0470
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to
>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>> "unsubscribe"
>>
>
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
>



-- 
Regards,
       Alan

Alan Berg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130425/052fa996/attachment.html