Adam, are Sakai objects going to be accessible to the XWiki scripts? This could have a great impact I believe. (e.g. to provide specific views on the LMS data; e.g. "the sessions of learners that have been taking this kind of learning activity and had issues"?) The development model of Sakai is close to that of Moodle, if I do not mistake: plugins. The one of XWiki is considerably more flexible I believe, deployment can be fully web-based and authorizations are fine grained. So you can give admin rights to a space to "the current TA helping my course" so that "he gets you running with some development that is local to your space". Le 29 juin 2011 à 22:29, Ludovic Dubost a écrit :

Le 1 juil. 2011 à 18:01, Adam Hocek a écrit : 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 : 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

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 <paul(a)hoplahup.net> To: XWiki Developers <devs(a)xwiki.org> Date: 07/05/2011 04:29 PM Subject: Re: [xwiki-devs] a successful integration of XWiki with Sakai Sent by: devs-bounces(a)xwiki.org Le 1 juil. 2011 à 18:01, Adam Hocek a écrit : XWiki 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 : in good 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 devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

Hi Ludovic, Thanks for your reply back. Sorry for not getting back sooner. I do have a link to the presentation at http://www.slideshare.net/ahocek/xwiki-sakai-integration . I would be happy to give you more details on the integration and options we looked at. In short we implemented a Sakai tool that used Sakai's user, group, roles management tools to map to XWiki groups and permissions. We have hooks into when a Sakai course site and roster are updated so to synchronize with XWiki users and groups. We looked at two UI options, exposing XWiki through an iframe or writing Sakai-side UI components to interface directly with XWiki. We opted for a mixed implementation with most of XWiki being exposed through an iframe using XWiki css and velocity scripts to customize. For editing we use Sakai's standardized editor, FCKEditor (later will move to CKEditor). We added widgets to the editor to allow XWiki pages to reference Sakai resources. There could of course be other widgets that could added into the editor and integrate with specific Sakai tools. The rest of implementation exposes XWiki in an iframe for views, annotations, comments, history, etc.. Last comment on the implementation, we looked at both XWiki'a REST and RPC implementations. We first implemented using the REST API and found that response was a little slow for certain accumulative queries and iterations. The RPC implementation was more responsive, but in the end it sounds like the XWiki community is more interested in supporting the REST API so we would go with a REST implementation too. 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. - Adam Adam Hocek Information Technology Marist College tel: 845-575-3948 From: Ludovic Dubost <ludovic(a)xwiki.com> To: XWiki Developers <devs(a)xwiki.org> Date: 06/29/2011 04:29 PM Subject: Re: [xwiki-devs] a successful integration of XWiki with Sakai Sent by: devs-bounces(a)xwiki.org Hi Adam, This is great ! I've seen some tweets during the conference that announced the session. I heard a lot about Sakai and it's great that there is now an integration. We'd love to know the type of integration you did. Is it authentication, UI level integration, content integration. If you have a pointer to your slides of the presentation that would be great. You might also know the Curriki (http://www.curriki.org) is build on top of the XWiki Software, which is an education oriented software which is also released under the LGPL licence. It could be possible to piggyback on your integration to integrate Curriki with Sakai. Ludovic 2011/6/29 Adam Hocek <Adam.Hocek(a)marist.edu> less greater will -- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

Here are my answers to your questions. Data is pushed from sakai to XWiki. The authentication, groups and rights is controlled by the tool and pushed to XWiki. So permissions set in Sakai are pushed to XWiki. We are in the process of committing the code to the Sakai repository and will include the velocity scripts as well. We chose the FCKEditor since this is the editor used in all Sakai tools. We did not want to introduce a different editor for the wiki. The output of the editor is in HTML/XHTML. Will do so in a separate email. Hope I was able to answer your questions satisfactorily. Let me know if something is still unclear. - Adam Adam Hocek Information Technology Marist College tel: 845-575-3948 From: Ludovic Dubost <ludovic(a)xwiki.com> To: XWiki Developers <devs(a)xwiki.org> Date: 07/04/2011 05:20 AM Subject: Re: [xwiki-devs] a successful integration of XWiki with Sakai Sent by: devs-bounces(a)xwiki.org Thanks for the feedback. Some more questions below. 2011/7/1 Adam Hocek <Adam.Hocek(a)marist.edu>du>: roles Great. It's not clear from the presentation if you pushed sakai data to XWiki or if you overriden the auth, groups and rights services ? We looked at two UI options, exposing XWiki scripts Is the iframe velocity script changes available somewhere ? Integration like that comes up from time to time and we don't have a clean "skin less" skin. It could be nice to share it. move You mention FCKEditor vs XWiki Editor ? What make you choose not to use the XWiki Editor ? Are you storing content as HTML/XHTML or are you talking to the XWiki conversion backend ? The annotations, RPC it REST It would be great to list the REST issues that you had and also any missing REST services that there might be. We should make sure our API is complete for people to work with. good 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. Ludovic announced integration. also Curriki -- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

Hi Manish, If I understand your question correctly, we are only using one instance of XWiki. This is automatically created at start-up. Under that instance we create and manage our wiki spaces. I will put in a separate email (tomorrow) the performance issues and suggestions we faced with using REST API. - Adam Adam Hocek Information Technology Marist College tel: 845-575-3948 From: xManish <shresthamanish(a)gmail.com> To: devs(a)xwiki.org Date: 07/05/2011 01:37 PM Subject: Re: [xwiki-devs] a successful integration of XWiki with Sakai Sent by: devs-bounces(a)xwiki.org Hi Adam, I am very interested in this topic as I have also been working on integrating xwiki to my application which has been released as beta version. Would you please let us know what level of integration did you had with the wiki? Like, was there auto wiki creation/deletion depending upon some action in your application? I have been trying to do that in our project and I have also used REST Api. But I have been facing the problem of performance as the wiki started growing. Could you please let us know what kind of things did you considered for the performance ? Thanks, Manish -- View this message in context: http://xwiki.475771.n2.nabble.com/a-successful-integration-of-XWiki-with-Sa… Sent from the XWiki- Dev mailing list archive at Nabble.com. _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs