LOM metadata for Learning Sequences

1 Initial Problem

Metadata (and thus taxonomies) cannot yet be used in learning sequences. For this reason, learning sequences cannot be provided with information on the language and licence, which would be particularly relevant in cases where these learning sequences are to be exported and published as OER, for example.

2 Conceptual Summary

Based on objects such as the content page a new tab "Metadata" is to be displayed in the learning sequence. This tab is only visible to users with the right to edit the settings.

There is no subtab shown unless the learning sequence is in a category that uses taxonomies. Then the two subtabs LOM and Taxonomies are displayed.

If possible, the new LOM Metadata Editor from the KS should be used: Moving LOM Metadata Editor to Kitchensink

3 User Interface Modifications

3.1 List of Affected Views

• learning sequence - new tab "Metadata" - subtab LOM
• learning sequence - new tab "Metadata" - subtab Taxonomy Assignment

3.2 User Interface Details

In case, the parent category uses taxonomies, the subtab Taxonomy Assignment is displayed:

3.3 New User Interface Concepts

{ If the proposal introduces any completely new user interface elements, you might consult UI Kitchen Sink in order to find the necessary information to propose new UI-Concepts. Note that any maintainer might gladly assist you with this. }

3.4 Accessibility Implications

{ If the proposal contains potential accessibility issues that are neither covered by existing UI components nor clarified by guidelines, please list them here. For every potential issue please either propose a solution or write down a short risk assessment about potential fallout if there would be no solution for the issue. }

4 Technical Information

{ The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues. }

5 Privacy

{ Please list all personal data that will need to be stored or processed to implement this feature. For each date give a short explanation why it is necessary to use that date. }

6 Security

{ Does the feature include any special security relevant changes, e.g. the introducion of new endpoints or other new possible attack vectors. If yes, please explain these implications and include a commitment to deliver a written security concept as part of the feature development. This concept will need an additional approvement by the JourFixe. }

7 Contact

• Author of the Request: Seibt, Alina [alina.seibt]
• Maintainer: Klees, Richard [rklees]
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

8 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• …

9 Discussion

10 Implementation

{ The maintainer has to give a description of the final implementation and add screenshots if possible. }

Test Cases

Test cases completed at {date} by {user}

• {Test case number linked to Testrail} : {test case title}

Privacy

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

Approval

Approved at {date} by {user}.