Search

eNOSHA is an open source Learning Object Repository (LOR) developed at the University of Colombo School of Computing (UCSC) in a collaboration between UCSC in Sri Lanka, and two universities from Sweden during 2009 and 2010. eNOSHA is a system where content developers and instructional designers can store and reuse learning objects on 4 different aggregation levels. The system was built based on a need analysis at UCSC in late 2008 and was taken into use at the eLearning Centre at UCSC in early 2010. The system has so far been successful and supported the organisation and reuse of e-learning content at the UCSC eLearning Centre (eLC). However, there still exist several reasons for further improvements when it comes to usability and user-friendliness. Moodle is one of the most popular open-source Course Management Systems (CMS) and has been used in the daily work at UCSC during the last 5 years. Moodle is an effective system for building courses and structure course material but features for storing, retrieving and version handling of learning objects is still under construction in the Moodle community. Persons working with course development need a LOR as well as a CMS in their daily work but to be forced to multiple logins and switching between systems is not good usability or user-friendly. This paper is about the integration between the eNOSHA system and the Moodle system and how it best should be done. Should the eNOSHA system be connected and integrated as a Moodle module in collaboration with the Moodle developing community or is it a better idea to build a module in eNOSHA that handles the communication with Moodle? From a developer’s perspective, the building of a Moodle module to handle the connection to the eNOSHA system would be a fast and convenient alternative since the Moodle module template provided by moodle.org could be used as a skeleton for an integration of the additional functionality. However, the Moodle community did not like the idea of integ

eNOSHA is an open source Learning Object Repository (LOR) developed at the University of Colombo School of Computing (UCSC) in a collaboration between UCSC in Sri Lanka, and two universities from Sweden during 2009 and 2010. eNOSHA is a system where content developers and instructional designers can store and reuse learning objects on 4 different aggregation levels. The system was built based on a need analysis at UCSC in late 2008 and was taken into use at the eLearning Centre at UCSC in early 2010. The system has so far been successful and supported the organisation and reuse of e-learning content at the UCSC eLearning Centre (eLC). However, there still exist several reasons for further improvements when it comes to usability and user-friendliness. Moodle is one of the most popular open-source Course Management Systems (CMS) and has been used in the daily work at UCSC during the last 5 years. Moodle is an effective system for building courses and structure course material but features for storing, retrieving and version handling of learning objects is still under construction in the Moodle community. Persons working with course development need a LOR as well as a CMS in their daily work but to be forced to multiple logins and switching between systems is not good usability or user-friendly. This paper is about the integration between the eNOSHA system and the Moodle system and how it best should be done. Should the eNOSHA system be connected and integrated as a Moodle module in collaboration with the Moodle developing community or is it a better idea to build a module in eNOSHA that handles the communication with Moodle? From a developer’s perspective, the building of a Moodle module to handle the connection to the eNOSHA system would be a fast and convenient alternative since the Moodle module template provided by moodle.org could be used as a skeleton for an integration of the additional functionality. However, the Moodle community did not like the idea of integ

eNOSHA is an open source Learning Object Repository (LOR) developed at the University of Colombo School of Computing (UCSC) in a collaboration between UCSC in Sri Lanka, and two universities from Sweden during 2009 and 2010. eNOSHA is a system where content developers and instructional designers can store and reuse learning objects on 4 different aggregation levels. The system was built based on a need analysis at UCSC in late 2008 and was taken into use at the eLearning Centre at UCSC in early 2010. The system has so far been successful and supported the organisation and reuse of e-learning content at the UCSC eLearning Centre (eLC). However, there still exist several reasons for further improvements when it comes to usability and user-friendliness. Moodle is one of the most popular open-source Course Management Systems (CMS) and has been used in the daily work at UCSC during the last 5 years. Moodle is an effective system for building courses and structure course material but features for storing, retrieving and version handling of learning objects is still under construction in the Moodle community. Persons working with course development need a LOR as well as a CMS in their daily work but to be forced to multiple logins and switching between systems is not good usability or user-friendly. This paper is about the integration between the eNOSHA system and the Moodle system and how it best should be done. Should the eNOSHA system be connected and integrated as a Moodle module in collaboration with the Moodle developing community or is it a better idea to build a module in eNOSHA that handles the communication with Moodle? From a developer’s perspective, the building of a Moodle module to handle the connection to the eNOSHA system would be a fast and convenient alternative since the Moodle module template provided by moodle.org could be used as a skeleton for an integration of the additional functionality. However, the Moodle community did not like the idea of integ

eNOSHA is an open source Learning Object Repository (LOR) developed at the University of Colombo School of Computing (UCSC) in a collaboration between UCSC in Sri Lanka, and two universities from Sweden during 2009 and 2010. eNOSHA is a system where content developers and instructional designers can store and reuse learning objects on 4 different aggregation levels. The system was built based on a need analysis at UCSC in late 2008 and was taken into use at the eLearning Centre at UCSC in early 2010. The system has so far been successful and supported the organisation and reuse of e-learning content at the UCSC eLearning Centre (eLC). However, there still exist several reasons for further improvements when it comes to usability and user-friendliness. Moodle is one of the most popular open-source Course Management Systems (CMS) and has been used in the daily work at UCSC during the last 5 years. Moodle is an effective system for building courses and structure course material but features for storing, retrieving and version handling of learning objects is still under construction in the Moodle community. Persons working with course development need a LOR as well as a CMS in their daily work but to be forced to multiple logins and switching between systems is not good usability or user-friendly. This paper is about the integration between the eNOSHA system and the Moodle system and how it best should be done. Should the eNOSHA system be connected and integrated as a Moodle module in collaboration with the Moodle developing community or is it a better idea to build a module in eNOSHA that handles the communication with Moodle? From a developer’s perspective, the building of a Moodle module to handle the connection to the eNOSHA system would be a fast and convenient alternative since the Moodle module template provided by moodle.org could be used as a skeleton for an integration of the additional functionality. However, the Moodle community did not like the idea of integ

eNOSHA is an open source Learning Object Repository (LOR) developed at the University of Colombo School of Computing (UCSC) in a collaboration between UCSC in Sri Lanka, and two universities from Sweden during 2009 and 2010. eNOSHA is a system where content developers and instructional designers can store and reuse learning objects on 4 different aggregation levels. The system was built based on a need analysis at UCSC in late 2008 and was taken into use at the eLearning Centre at UCSC in early 2010. The system has so far been successful and supported the organisation and reuse of e-learning content at the UCSC eLearning Centre (eLC). However, there still exist several reasons for further improvements when it comes to usability and user-friendliness. Moodle is one of the most popular open-source Course Management Systems (CMS) and has been used in the daily work at UCSC during the last 5 years. Moodle is an effective system for building courses and structure course material but features for storing, retrieving and version handling of learning objects is still under construction in the Moodle community. Persons working with course development need a LOR as well as a CMS in their daily work but to be forced to multiple logins and switching between systems is not good usability or user-friendly. This paper is about the integration between the eNOSHA system and the Moodle system and how it best should be done. Should the eNOSHA system be connected and integrated as a Moodle module in collaboration with the Moodle developing community or is it a better idea to build a module in eNOSHA that handles the communication with Moodle? From a developer’s perspective, the building of a Moodle module to handle the connection to the eNOSHA system would be a fast and convenient alternative since the Moodle module template provided by moodle.org could be used as a skeleton for an integration of the additional functionality. However, the Moodle community did not like the idea of integ

eNOSHA is an open source Learning Object Repository (LOR) developed at the University of Colombo School of Computing (UCSC) in a collaboration between UCSC in Sri Lanka, and two universities from Sweden during 2009 and 2010. eNOSHA is a system where content developers and instructional designers can store and reuse learning objects on 4 different aggregation levels. The system was built based on a need analysis at UCSC in late 2008 and was taken into use at the eLearning Centre at UCSC in early 2010. The system has so far been successful and supported the organisation and reuse of e-learning content at the UCSC eLearning Centre (eLC). However, there still exist several reasons for further improvements when it comes to usability and user-friendliness. Moodle is one of the most popular open-source Course Management Systems (CMS) and has been used in the daily work at UCSC during the last 5 years. Moodle is an effective system for building courses and structure course material but features for storing, retrieving and version handling of learning objects is still under construction in the Moodle community. Persons working with course development need a LOR as well as a CMS in their daily work but to be forced to multiple logins and switching between systems is not good usability or user-friendly. This paper is about the integration between the eNOSHA system and the Moodle system and how it best should be done. Should the eNOSHA system be connected and integrated as a Moodle module in collaboration with the Moodle developing community or is it a better idea to build a module in eNOSHA that handles the communication with Moodle? From a developer’s perspective, the building of a Moodle module to handle the connection to the eNOSHA system would be a fast and convenient alternative since the Moodle module template provided by moodle.org could be used as a skeleton for an integration of the additional functionality. However, the Moodle community did not like the idea of integ