jump to navigation

Update: Interoperability With JORUM October 27, 2009

Posted by YvonneMonterroso in : Comms , trackback

I have been having some really good communication back and forth with Peter and Gareth at JORUM. We had initially run into an issue being able to access JORUM via harvesting. As it happens, JORUM had turned off the harvesting service on their side for an interim period. They have now turned the service back on allowing us to pass the first hurdle. Further tests uncovered the next issue which was a problem in the JORUM identify request. We’re currently working on a technical work around for this issue.

We have also engaged to understand more about how JORUM uses Shibboleth to authenticate users. Gareth indicated that JORUM does not have its own IdP and the Shibboleth implementation would use the NTU institutional IdP to authenticate users. Bill Lee, technical product manager for the Integration and Middleware team has been engaged in these conversations and using this information to ensure that our product can successfully integrate with the NTU authentication model. Bill has indicated that using the NTU IdP to authenticate is a solution that will be easier to use as the need to synchronize between a JORUM and NTU IdP would have caused added complexity to the model.

Gareth also indicated, as several people working on the project are already aware, that JORUM is launching an open service in January that does not require authentication. I think it will make sense to set up the integration with the open service when it is launched in January.

Lastly, an update on publishing objects from NTU to JORUM. Currently there is only one method of publishing to JORUM and that is using their OER deposit tool. The OER deposit tool is a user interface for depositing information and we are currently limited to using this to manually deposit materials. This process will be external to the Desire2Learn tools. In the future, as JORUM adds other options, it may be possible integrate the LOR and JORUM seamlessly through a web service call.

Comments»

no comments yet - be the first?