2. Example

2.4. Stand-alone website (File/URL) - COMET lesson or Simulator

1. COMET lesson - embedded File

Reusing ready resources saves time. However many resources are a) to broad and b) have its own navigation.

Ideally we will find time and tools to retrieve only a chunk of content that we really need from a broader lesson or module. Otherwise we need to point the learner and inform what part of the content is required from him to view. 

Resources, like COMET lessons, have their own navigation as well as the course website. The double navigation may be confusing for learners. In addition, links included in the resource may lead to external website or external resources. It is good to be clear about what is the essential and what optional part.

File feature is one of the solutions to upload a stand-alone website to and have it run in the course environment. For details see the lesson on "Displaying resources - Appearance".

2. Simulator - URL or a File to download

Simulators are becoming more and more popular in our training. Like any interactive exercise they may be large files. Storing a simulator in an external repository may be necessary due to the space it occupies on the server. Accordingly a simulator would be shared as an URL pointing to the external repository. Nevertheless, you should keep in mind that there will be two separate spaces to keep up-to-date -- Moodle course and external repository. 

Another way of sharing a simulator, which will reassure that the learners have the file saved locally is to using File with a Force download setting.