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

Florian Heß hess at ub.uni-heidelberg.de
Wed Aug 19 16:56:18 BST 2020


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

-- 
UB Heidelberg (Altstadt)
Plöck 107-109, 69117 HD
Abt. Informationstechnik
https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.ub.uni-heidelberg.de%2F&data=01%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7C80cd541dcc8347def27808d844586a27%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=4uakNiKFFnSK3xQn2xAUnh5rGZFvlpXWPg4TVBPdgnk%3D&reserved=0



More information about the Eprints-tech mailing list