Feature Wiki
Tabs
Better Organization of Copyright Licences
Page Overview
[Hide]- 1 Initial Problem
- 2 Conceptual Summary
- 3 User Interface Modifications
- 4 Additional Information
- 4.1 Involved Authorities
- 4.2 Technical Aspects
- 4.3 Privacy
- 4.4 Security
- 4.5 Contact
- 4.6 Funding
- 5 Discussion
- 6 Implementation
- 6.1 Description and Screenshots
- 6.2 Test Cases
- 6.3 Privacy
- 6.4 Approval
1 Initial Problem
Currently, preset copyright licences in ILIAS can only be active or outdated. Outdated licences can not be selected for objects, but are still displayed for older objects that already had those licences selected.
This very short hierarchy is not sufficient for practical use. For example, sometimes a licence should not be selected for newly created content, but has to be available for selection when pre-existing material is used in the creation of content (e.g. a file under a 3.0 Creative Commons licence is uploaded as an object to ILIAS). Currently this leads to installation having a large list of (non-outdated) licences configured (e.g. all 4.0 and 3.0 Creative Commons licences), needlessly confusing users.
2 Conceptual Summary
It should be possible to mark licences as 'Featured' in the administration. Featured licences should be emphasized in forms where licences are selected, and non-featured licences should be deemphasized.
3 User Interface Modifications
3.1 List of Affected Views
- Metadata Administration > Available Copyrights
- LOM tab of objects
- creation screen for File objects
3.2 User Interface Details
new copyright input: radios for featured licences, last radio 'other' with dropdown sub-input containing all other (non-outdated) licences.
How to display the currently selected licence, if it is outdated? What about manual input?
3.3 New User Interface Concepts
-
3.4 Accessibility Implications
No accessibility implications.
4 Additional Information
4.1 Involved Authorities
- Authority to Sign off on Conceptual Changes: Schmitz, Tim [tschmitz], Meyer, Stefan [smeyer]
- Authority to Sign off Code Changes: Schmitz, Tim [tschmitz], Meyer, Stefan [smeyer]
If this request is related to multiple components, please list both authorities for all related components.
4.2 Technical Aspects
The LOM API should offer a pre-built 'Copyright' input field to consuming components. There should be some light configuration possible (e.g. only make featured licences selectable, or allow custom input).
4.3 Privacy
No privacy implications.
4.4 Security
No foreseeable security implications.
4.5 Contact
Person to be contacted in case of questions about the feature or for funding offers: Schmitz, Tim [tschmitz]
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}
- {Test case number linked to Testrail} : {test case title}
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}.
Last edited: 2. Sep 2026, 15:55, Schmitz, Tim [tschmitz]
