Paul,

I like your thought on sharing java objects  between Sakai and XWiki.  The 
benefits and enhanced capabilities could be significant.  There is an 
Entity Broker in Sakai used for purposes of sharing objects between tools 
that we could use.  We are looking closer into this and perhaps even a 
proof of concept where we might access, for example,  the Assignment tool 
and access the grades for a given student that will get rendered with the 
custom data for the user visiting the assignment wiki page.

Once we get our initial investigation done I will explore the interest 
with the Sakai community.  My guess is there will be a lot of interest in 
this capability.

- Adam

Adam Hocek
Information Technology
Marist College
tel: 845-575-3948



From:   Paul Libbrecht <[email protected]>
To:     XWiki Developers <[email protected]>
Date:   07/05/2011 04:29 PM
Subject:        Re: [xwiki-devs] a successful integration of XWiki with 
Sakai
Sent by:        [email protected]




Le 1 juil. 2011 à 18:01, Adam Hocek a écrit :

> I do agree the granularity of fine grained permissions in XWiki is very 
> flexible.  We just had to manage the mapping of Sakai user/group roles, 
> that are specific to Sakai (course) sites, and expose the granular 
> permissions of XWiki.
> 
> In your comment there was one thing I wasn't clear on about providing 
> queries/reports on Sakai LMS data.  Are there specific ways in which 
XWiki 
> can help with that process?  Within Sakai there are some reporting 
tools, 
> but there is still desire to improve on the data collected and provide 
> better tracking tools.

Correct, XWiki has a fairly deep programming model, at entry level using 
velocity, a bit deeper with Groovy, and far deeper with java. All three 
layers can be published in a web-fashion.

My scenario was fo a teacher to invite a "helping coder" (it could even be 
a consulting company) that would write dedicated reports that would use 
the Sakai objects to report in a more dedicated fashion. This would 
support learning analytics to become heavily learning scenario specific.

For this to work, I would consider it easier for Sakai and XWiki to share 
some java objects, which is probably easy.


Le 4 juil. 2011 à 11:20, Ludovic Dubost a écrit :

>> Thank you for the mention of curriki.org.  Many Sakai deployments are 
in
>> colleges and universities, but there is a growing number of K-12 grade
>> schools using Sakai, in which case the curriki integration would be a 
good
>> match.
> 
> Note that Curriki is available as separate software, so it's not
> necessarly about the K-12 content of Curriki.org.
> Curriki could be used as the software as a content repository.


Correct, see http://curriki.xwiki.org for more details.
It's clearly complementary to Sakai: a repository is to serve a large 
population while an LMS is meant to be institution specialized.

paul
_______________________________________________
devs mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/devs

_______________________________________________
devs mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/devs

Reply via email to