EPrints Technical Mailing List Archive

See the EPrints wiki for instructions on how to join this mailing list and related information.

Message: #08296

< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

Re: [EP-tech] GDPR issue: replace_core (to set export_as_xml => 0) no longer effective for contact_email in v3.4+?

  • To: <eprints-tech@ecs.soton.ac.uk>
  • Subject: Re: [EP-tech] GDPR issue: replace_core (to set export_as_xml => 0) no longer effective for contact_email in v3.4+?
  • From: David R Newman <drn@ecs.soton.ac.uk>
  • Date: Wed, 19 Aug 2020 17:19:39 +0100
Hi Florian,
You will need to copy flavours/pub_lib/cfg.d/eprint_fields_common.pl to your archive cfg/cfg.d/ directory and set the export_as_xml => 0 in this newly created file.
I agree we should probably not have this field exporting by default, although it is the sort of fields that would typically be required in internal (authenticated) exports.  I have created a GitHub issue for this: 

https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Feprints%2Feprints3.4%2Fissues%2F91&amp;data=01%7C01%7C%7C8348c5fdc2614e08ea6c08d8445bad11%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=y6vkEfJisYuFOhsRwVjmvpaESqQfaYnlxeqt5MXisgI%3D&amp;reserved=0

I think chan

Regards

David Newman

On 19/08/2020 16:56, Florian Heß via Eprints-tech wrote:

Hi,

we blocked privacy sensitive contact_email from being propagated by some
plugins linked in the summary page. That no longer works in a simple
manner in 3.4+, because replace_core field setting takes effect only for
core fields ("provenance" => "core"), but contact_email now is defined
in pub_lib/cfg.d/eprint_fields_common.pl which is why "provenance" is
set to "config".

When I try to set export_as_xml => 0 for the fields, EPrints throws an
error because of duplicate field eprint.contact_email.

The flag export_as_xml is evaluated in Plugins CSV and JSON and Simple.
Lacking an idea for a better solution, I will now hack the
eprint_fields_common.pl file in a way that is probably not update-safe.

I am afraid this needs to be done to make EPrints 3.4+ (closer to) GDPR
compliant, does it?


Viele Grüße
Florian



--
This email has been checked for viruses by AVG.
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.avg.com%2F&amp;data=01%7C01%7C%7C8348c5fdc2614e08ea6c08d8445bad11%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=yqyL3xczS2tmVOc2C4YHajmW%2F01PrDVZ6wp3anxKKCE%3D&amp;reserved=0