[xwiki-devs] a successful integration of XWiki with Sakai
Hello XWiki Developers, I wanted to let you know that we completed our first release of integration of XWiki with Sakai (sakaiproject.org). Sakai is an open source collaborative teaching and learning application used by many educational institutes worldwide. The integration replaces an older less supported wiki tool in Sakai. We presented the new tool at the recent Sakai 2011 conference in Los Angeles, CA, and are anticipating several schools to begin using the tool. I think this will be bring about greater exposure and have a positive impact for the respective open source communities. If anyone has any questions I'd be happy to try and answer them. We will probably be emailing to this list sometime soon with some specific questions and requests. Cheers, - Adam Adam Hocek Information Technology Marist College tel: 845-575-3948
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 <[email protected]>
Hello XWiki Developers,
I wanted to let you know that we completed our first release of integration of XWiki with Sakai (sakaiproject.org). Sakai is an open source collaborative teaching and learning application used by many educational institutes worldwide. The integration replaces an older less supported wiki tool in Sakai. We presented the new tool at the recent Sakai 2011 conference in Los Angeles, CA, and are anticipating several schools to begin using the tool. I think this will be bring about greater exposure and have a positive impact for the respective open source communities.
If anyone has any questions I'd be happy to try and answer them. We will probably be emailing to this list sometime soon with some specific questions and requests.
Cheers, - Adam
Adam Hocek Information Technology Marist College tel: 845-575-3948 _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost
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 :
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 <[email protected]>
Hello XWiki Developers,
I wanted to let you know that we completed our first release of integration of XWiki with Sakai (sakaiproject.org). Sakai is an open source collaborative teaching and learning application used by many educational institutes worldwide. The integration replaces an older less supported wiki tool in Sakai. We presented the new tool at the recent Sakai 2011 conference in Los Angeles, CA, and are anticipating several schools to begin using the tool. I think this will be bring about greater exposure and have a positive impact for the respective open source communities.
If anyone has any questions I'd be happy to try and answer them. We will probably be emailing to this list sometime soon with some specific questions and requests.
Cheers, - Adam
Adam Hocek Information Technology Marist College tel: 845-575-3948 _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Hi Paul, In responding to Ludovic I may have covered some of the questions you had. The only object s for far that would be accessible to XWiki scripts are Sakai resources (e.g. documents, links). 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. - Adam Adam Hocek Information Technology Marist College tel: 845-575-3948 From: Paul Libbrecht <[email protected]> To: XWiki Developers <[email protected]> Date: 06/29/2011 04:51 PM Subject: Re: [xwiki-devs] a successful integration of XWiki with Sakai Sent by: [email protected] 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 :
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 <[email protected]>
Hello XWiki Developers,
I wanted to let you know that we completed our first release of integration of XWiki with Sakai (sakaiproject.org). Sakai is an open source collaborative teaching and learning application used by many educational institutes worldwide. The integration replaces an older less supported wiki tool in Sakai. We presented the new tool at the recent Sakai 2011 conference in Los Angeles, CA, and are anticipating several schools to begin using the tool. I think this will be bring about greater exposure and have a positive impact for the respective open source communities.
If anyone has any questions I'd be happy to try and answer them. We will probably be emailing to this list sometime soon with some specific questions and requests.
Cheers, - Adam
Adam Hocek Information Technology Marist College tel: 845-575-3948 _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
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
Hi, I wanted to discuss and open up to comments some performance related issues we encountered when working with the REST API. In general working with the REST API was straightforward. The only area where we experienced problems was when needing to check permissions on a page to see if a given user had edit access to a page. To accomplish this we have to retrieve all pages, then iterate through the list of pages getting all objects, then iterate through the list of objects to get all permission objects and finally access the permissions, The amount of data going back and forth between queries has an impact on performance. As a side when we worked with the RPC a direct call to get permission objects simplifies the process. Along these lines would it make sense to extend the REST API to include a collection of permissions where we could query on users or pages? So given a permission setting and a list of users we would get back a list of pages or given a permission setting and a list of pages we would get back a list of users. I would be interested to hear back on this need and how the semantics for extending the REST API should be to support this type of use case. Thanks, - Adam Adam Hocek Information Technology Marist College tel: 845-575-3948
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
Paul, We looked closer at referencing Sakai entities within XWiki and found that there is an easy way to include not only Sakai resources, but to also include links to other Sakai tools (e.g. assignments, forums, ...) from the FCKEditor. The Sakai FCKEditor has a javascript plugin that allows access to Sakai's Entity Broker which allows references to other Sakai tools and properties. This enables a wiki page author to include references to resources and other entities within Sakai. - 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
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 <[email protected]> To: XWiki Developers <[email protected]> Date: 06/29/2011 04:29 PM Subject: Re: [xwiki-devs] a successful integration of XWiki with Sakai Sent by: [email protected] 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 <[email protected]>
Hello XWiki Developers,
I wanted to let you know that we completed our first release of integration of XWiki with Sakai (sakaiproject.org). Sakai is an open source collaborative teaching and learning application used by many educational institutes worldwide. The integration replaces an older less supported wiki tool in Sakai. We presented the new tool at the recent Sakai 2011 conference in Los Angeles, CA, and are anticipating several schools to begin using the tool. I think this will be bring about greater exposure and have a positive impact for the respective open source communities.
If anyone has any questions I'd be happy to try and answer them. We will probably be emailing to this list sometime soon with some specific questions and requests.
Cheers, - Adam
Adam Hocek Information Technology Marist College tel: 845-575-3948 _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Thanks for the feedback. Some more questions below. 2011/7/1 Adam Hocek <[email protected]>:
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.
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
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.
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.
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
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 ?
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.
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.
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. Ludovic
- Adam
Adam Hocek Information Technology Marist College tel: 845-575-3948
From: Ludovic Dubost <[email protected]> To: XWiki Developers <[email protected]> Date: 06/29/2011 04:29 PM Subject: Re: [xwiki-devs] a successful integration of XWiki with Sakai Sent by: [email protected]
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 <[email protected]>
Hello XWiki Developers,
I wanted to let you know that we completed our first release of integration of XWiki with Sakai (sakaiproject.org). Sakai is an open source collaborative teaching and learning application used by many educational institutes worldwide. The integration replaces an older less supported wiki tool in Sakai. We presented the new tool at the recent Sakai 2011 conference in Los Angeles, CA, and are anticipating several schools to begin using the tool. I think this will be bring about greater exposure and have a positive impact for the respective open source communities.
If anyone has any questions I'd be happy to try and answer them. We will probably be emailing to this list sometime soon with some specific questions and requests.
Cheers, - Adam
Adam Hocek Information Technology Marist College tel: 845-575-3948 _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost
Here are my answers to your questions.
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 ? 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.
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. We are in the process of committing the code to the Sakai repository and will include the velocity scripts as well.
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 ? 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.
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. 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 <[email protected]> To: XWiki Developers <[email protected]> Date: 07/04/2011 05:20 AM Subject: Re: [xwiki-devs] a successful integration of XWiki with Sakai Sent by: [email protected] Thanks for the feedback. Some more questions below. 2011/7/1 Adam Hocek <[email protected]>:
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.
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
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.
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.
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
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 ?
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.
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.
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. Ludovic
- Adam
Adam Hocek Information Technology Marist College tel: 845-575-3948
From: Ludovic Dubost <[email protected]> To: XWiki Developers <[email protected]> Date: 06/29/2011 04:29 PM Subject: Re: [xwiki-devs] a successful integration of XWiki with Sakai Sent by: [email protected]
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 <[email protected]>
Hello XWiki Developers,
I wanted to let you know that we completed our first release of integration of XWiki with Sakai (sakaiproject.org). Sakai is an open source collaborative teaching and learning application used by many educational institutes worldwide. The integration replaces an older less supported wiki tool in Sakai. We presented the new tool at the recent Sakai 2011 conference in Los Angeles, CA, and are anticipating several schools to begin using the tool. I think this will be bring about greater exposure and have a positive impact for the respective open source communities.
If anyone has any questions I'd be happy to try and answer them. We will probably be emailing to this list sometime soon with some specific questions and requests.
Cheers, - Adam
Adam Hocek Information Technology Marist College tel: 845-575-3948 _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
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-Sak... Sent from the XWiki- Dev mailing list archive at Nabble.com.
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 <[email protected]> To: [email protected] Date: 07/05/2011 01:37 PM Subject: Re: [xwiki-devs] a successful integration of XWiki with Sakai Sent by: [email protected] 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-Sak... Sent from the XWiki- Dev mailing list archive at Nabble.com. _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Hi Adam, That's great. FYI I've added a link to your integration slides here: http://www.xwiki.org/xwiki/bin/view/Main/ExternalLinks Thanks -Vincent On Jun 29, 2011, at 10:23 PM, Adam Hocek wrote:
Hello XWiki Developers,
I wanted to let you know that we completed our first release of integration of XWiki with Sakai (sakaiproject.org). Sakai is an open source collaborative teaching and learning application used by many educational institutes worldwide. The integration replaces an older less supported wiki tool in Sakai. We presented the new tool at the recent Sakai 2011 conference in Los Angeles, CA, and are anticipating several schools to begin using the tool. I think this will be bring about greater exposure and have a positive impact for the respective open source communities.
If anyone has any questions I'd be happy to try and answer them. We will probably be emailing to this list sometime soon with some specific questions and requests.
Cheers, - Adam
Adam Hocek
participants (5)
-
Adam Hocek -
Ludovic Dubost -
Paul Libbrecht -
Vincent Massol -
xManish