Update notes for 2018-05-16

content/posts/2018-05.md

@@ -259,3 +259,16 @@ $ curl -X POST -H 'Content-type:application/json' --data-binary '{"add-field": {
   - We use Google Analytics to track website usage, which makes Google the "Data Processor" and in this case we merely need to *limit* or *obfuscate* the information we send to them
   - As the only personally identifiable information we send is the user's IP address, I think we only need to enable [IP Address Anonymization](https://support.google.com/analytics/answer/2763052) in our `analytics.js` code snippets
   - Then we can add a "Privacy" page to CGSpace that makes all of this clear
+- Silvia asked if I could sort the records in her Listings and Report output and it turns out that the options are misconfigured in `dspace/config/modules/atmire-listings-and-reports.cfg`
+- I created and merged a pull request to fix the sorting issue in Listings and Reports ([#374](https://github.com/ilri/DSpace/pull/374))
+- Regarding the IP Address Anonymization for GDPR, I ammended the Google Analytics snippet in `page-structure-alterations.xsl` to:
+
+```
+ga('send', 'pageview', {
+  'anonymizeIp': true
+});
+```
+
+- I tested loading a certain page before and after adding this and afterwards I saw that the parameter `aip=1` was being sent with the analytics response to Google
+- According to the [analytics.js protocol parameter documentation](https://developers.google.com/analytics/devguides/collection/analyticsjs/field-reference#anonymizeIp) this means that IPs are being anonymized
+- After finding and fixing some duplicates in IITA's `IITA_April_27` test collection on DSpace Test (10568/92703) I told Sisay that he can move them to IITA's Journal Articles collection on CGSpace