Feature Wiki
Tabs
File-Object: Setting for Copyright Selection Workflow
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
If copy rights are activated in an installation, the list of possible copyrights in the upload dialogue can become very long and confusing. However, this list is relevant if you want to encourage users to select the licence early on in the creation process. However, there is also the
2 Conceptual Summary
To counteract this problem, a new setting is being introduced in the administration, which globally determines how the licence selection workflow should take place:
- when uploading files or creating file objects (as before)
- afterwards via the metadata tab
If you select the setting that you want to select licences afterwards in the metadata tab, the licence selection will no longer be displayed in the upload dialogue. The file object then behaves in the same way as other ILIAS objects in the magazine, i.e. the licence is specified via the metadata tab.

If the Copright-Selection is disbled globally (Service deactivated), the Options get disbled as well:

The setting would be set to ‘During creation’ by default (e.g. when updating to ILIAS 11 or reinstalling), which maintains the previous behaviour.
3 User Interface Modifications
3.1 List of Affected Views
- Administration -> Repository & Objects -> File
3.2 User Interface Details
{ For each of these views please list all user interface elements that should be modified, added or removed. Please provide the textual appearance of the UI elements and their interactive behaviour. }
3.3 New User Interface Concepts
The feature is implemented with existing UI components and does not introduce any new UI concepts.
3.4 Accessibility Implications
The use of existing UI components does not introduce any new implications for accessibility.
4 Additional Information
4.1 Involved Authorities
- Authority to Sign off on Conceptual Changes: Schmid, Fabian [fschmid]
- Authority to Sign off Code Changes: Schmid, Fabian [fschmid]
Person to be contacted in case of questions about the feature or for funding offers: Schmid, Fabian [fschmid]
If this request is related to multiple components, please list both authorities for all related components.
4.2 Technical Aspects
None
4.3 Privacy
No new personal data is collected or processed as a result of the implementation of the feature.
4.4 Security
The implementation of the feature does not introduce any new attack vectors. there are no further special security-related considerations to be made.
4.5 Contact
Person to be contacted in case of questions about the feature or for funding offers: {Please add related profile link of this person}
4.6 Funding
Funding status and funding parties are listed in the block 'Status of Feature' in the right column of this page.
Funding is still required for this feature. Information on the implementation costs can be found here:
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: 7. Oct 2025, 11:40, Schmid, Fabian [fschmid]