QuILT-GDPR

A Miau Wiki wikiből
QuILT-sitemap: https://miau.my-x.hu/mediawiki/index.php/QuILT-content

Recommendations, how rules could be designed and customized:

Please, give your statements about GDPR-relevant parameters concerning the handling rules of your data asset collected before/during the course!

Case A: anonymized objects (persons)

Collecting data

Do you want to be anonymized during the whole course? 

(yes – it means: you may never use your name in any layers of the data collection)

Handling data

Are you understanding that anonymized data should not be protected anyway? 

(yes)

Case B: non-anonymized objects (persons)

Collecting data

Do you want to be yourself during the whole course? 

(yes – it means, you should always use your name in all layers you may manage them)

Layers of data collecting

MIAU-WIKI articles/discussion pages with logs 

(yes/no)

Emails 

(yes/no)

Documents like DOC, XLS, PPT 

(yes for all types or separately for DOC-XLS-PPT / no for all or separately for DOC-XLS-PPT)

Questionnaires 

(yes/no)

Dashboards like PLA/midterm/final 

(yes for all types or separately for each type /no for all or separately for each type)

Other:..................... 

(recommendations for this layer should be send from Students as far as possible)

Frequency of data collecting

  • Each saving will be stored and becomes always visible for ever.
  • Previews will not be stored.
  • These parameters can not be changed.

Handling data

Are you understanding that personalized data may be protected according to all of their characteristics? 

(yes – it means, you can change your name to anonymous in the layers you may manage them – but the copies about your personalized documents till changing can be used by others unlimited also in the future)

Layers of data handling

Are agreeing, that data may be counted? (e.g. the sum of happenings may be visualized like amount of logins)

(yes/no)

Are agreeing, that averages may be built? (e.g. the average of happenings may be visualized like average time being logged in)

(yes/no)

Are agreeing, that data may be used for benchmarking? (e.g. the realtions of happenings may be visualized like ranks of persons according to each attribute)

(yes/no)

Are agreeing, that data may be used for forecasting? (e.g. the expected values of happenings may be visualized like timestamp of the next login or duration of the next session)

(yes/no)

Are agreeing, that data may be used for profiling? (e.g. the index of aggregated happenings may be visualized like effectiveness of activities where the more is the effectiveness the less deleting will be made, or the more amount of characters being typed, or the more specific characters like .,-!? got used, etc.)

(yes/no)

Frequency of data collecting

  • Each saving will be stored and becomes always visible for ever.
  • Previews will not be stored.
  • These parameters can not be changed.


Everybody may offer new description layers/questions and/or fine tune the above mentioned initial interpretations!