Customizable LOM Digest

1 Initial Problem

OER-repositories (ZOERR, Twillo, etc.) require certain, specific LOM data. To provide this repository with this data, users need to know:

• what is required
• where to edit it among the more than 100 field options

2 Conceptual Summary

organisations should be able to configure thte LOM Digest. The LOM Digest can then comprise all repsitory-required data with some affordance.

3 User Interface Modifications

3.1 List of Affected Views

• Administration > Search and Find > Metadata > Copyright & OER > LOM Digest
• Object > Metadata > LOM

3.2 User Interface Details

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 data point, provide a short explanation of why it is necessary to use that data. You may consult the Privacy Clinic for questions regarding the legality, minimization, or appropiate use of personal data in compliance with applicable privacy regulations such as GDPR. }

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: {Please add your name.}
• Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
• 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}.