Feature Wiki

Information about planned and released features

Tabs

Learning Object Metadata for Mediacast, Mediapool, and Blog

Page Overview

1 Initial Problem
2 Conceptual Summary
3 User Interface Modifications
- 3.1 List of Affected Views
- 3.2 User Interface Details
- 3.3 New User Interface Concepts
- 3.4 Accessibility Implications
4 Technical Information
5 Privacy
6 Security
7 Contact
8 Funding
9 Discussion
10 Implementation

1 Initial Problem

Currently, not every type of object in ILIAS can carry LOM. Among the objects not supporting LOM at the moment are Mediacast, Mediapool, and Blog.

2 Conceptual Summary

Support for LOM is added to Mediacast, Mediapool, and Blog.

As a side effect, these objects will then also support Taxonomies better, since their 'Metadata' tab will always be shown.

3 User Interface Modifications

3.1 List of Affected Views

Mediacast > Metadata
Mediapool > Metadata
Blog > Metadata

3.2 User Interface Details

The objects will have a tab 'Metadata' with subtab 'LOM', which will always be shown. Like for all other LOM-enabled objects, the subtab 'LOM' contains the quick edit form for the object's LOM, as well as a button leading to the full LOM editor (see Moving LOM Metadata Editor to Kitchensink for details).

3.3 New User Interface Concepts

No new UI concepts required.

3.4 Accessibility Implications

No known accessibility implications.

4 Technical Information

As for all other objects, the LOM fields general > title and general > description will automatically be set to the object's title and description and their respective languages (translations via Multilingualism excluded). No other LOM fields will be filled automatically.

The required infrastructure for this mechanism is already implemented in the Object service (see e.g. ilObject::createMetaData), and just has to be used in the Data Collection. For details, see here.

5 Privacy

No personal data is automatically stored in the LOM of Mediacasts, Mediapools, and Blogs. For information about what personal data can be entered manually into the LOM of an object, see the privacy information of MetaData.

6 Security

No foreseeable security implications.

7 Contact

Author of the Request: Schmitz, Tim [tschmitz]
Maintainer: Killing, Alexander [alex] for Mediacast, Mediapool, and Blog, Meyer, Stefan [smeyer] and Schmitz, Tim [tschmitz] for MetaData
Implementation of the feature is done by: Schmitz, Tim [tschmitz]

8 Funding

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

FH Dortmund

9 Discussion

JourFixe, ILIAS [jourfixe], 18 MAR 2024: We highly appreciate this suggestion and schedule the feature for ILIAS 10.

10 Implementation

Implemented as described above, Blog, Mediacast and Mediapool now support LOM as other objects do. They have a 'Metadata'-tab where the LOM editor can be accessed, their title and description is synchronized with the respective LOM fields, LOM is shown on their Info Page, fields like keywords are found in the search, LOM persists through export/import and copying, etc.