JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for DATA-PROTECTION Archives


DATA-PROTECTION Archives

DATA-PROTECTION Archives


data-protection@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

DATA-PROTECTION Home

DATA-PROTECTION Home

DATA-PROTECTION  2001

DATA-PROTECTION 2001

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Mirroring of discussion list archives (long)

From:

Chris Evans <[log in to unmask]>

Reply-To:

Chris Evans <[log in to unmask]>

Date:

Mon, 29 Jan 2001 00:25:17 -0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (90 lines)

> 1) I certainly think that anyone who operates a list server
> where the list archive is available on a public Web site
> needs to ensure that anyone who subscribes is aware of the
> implications of this.  Some might argue that JISCmail has not
> done enough on this front (nor mailbase before it).  As a list
> owner I can change the welcome message to highligiht this
> issue, but I think it should be down to the operator of the
> list server system to inform users of this.  After all, this
> is the Data Controller in this instance, yes?

This raises an issue that is of interest to me in another setting and it
concerns the specificity of the determination of the use of the data.
I can see an argument that Jismail and mailbase merely offer so
generic a level of use of the data that they are data processors for
the list owners, who (attempt to) determine the specific use of the
data.  I think this issue overlaps with, but is actually rather distinct
from, the issue of the nature of the data, e.g. Email addresses,
necessary only for transfer cf. message contents...

My example is different but may help make the distinction.  I am part
of a research group who process data for many psychotherapy and
counselling services.  The data that reaches us is anonymised and
nothing in it or anything else we see can unanonymise it.  However,
the services who supply the data, probably can unanonymise it
unless they have taken the rather remarkable, and almost technically
impossible/implausible, decision to throw away any linking info.

Now we set a general spec. for the analyses we return to the
services.  We might, probably will, also sometimes do specific
extensions either because we can see it would make the analyses
more useful, or because services request such extensions.

We also, by agreement with the services and to everyone's
"scientific" benefit, from time to time run analyses on either the
whole accumulating dataset or subsets of it.  Those are mainly, but
may not only be, psychometric.  We determine those and the results
go into the "scientific" literature, i.e. the public domain, though never
with individual data and never, that we can see, with identifiable
service level aggregates (yet).

We also give the raw data in electronic form back to the services
and they may do various sensible analyses for their local needs
where they have the skills on hand.  Those analyses might be
automated but some might also be detailed case discussions of
outliers (i.e. quite specific to a named individual and drawing in data
way above and beyond the anonymised data processed by us).

Now my view is:
a) That we are data controllers in relation to the group summary
analyses sent back to the services and the specifics we do above
and beyond those. (Or, more strictly, the data are simply not within
the remit of the DPA as they don't seem to be "personal data", but
that only dodges rather than answering what seems to me to be an
interesting question!)
b) If we work with an individual service to come up with additional
analyses, we and they are joint controllers?  How do you work out
the balance, often they might say what they want and we might
advise on the statistical and psychometric analyses that seem most
apt.
c) Where they do analyses on the data we send back to them, they
are data controllers.

I _think_ that's sensible. Now for me it illustrates some of the
problems of the DPA coming off the rails with the best of intentions,
because I think that the complexity of explaining all that so there
could be fully informed consent, is way into "disproportionate".

(I know I've tilted this a bit as the true anonymisation of the data that
reach us do seem to put that layer outside DPA ... but the issue
seems to arise for the Jismail situation.)

Any thoughts anyone?

TIA,

Chris

P.S. Please note that the role in which I do this work is not, directly,
one arising from any of the three (!) jobs shown in my signature
though I suspect similar issues are faced in those august bodies or
will be some day!

Chris Evans <[log in to unmask] or [log in to unmask]>
Consultant Psychiatrist in Psychotherapy,
Rampton Hospital; Associate R&D Director,
Tavistock & Portman NHS Trust;
Hon. SL Institute of Psychiatry
*** My views are my own and not representative
of those institutions ***

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
2006
2005
2004
2003
2002
2001
2000
1999
1998


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager