My previous posts have focused on the forthcoming Y3 Design Conference of the Learning Layers (LL) project. In the first post I compared the situation of the project before the Y1 Design conference (two years ago) and before the Y3 Design Conference (currently). In the second post I gave an overview how we have been working with the Learning Toolbox (LTB). This third post focuses (with reference to the LTB) to a general issue for the whole LL project and for all pilot activities. In English there several parallel concepts that refer to this problem context – data protection, data privacy, confidentiality …. I German this is all covered with one word: “Datenschutz”.
When discussing the next steps in the piloting with the Learning Toolbox we noticed that we do not have a coherent policy for Datenschutz. In this respect I wrote the following paragraph in the input on LTB to a wiki page of the LL Design Conference:
” (…) we need to develop a clear policy for data protection/ data security (Datenschutz) that covers the Layers Box (LB), the Learning Toolbox (LTB), the social semantic server (SSS) and linked platforms (Baubildung.net). Firstly, we need urgently a brief Users’ Guide for the pilot phase. This is necessary to assure our pilot partners that they have control of their own data when using the LL tools and related services. Secondly, we need to develop the policy for the continuation phase beyond the funding period of the LL project. This is an essential element of the exploitation plans.”
As a response to this apparent need Graham Attwell started looking for documents that could be helpful for us. We all agreed that we need to pay attention to the legal aspects (with sufficiently detailed documents) but we also need to prepare short user-friendly documents that we can use with our pilot partners. From this perspective we started looking at the Datenschutz policy documents of FutureLearn (a consortium of British universities that organises MOOCs). FutureLearn has developed the following set of documents:
- Terms – the overarching framework agreement that covers in detail all possible policy issues.
- Openness – A short list of openness principles.
- Cookies – Policy for using different type of cookies.
- Accessibility – Accessibility policy (including the responsibilities of different parties).
- Code of Conduct – A short list of principles as the commitments of users to which they agree when signing up.
- Data protection – A short document declaring the policy for data control, data collection and responsibilities of different parties.
We are most certainly aware of the fact that the policies of a provider of MOOCs are different from the ones that the LL project needs to develop. So, there is no prospect for easy one-to-one translations. BUT what inspires us is the nicely differentiated set of coherent documents – some for ordinary users, some for experts – within a common framework. Also, what inspires us, is the fact that FutureLearn – like the LL project – is committed to Open Source software. So, there is a lot in common to work with.
More blogs to come …