5 Jul
2011
5 Jul
'11
10:28 p.m.
Le 1 juil. 2011 à 18:01, Adam Hocek a écrit :
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
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.