Adopt Settings From Other SCORM Modules

1 Initial Problem

SCORM settings are very complex, not always intuitiv and wrong settings can lead to unwanted behavior of the SCORM module. Therefore it is important to choose the correct settings for the SCORM modules.

There are no templates for SCORM settings meaning that the settings have to be changed for every SCORM module seperately.  Since the default settings are not suitable in most szenarios, this leads to a huge amount of workload on installations where SCORM is frequently used in multiple modules. And it can lead to mistakes when forgetting settings or selecting a wrong option. 

To solve this problem we suggest to implement a feature where settings from one SCORM module can be adopted to another. With this feature it would be possible to use specific SCORM module as templates to ruduce workload and errors. 

2 Conceptual Summary

The settings of SCORM modules will get a new subtab in which another SCORM module can be selected from which the settings can be adopted.

It will be possible to select out of all modules with matching SCORM version. In addition to that the acting ILIAS-login need to have the permission "Edit Settings" for the SCORM modules.

Optional (depending on funding): After a SCORM module is selected for adopting the setting from it, a comparision with the divergent settings will be shown.

The relevant settings for SCORM modules are stored in the database table "sahs_lm". When adopting the settings from another SCORM module the column of the table can be used. Only the ID needs to be changed.

The following settings should be left out: title, description, online, tile Image. This is not a problem since they all are not included in the table "sahs_lm". 

3 User Interface Modifications

3.1 List of Affected Views

3.2 User Interface Details

The subtab "Adopt Settings From SCORM Module" will be added to the settings of a SCORM module (see mockup).

In this tab the SCORM module from which the settings should be adopted can be selected using ilExplorer.

We optionally (depending on funding) suggest to implement a view that shows the differences in the settings between the current module and the selected module (see mockup).

3.3 New User Interface Concepts

The feature is implemented with existing UI components and does not introduce any new UI concepts.

3.4 Accessibility Implications

The use of existing UI components does not introduce any new implications for accessibility.

4 Additional Information

4.1 Involved Authorities

4.2 Technical Aspects

This feature depends on ilExplorer.

4.3 Privacy

No new personal data is collected or processed as a result of the implementation of the feature.

4.4 Security

The implementation of the feature does not introduce any new attack vectors.

The only security relevant consideration needed is to decide which permission needs to be granted for showing a SCORM module in the selection view.

4.5 Contact

Person to be contacted in case of questions about the feature or for funding offers: Wischniak, Stanislav [wischniak], Mix, Eva [emix] 

4.6 Funding

Funding status and funding parties are listed in the block 'Status of Feature' in the right column of this page.

If you are interested to give funding for this feature, please get into contact with the person mentioned above as 'Contact'.

5 Discussion

6 Implementation

Feature has been implemented by {Please add related profile link of this person}

6.1 Description and Screenshots

{ Description of the final implementation and screenshots if possible. }

6.2 Test Cases

Test cases completed at {date} by {user}

6.3 Privacy

Information in privacy.md of component: updated at {date} by {user} | no change required

6.4 Approval

Approved at {date} by {user}.