Better Organization of Copyright Licences

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.

Further, ILIAS comes with pre-installed Creative Commons licences, but after that treats them as user generated. This has some unfortunate side effects, which have caused problems in the past: it is needlessly complicated to make changes to their title, description, or icon as part of the maintenance of ILIAS, we can not offer their icons as part of ILIAS but have to link to them, etc.

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.

It should not be possible to edit or delete the pre-installed Creative Commons licences, but they should be deactivatable. Is that the same as outdated, or is that a new status?

3 User Interface Modifications

3.1 List of Affected Views

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

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}

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}.