[PUBLIC] Empowering Data Citizens: Platform requirements table
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

View only
 
 
ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
Note: This table summarises the user-specific questions, needs, as well as technical and procedural requirements for the end-to-end workflow and metadata framework. Through the end-to-end workflow, data is being transferred between different systems and user groups. This table describes which concerns and needs as well as responding requirements need to be met to support data transfers through the end-to-end workflow in a sustainable fashion.
2
3
Which is the sphere of data transfer?Between which systems/actors does the data transfer occur?Which systems/actors are directly or indirectly involved in the data exchange?Which questions concern the involved actors in the specifc phase of data exchanges?Which system or procedural needs do users have?Which requirements result from this, particularly with regard to platform functionalities and metadata descriptions?
4
closed data -> shared dataMobileMiner -> openPDS (backend)Smartphone userHow will my data be stored on the openPDS platform?
How can third parties access my data?
Which third parties can access my data?
For what purposes can third parties access my data?
user needs to know under which conditions data can be stored in the openPDS backend;
user needs to be informed about in which ways data can be reused by third parties
- Terms and Conditions from openPDS-based intermediary;
- data storage platform needs a system which enables users to (dis-)close individual data types;
- openPDS needs a function to informs data users which third party users and data aggregators get access to openPDS and for which indicated purposes
5
closed data -> shared dataMobileMiner -> openPDS (backend)openPDSHow can user data be stored on the openPDS platform backend?
Which data can be shared with trusted third parties and data aggregators?
How and under which conditions was the data collected?
platform needs to have clarified terms under which data is being stored in the openPDS backend;
platform needs to have a clear user guidance on where data can shared with trusted third parties or data aggregators;
platform needs to know which are the conditions under which the data was collected, in order to understand limitations of the data and potential utility limitations
- Terms and Conditions for data storage in openPDS backend need to be clear to regulate data storage;
- platform needs a system to inform users about conditions of data sharing and to enable them to opt-in to sharing with trusted third parties or data aggregators;
- platforms needs to create metadata about how the data was created and processed
6
shared data (openPDS) -> shared data (third party users)openPDS (frontend) -> trusted third partiesopenPDSWhich trusted third parties request access to openPDS's data?
For which purposes do trusted third parties request access to user data?
Which analyses do third party users envision/plan?
Which are the general usage terms of the data access front-end?
needs to know the purposes for which the data is being accessed and analysed (e.g. specifics of individual studies, planned exploitation of results);
usage terms need to be clarified with third parties
- openPDS needs specific Terms and Conditions for data access front-end;
- openPDS needs a system to record information about trusted third parties and for which specific purposes and analyses they request access to the data;
- openPDS needs an application and user access system to control data queries by trusted third parties;
7
shared data (openPDS) -> shared data (third party users)openPDS (frontend) -> trusted third partiestrusted third partiesUnder what conditions can we access the data?
How can we analyse and reuse the data?
Which data can we access?
Which information is contained in the data?
Under what conditions has the data been collected?
need to know how data was generated, what it contains, and how it can be reused (i.e. licensing restrictions; ethical guidance on data usage; etc.)- openPDS needs Terms and Conditions for front-end data access;
- openPDS data needs a license to regulate reuse conditions;
- openPDS needs to create administrative, descriptive and structural metadata which give contextual background information and reuse guidance to third party users
8
shared data (openPDS) -> shared data (third party users)openPDS (frontend) -> trusted third partiessmartphone user (indirect information needs)Who is requesting access to user data?
How often has the data been queried by third party users?
Which type of queries have been run against the data?
needs to know what purposes the data will generally be used for in order to decide whether data should be available (e.g. linking with other data; inclusion in certain services; etc.);
potentially needs to know about specific users of data as well;
might want to have at least an ex-post control
- ideally, openPDS would have a tracking system to enable smartphone users to see who has been querying their data how often and through which kind of queries -> this would allow users to monitor third party compliance with the conditions under which data access was granted
9
shared data (openPDS) -> shared data (third party users)openPDS (frontend) -> data aggregatorsopenPDSUnder which terms and conditions can the data be aggregated?
How will the data be aggregated?
What steps and techiques are used to ensure privacy of individual smartphone users?
For which purposes and audiences will the open data be generated?
needs to know the purposes for which the data is being accessed and aggregated (e.g. specifics of data audience);
needs to know about aggregation and anonymisation steps which will be undertaken by the data aggregators;
usage terms and conditions need to be clarified with data aggregators
- openPDS needs Terms and Conditions for data access through data aggregators;
- openPDS needs a system to ensure that tracks information on how the data will be aggregated, anonymised and which audiences will mainly be targeted by the data publication
10
shared data (openPDS) -> shared data (third party users)openPDS (frontend) -> data aggregatorsdata aggregatorsUnder what conditions can we access the data?
How are we allowed to analyse and aggregate the data?
Which data can we access?
Which information is contained in the data?
Under what conditions has the data been collected?
need to know how data was collected, what information it essentially contains, and what the expectations are regarding reuse and privacy (thus informing data aggregation, anonymisation and creation of metadata on ethical usage of data);
needs to know which data has been identified by users as "private" or "publishable"
- Terms and Conditions for front-end data access (specific to data aggregators);
- administrative metadata to guide the aggregation and privatisation of metadata;
- openPDS data needs a license to regulate data aggregation conditions;
- openPDS needs to create administrative, descriptive and structural metadata which give contextual background information and reuse guidance to data aggregators
11
shared data (openPDS) -> shared data (third party users)openPDS (frontend) -> data aggregatorssmartphone user (indirect information needs)Who is requesting access as a data aggregator?
How will the data be queried, aggregated and anonymised?
For which primary purposes and audiences is the dataset being created?
needs to know about data usage plans (i.e. intended audiences, aggregation and anonymisation steps, background of data aggregators);- openPDS would ideally need a monitoring channel to inform users about current aggregator queries;
- ideally, openPDS would have a tracking system to enable smartphone users to see who has been querying their data how and which open datasets have been created from the data -> this would allow users to monitor third party compliance with the conditions under which data access was granted
12
shared data (data aggregators) -> open datadata aggregators -> open data usersdata aggregators- no downstream information concerns -
13
shared data (data aggregators) -> open datadata aggregators -> open data usersopen data usersHow has the data been processed (especially re. aggregation and anonymisation)?
How is the dataset constructed?
What geographic and demographic coverage does the dataset have?
What finformation does the dataset contain?
Under what conditions can the open data set be used?
need to know about what data is covered by the aggregate dataset (i.e. information on what was the original data base, info on aggregation and anonymisation actions performed, needs metadata on how data should be used...)- datasets need rich metadata descriptions, particularly regarding provenance, contained information, as well as descriptive and structural metadata
- needs a metadata description to guide ethical data usage;
- datasets need a licence attached (specifying attribution and share-alike conditions)
14
shared data (data aggregators) -> open datadata aggregators -> open data userssmartphone user (indirect information needs)How has the data been reused?-- ideally would need to be informed about how the open data sets have been reused (in order to showcase impacts etc.) --Ideally, data aggregators would publish examples of how the data has been reused
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
Loading...