Preparing ILIAS for the General Data Protection Regulation (GDPR)

1 Initial Problem

The General Data Protection Regulation (GDPR) (Regulation (EU) 2016/679) is a regulation by which the European Parliament, the Council of the European Union and the European Commission intend to strengthen and unify data protection for all individuals within the European Union (EU). It also addresses the export of personal data outside the EU. The GDPR aims primarily to give control back to citizens and residents over their personal data and to simplify the regulatory environment for international business by unifying the regulation within the EU. […] The regulation was adopted on 27 April 2016. It becomes enforceable from 25 May 2018 after a two-year transition period and, unlike a directive, it does not require national governments to pass any enabling legislation, and is thus directly binding and applicable.

Source: Wikipedia

This regulation will have potentially far-reaching consequences for every institution using (something like) ILIAS. Among other things it might mandate technical measures, eg. the possibility for endusers to access the data an ILIAS installation accumulated about them at the push of button and/or perhaps a standardized (technical) interface to access/export that data, too.

To date, at least at the time of the initial creation of this feature wiki entry (16.01.2018) this developement has not been widely discussed within the ILIAS community (even though the “two-year transition period” is almost over). IANAL, so preliminary this entry is merely meant as a kind of “scaffolding” and has to be fleshed out in a community effort. Ie. help with extending and substantiating this entry is wanted, needed and will very much be welcomed.

Also not: Since we are ”quite late to the game” it might not be enough to rush measures for ILIAS 5.4 anymore. At the very least some “bugfixing” might become imperative, too. (Again, IANAL …!)

This (at least) concerns all institutions using ILIAS within the EU.

2 Conceptual Summary

Things that might need to be done on the technical side …

• Like eg. Facebook will probably have to offer an easily accessible, human-readable export of all user data (per user) at the push of a button (see example screenshots).

  

  

• (Please help extend this list …!)

3 User Interface Modifications

3.1 List of Affected Views

(Tbd.)

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

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 Contact

6 Funding

7 Discussion

8 Implementation

{The maintainer has to give a description of the final implementation and add screenshots if possible.}

Test Cases

Approval

Approved at {date} by {user}.