Feature Wiki
Tabs
improve visibility of certificates
Page Overview
[Hide]If you need any help in filling out this wiki page, please visit our ILIAS Community FAQ. And please complete the metadata information in the right column after having created the page.
1 Initial Problem
Currently, certificates are awarded when certain learning materials are passed (such as a whole course or a test/an exercise). At the moment there are different solutions in ilias to visalize the moment when the user gets his/her certificate depending on the objects that awards the certificate.
- If you get your certificate in a course, there will be a little icon next to the action menu.
- If you get your certificate in a test, there will be a button "certificate" on the results view.
2 Conceptual Summary
We propose to introducde a pop-over solution which works like the badges in ILIAS.
- If a user gets a certificate, there will be a pop-over notification, which signalizes that that a certificate was awarded. This pop-up solution should be active as soon as the certificate service is activated.
- Problem and proposal for a little expansion: The pop-over notification (which is used for the badges) is actually displayed too short. The pop-over notification is supposed to be closed by the user through the little x-button, and does not disappear without any action of the user.
- Secondly, ILIAS should send an e-mail automatically when a user gets the certificate (as it is the case when working with badges). This message also includes a link to the learning achivements side.
- What happens on the mobile screen? On the mobile screen there is the same behavior as on full screen.
3 User Interface Modifications
3.1 List of Affected Views
1. First of all, we need the pop-over notification visualized in the style of the certificate. This mockup could show this:
![](./data/docu/mobs/mm_72968/Mockup_Pop-over.png?il_wac_token=12e880fc1cc798bc01bcf5bd5e9cf791a4f0cb64&il_wac_ttl=5&il_wac_ts=1725755558)
2. Secondly, this notification should be shown on the same place, like the pop-over notification from the badges. If there are two notifications at the same time, they will be presented successively.
A. Solution for ILIAS Version 5.4
- the pop-over signalizes for the users, that they got a certificate.
- the pop-over must be closed via the little x-button.
![](./data/docu/mobs/mm_72970/Badge_erhalten.png?il_wac_token=12e880fc1cc798bc01bcf5bd5e9cf791a4f0cb64&il_wac_ttl=5&il_wac_ts=1725755558)
A.1 Solution for ILIAS Version 5.4
- as soon as the pop-over is closed by the user, the little certificate icon will be shown as before.
![](./data/docu/mobs/mm_72980/Mockup_Icon_Zertifikat.png?il_wac_token=12e880fc1cc798bc01bcf5bd5e9cf791a4f0cb64&il_wac_ttl=5&il_wac_ts=1725755558)
B. Solution for ILIAS Version 6.0/7.0
- the pop-over signalizes for the users, that they got a certificate.
- the pop-over must be closed via the little x-button.
![](./data/docu/mobs/mm_72977/Mockup_Zertifikat_6.0.png?il_wac_token=12e880fc1cc798bc01bcf5bd5e9cf791a4f0cb64&il_wac_ttl=5&il_wac_ts=1725755558)
B.1 Solution for ILIAS Version 6.0/7.0
- if the pop-over is closed by the user there is no little icon next to the action-menue anymore but the signal in the notification center that will show up.
- After this, the user is able to open the notification center and get access to the certificate on this way.
![](./data/docu/mobs/mm_72981/Mockup_Notification_Center.png?il_wac_token=12e880fc1cc798bc01bcf5bd5e9cf791a4f0cb64&il_wac_ttl=5&il_wac_ts=1725755558)
3.2 User Interface Details
1. We need a pop-over for the certificate.
2. Change in behavior: the pop-over will be shown as long as the user doesn´t close the pop-over with the help of the little x-button.
![](./data/docu/mobs/mm_72968/Mockup_Pop-over.png?il_wac_token=12e880fc1cc798bc01bcf5bd5e9cf791a4f0cb64&il_wac_ttl=5&il_wac_ts=1725755558)
3.3 New User Interface Concepts
4 Technical Information
{The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues.}
5 Privacy Information
{ Please list all personal data that will need to be stored or processed to implement this feature. For each date give a short explanation why it is necessary to use that date. }
6 Contact
- Author of the Request: {Please add your name.}
- Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
- Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}
7 Funding
If you are interest in funding this feature, please add your name and institution to this list.
- …
8 Discussion
9 Implementation
{The maintainer has to give a description of the final implementation and add screenshots if possible.}
Test Cases
Test cases completed at {date} by {user}
- {Test case number linked to Testrail} : {test case title}
Approval
Approved at {date} by {user}.
Last edited: 22. Sep 2020, 15:18, Kunkel, Elena Charlotte [elena]