Feature Wiki
Tabs
Copyright as Page Editor Component
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 the copyright of an object is only displayed on its Info-tab, and its Metadata-tab. Only the former is available to users without 'Edit Settings' permission. This leads to authors inserting copyright information manually into the content of objects and not into the object's LOM, circumventing all of the OER infrastructure in ILIAS.
2 Conceptual Summary
The page editor offers a 'Copyright Information of Repository Object' component. It displays the copyright information of the current object as it would be on the object's info page. No further configuration is offered.
The component should always display the copyright information of the overarching repository object, and not potential subobjects. For example, on a page in a Learning Module the copyright information of the Learning Module will be shown, and not that of the page. This will make the behavior of the component clearer.
Outside of the context of objects with LOM support, for example on the content page of a Category or in a Portfolio, the component should not be offered at all. The component should also not be offered if copyright selection is not enabled on the installation.
3 User Interface Modifications
3.1 List of Affected Views
- Content pages in the context of repository objects with LOM support:
- Blog Posting
- Wiki Page
- Glossary
- Course/Group Page
- Course/Group Start Object Page
- Content Page Object
- ILIAS Learning Module
- Learning Sequence Intro and Outro Page
3.2 User Interface Details
When and where appropriate, "Insert Copyright Information of Repository Object" is offered in the Page Editor.
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: Meyer, Stefan [smeyer] and Schmitz, Tim [tschmitz]
- Authority to Sign off Code Changes: Meyer, Stefan [smeyer] and Schmitz, Tim [tschmitz]
If this request is related to multiple components, please list both authorities for all related components.
4.2 Technical Aspects
The Metadata component will provide the page editor component as ilPageContent. The component will only be available where it is actively enabled via ilPageConfig::setEnablePCType in the corresponding ilPageConfig.
When other components enable LOM, and also use the page editor, the component has to be enabled via their ilPageConfig. This will be documented in the enabling_lom.md in the Metadata documentation.
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
Kunkel, Matthias [mkunkel], 13 OCT 2026: Thanks for this feature request. I have two questions:
- I assume that „in the same form as it is shown e.g. on the Info Screen“ means that there is no option to modify its look with a content style, e.g. by giving all copyright information a background or a frame within this content style, right? Or in other words this page element is not controlled by the content style, right?
- If a new object type with page editor support gets LOM support, too – what does a developer has to take into consideration to offer this page component? Or does it appear automatically in the list of supported page components?
Schmitz, Tim [tschmitz], 14 OCT 2026: Thank you for the questions:
- Correct, the component will not be stylable via the content style. The presentation of copyright should be consistent across ILIAS.
- For new usages of the component, it has to be enabled manually in the corresponding ilPageConfig. I'll document that in the "Enabling LOM" guide.
I have also added this information to the article above.
Kruse, Fabian [Fabian], 19.10.2026: I appreciate this feature, but the wording "Insert Copyright Information of Repository Object" is quite long for this menu. Would "Insert Copyright Information" suffice?
JourFixe, ILIAS [jourfixe], 19 OCT 2026: We highly appreciate this suggestion and accept the feature for trunk.
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: 19. Oct 2026, 15:41, Kunkel, Matthias [mkunkel]

