Separating administration nodes for MathJax and Maps and make it distinct nodes

1 Initial Problem

In the beginning of ILIAS 3 we have introduced an administration node that should contain settings for third-party tools of any kind. For years now, only two tools are managed in this administration node: MathJax support and Maps.

It does not make sense to keep this collection of third-party tools administration if ony two tools have to be addressed. Both tools have also their own Mantis category and Services directory.

2 Conceptual Summary

We want to get rid of this special case and introduce two new administration nodes:

• Administration » Extending ILIAS » Maps
• Administration » Extending ILIAS » MathJax

The existing setting screens are re-used, but both new administration nodes need their proper permission settings:

• Actually existing subtab Maps in Administration » Extending ILIAS » Third Party Software becomes the main tab Settings (of new administration node Maps)
• Actually existing subtab MathJax in Administration » Extending ILIAS » Third Party Software becomes the main tab Settings (of new administration node MathJax)

The existing permissions for "Third Party Software" can be removed and substituted by the following new permissions:

• Maps:
  • Visible: Administration of Maps is visible
  • Read: User has read access to administration of Maps
  • Edit Settings: User can edit settings of Maps administration
  • Change Permissions: User can change permission settings of Maps administration
• MathJax:
  • Visible: Administration of MathJax is visible
  • Read: User has read access to administration of MathJax
  • Edit Settings: User can edit settings of MathJax administration
  • Change Permissions: User can change permission settings of MathJax administration

3 User Interface Modifications

3.1 List of Affected Views

• Administration » Extending ILIAS » Maps
• Administration » Extending ILIAS » MathJax

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

{ If the proposal introduces any completely new user interface elements, you might consult UI Kitchen Sink in order to find the necessary information to propose new UI-Concepts. Note that any maintainer might gladly assist you with this. }

3.4 Accessibility Implications

{ If the proposal contains potential accessibility issues that are neither covered by existing UI components nor clarified by guidelines, please list them here. For every potential issue please either propose a solution or write down a short risk assessment about potential fallout if there would be no solution for the issue. }

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

{ 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 Security

{ Does the feature include any special security relevant changes, e.g. the introducion of new endpoints or other new possible attack vectors. If yes, please explain these implications and include a commitment to deliver a written security concept as part of the feature development. This concept will need an additional approvement by the JourFixe. }

7 Contact

• Author of the Request: Kunkel, Matthias [mkunkel]
• Maintainer: Klees, Richard [rklees] for Maps and Neumann, Fred [fneumann] for MathJax
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

8 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• ILIAS.nrw

9 Discussion

Kunkel, Matthias [mkunkel], 06 MAR 2022 : When Maps becomes a proper administration node we can think about re-arranging the settings screen for Maps. This is currently made to handle both supported Maps services. Maybe distinct settings screens for Open Layers Maps and Google Maps are a better option.

Grotz, Kendra [kgrotz], 24 JAN 2023: Just adding the initial Mantis Report here: Admin node „Third Party Software“ should be two separate nodes: MathJax and Maps.
Also, after yesterday's JF it seems there is now a third third-party tool on the horizon: Implement WOPI for File-Editing - should probably then be taken into account here.

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