[Building Sakai] Activity streams / dashboard

[Mark Breuker]

Hi Jim,

I read one of the goals for this project is to make activity streams a Kernel service. Would it be an idea to then make is very generic and use a standardized way of outputting streams such as http://activitystrea.ms/specs/json/1.0/

This could then be used by multiple tools (eg Dashboard or our Activity Stream Widget). We could then collaborate on the service part (eg implementing activity providers etc). Could be a nice feature for Sakai 2.10.

Regards,

Mark
________________________________
Van: Jim Eng [jimeng at umich.edu]
Verzonden: donderdag 3 januari 2013 17:11
To: Jim Eng
Cc: Mark Breuker; Adrian Fish; sakai-dev Developers; Zhen Qian
Onderwerp: Re: [Building Sakai] Activity streams / dashboard

And because you were asking about the processing of events to add items to the dashboard, I forgot to mention Gonzalo, who did the bulk of the work on the UI.

BTW, there's a ticket with a patch to add an entity broker for dashboard items, which will be committed soon.

Jim


On Jan 3, 2013, at 11:01 AM, Jim Eng wrote:

Yes, along with Zhen Qian.


On Jan 3, 2013, at 9:29 AM, Mark Breuker wrote:

Hi Jim,

I see most open issues in Jira for this project are assigned to your name. Does that mean you are currently the lead developer for this project?

- Mark
________________________________
Van: Jim Eng [jimeng at umich.edu]
Verzonden: donderdag 3 januari 2013 14:55
To: Adrian Fish
Cc: Mark Breuker; sakai-dev at collab.sakaiproject.org<mailto:sakai-dev at collab.sakaiproject.org>
Onderwerp: Re: [Building Sakai] Activity streams / dashboard

Thanks, Adrian.

Hi Mark,

We believe we have a fix in SVN for the performance problems Columbia experienced, but we have not yet done the requisite load tests to determine how well they work.  I expect we will see a little more tuning as a result of the load testing.  That has been scheduled a couple times here at Michigan, but was put off due to immediate needs to perform tests related to our production environment.  Michigan is planning to use dashboard later this year, depending on the load test results.

Jim


On Jan 3, 2013, at 4:47 AM, Adrian Fish wrote:

Hi Mark,

It's still under development, as far as I know. Columbia pulled it from production due to performance problems and I think those issues have been, or are being addressed. It might be worth dropping Scott Sidall from Longsight a line to get an update on that.

I can help you out with hooking up other events; I did if for CLOG and YAFT and it's pretty easy.

Cheers,
Adrian.


2013/1/3 Mark Breuker <mbreuker at loi.nl<mailto:mbreuker at loi.nl>>
Hi all,

We plan to further improve our activity stream (see attachment) that we show on our student's dashboard. I noticed there is similar work being done on the Dashboard tool (https://confluence.sakaiproject.org/x/TIPfB)

Although the UI works differently I think the back-end services are pretty similar to what we have developed. Ie a tool posts an event, this event is processed and added to a list of recent activities.

If the dashboard tool is still under active development I would like to get in touch to see if we can collaborate (extend the number of tools that can be listed in the activity stream).

Regards,

Mark



Mark Breuker
Product Owner
Tel.: +31 71 5451 203<tel:%2B31%2071%205451%20203>

Leidse Onderwijsinstellingen bv
Leidsedreef 2
2352 BA Leiderdorp
www.loi.nl<http://www.loi.nl/>

________________________________

<nwss_loi6abe.gif>

De informatie verzonden met dit e-mailbericht (en bijlagen) is uitsluitend bestemd voor de geadresseerde(n) en zij die van de geadresseerde(n) toestemming hebben dit bericht te lezen. Gebruik door anderen dan geadresseerde(n) is verboden. De informatie in dit e-mailbericht (en de bijlagen) kan vertrouwelijk van aard zijn en kan binnen het bereik vallen van een wettelijke geheimhoudingsplicht. Indien u deze e-mail ten onrechte ontvangen hebt, wordt u verzocht ons daarvan zo spoedig mogelijk per e-mail of telefonisch op de hoogte te stellen, en het ontvangen bericht (en de bijlagen) te wissen zonder deze te lezen, te kopiëren of aan derden bekend te stellen.

P  Denk aan het milieu voordat u dit bericht print


_______________________________________________
sakai-dev mailing list
sakai-dev at collab.sakaiproject.org<mailto: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<mailto:sakai-dev-unsubscribe at collab.sakaiproject.org> with a subject of "unsubscribe"

_______________________________________________
sakai-dev mailing list
sakai-dev at collab.sakaiproject.org<mailto: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<mailto:sakai-dev-unsubscribe at collab.sakaiproject.org> with a subject of "unsubscribe"




-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130110/334087c9/attachment.html