25. Internationale ILIAS-Konferenz

Jetzt Tickets sichern / Order Tickets now!

Feature Wiki

Information about planned and released features

Tabs

Data Collection : Printable Single View

Page Overview

[Hide]

1 Initial Problem

Recurrently, we receive requests for the ability to print individual data collection entries from their single-view.Currently, this can only be done via the browser itself, but this results in unwanted elements of the page being included. Furthermore, using the browser’s own print dialogue is not considered very intuitive – users would much rather expect an option within ILIAS itself.

2 Conceptual Summary

For single views of data collection entries, it should be possible to generate a printout or PDF directly, similar to other objects with page editor content (learning modules, portfolio, etc.).

  • The function should be located in the toolbar.
  • The object type icon, the object title, the description and the page content are displayed. (As with other objects)
  • The print function can be enabled and disabled in the view settings. The default setting value is 'disabled'.
    • Note: As not all content is actually suitable for printing or saving as a PDF, this decision should be left entirely to the author of the object. For example, videos and file objects are not suitable.

Screenshot from ILIAS

PDF / Printview

3 User Interface Modifications

3.1 List of Affected Views

  • Single View of a Data Collection Entry
  • 'Settings'-Tab for Views 

3.2 User Interface Details

  • Add a Button 'Print/PDF' in Single View of a Data Collection Entry (See chapter 2)
  • Add a Form Element to activate and deactivate Print Option in 'Settings'-Tab for Views
MockUp of form element to activate and deactivate printable single view

3.3 New User Interface Concepts

None.

3.4 Accessibility Implications

None.

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

Nothing specific.

4.3 Privacy

Nothing specific.

4.4 Security

Nothing specific.

4.5 Contact

Person to be contacted in case of questions about the feature or for funding offers: Samoila, Oliver [oliver.samoila]

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

01 June 2026 Giercke-Ungermann, Annett [Annett_Giercke]

Thank you very much for this feature request. The feature sounds very useful and could improve the usability of data collections in many use cases. In this context, I would like to kindly ask whether the accessibility requirements for the generated PDF documents have already been considered as part of this process.

My concern is that the PDF generation process might produce documents that are visually correct, but may not include sufficient semantic structure. For digital accessibility, elements such as a clear heading hierarchy, correct reading order, structural tags, and appropriate metadata are important.

Thank you very much in advance for your feedback.

01 June 2026, Samoila, Oliver [oliver.samoila]:

Thank you for your question.

This feature uses the same process as other objects that end up using content from the page editor.

Unfortunately, I didn’t have access to a tool such as https://pac.pdf-accessibility.org/de on my Mac. I haven’t been able to identify a suitable tool at such short notice. However, I can certainly do this at a later date.

Regardless of that, we have recently noted that we do not feel responsible for the actual user content and its correct output.
In short, I therefore only recognise the need to deliver the object title and object description correctly.

JourFixe, ILIAS [jourfixe], 01 JUN 2026: We highly appreciate this suggestion and accept it 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}.

Full Screen

Last edited: 1. Jun 2026, 14:14, Kunkel, Matthias [mkunkel]