mirror of
https://github.com/alanorth/cgspace-notes.git
synced 2024-11-22 14:45:03 +01:00
Update notes for 2018-05-16
This commit is contained in:
parent
b1eec8b91c
commit
e3e3a17941
@ -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
|
- 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
|
- 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
|
- 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
|
||||||
|
@ -27,7 +27,7 @@ Also, I switched it to use OpenJDK instead of Oracle Java, as well as re-worked
|
|||||||
|
|
||||||
<meta property="article:published_time" content="2018-05-01T16:43:54+03:00"/>
|
<meta property="article:published_time" content="2018-05-01T16:43:54+03:00"/>
|
||||||
|
|
||||||
<meta property="article:modified_time" content="2018-05-15T18:16:33+03:00"/>
|
<meta property="article:modified_time" content="2018-05-16T14:17:54+03:00"/>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -65,9 +65,9 @@ Also, I switched it to use OpenJDK instead of Oracle Java, as well as re-worked
|
|||||||
"@type": "BlogPosting",
|
"@type": "BlogPosting",
|
||||||
"headline": "May, 2018",
|
"headline": "May, 2018",
|
||||||
"url": "https://alanorth.github.io/cgspace-notes/2018-05/",
|
"url": "https://alanorth.github.io/cgspace-notes/2018-05/",
|
||||||
"wordCount": "1945",
|
"wordCount": "2081",
|
||||||
"datePublished": "2018-05-01T16:43:54+03:00",
|
"datePublished": "2018-05-01T16:43:54+03:00",
|
||||||
"dateModified": "2018-05-15T18:16:33+03:00",
|
"dateModified": "2018-05-16T14:17:54+03:00",
|
||||||
"author": {
|
"author": {
|
||||||
"@type": "Person",
|
"@type": "Person",
|
||||||
"name": "Alan Orth"
|
"name": "Alan Orth"
|
||||||
@ -439,6 +439,20 @@ $ curl -X POST -H 'Content-type:application/json' --data-binary '{"add-fiel
|
|||||||
<li>As the only personally identifiable information we send is the user’s IP address, I think we only need to enable <a href="https://support.google.com/analytics/answer/2763052">IP Address Anonymization</a> in our <code>analytics.js</code> code snippets</li>
|
<li>As the only personally identifiable information we send is the user’s IP address, I think we only need to enable <a href="https://support.google.com/analytics/answer/2763052">IP Address Anonymization</a> in our <code>analytics.js</code> code snippets</li>
|
||||||
<li>Then we can add a “Privacy” page to CGSpace that makes all of this clear</li>
|
<li>Then we can add a “Privacy” page to CGSpace that makes all of this clear</li>
|
||||||
</ul></li>
|
</ul></li>
|
||||||
|
<li>Silvia asked if I could sort the records in her Listings and Report output and it turns out that the options are misconfigured in <code>dspace/config/modules/atmire-listings-and-reports.cfg</code></li>
|
||||||
|
<li>I created and merged a pull request to fix the sorting issue in Listings and Reports (<a href="https://github.com/ilri/DSpace/pull/374">#374</a>)</li>
|
||||||
|
<li>Regarding the IP Address Anonymization for GDPR, I ammended the Google Analytics snippet in <code>page-structure-alterations.xsl</code> to:</li>
|
||||||
|
</ul>
|
||||||
|
|
||||||
|
<pre><code>ga('send', 'pageview', {
|
||||||
|
'anonymizeIp': true
|
||||||
|
});
|
||||||
|
</code></pre>
|
||||||
|
|
||||||
|
<ul>
|
||||||
|
<li>I tested loading a certain page before and after adding this and afterwards I saw that the parameter <code>aip=1</code> was being sent with the analytics response to Google</li>
|
||||||
|
<li>According to the <a href="https://developers.google.com/analytics/devguides/collection/analyticsjs/field-reference#anonymizeIp">analytics.js protocol parameter documentation</a> this means that IPs are being anonymized</li>
|
||||||
|
<li>After finding and fixing some duplicates in IITA’s <code>IITA_April_27</code> test collection on DSpace Test (<sup>10568</sup>⁄<sub>92703</sub>) I told Sisay that he can move them to IITA’s Journal Articles collection on CGSpace</li>
|
||||||
</ul>
|
</ul>
|
||||||
|
|
||||||
|
|
||||||
|
@ -4,7 +4,7 @@
|
|||||||
|
|
||||||
<url>
|
<url>
|
||||||
<loc>https://alanorth.github.io/cgspace-notes/2018-05/</loc>
|
<loc>https://alanorth.github.io/cgspace-notes/2018-05/</loc>
|
||||||
<lastmod>2018-05-15T18:16:33+03:00</lastmod>
|
<lastmod>2018-05-16T14:17:54+03:00</lastmod>
|
||||||
</url>
|
</url>
|
||||||
|
|
||||||
<url>
|
<url>
|
||||||
@ -164,7 +164,7 @@
|
|||||||
|
|
||||||
<url>
|
<url>
|
||||||
<loc>https://alanorth.github.io/cgspace-notes/</loc>
|
<loc>https://alanorth.github.io/cgspace-notes/</loc>
|
||||||
<lastmod>2018-05-15T18:16:33+03:00</lastmod>
|
<lastmod>2018-05-16T14:17:54+03:00</lastmod>
|
||||||
<priority>0</priority>
|
<priority>0</priority>
|
||||||
</url>
|
</url>
|
||||||
|
|
||||||
@ -175,7 +175,7 @@
|
|||||||
|
|
||||||
<url>
|
<url>
|
||||||
<loc>https://alanorth.github.io/cgspace-notes/tags/notes/</loc>
|
<loc>https://alanorth.github.io/cgspace-notes/tags/notes/</loc>
|
||||||
<lastmod>2018-05-15T18:16:33+03:00</lastmod>
|
<lastmod>2018-05-16T14:17:54+03:00</lastmod>
|
||||||
<priority>0</priority>
|
<priority>0</priority>
|
||||||
</url>
|
</url>
|
||||||
|
|
||||||
@ -187,13 +187,13 @@
|
|||||||
|
|
||||||
<url>
|
<url>
|
||||||
<loc>https://alanorth.github.io/cgspace-notes/posts/</loc>
|
<loc>https://alanorth.github.io/cgspace-notes/posts/</loc>
|
||||||
<lastmod>2018-05-15T18:16:33+03:00</lastmod>
|
<lastmod>2018-05-16T14:17:54+03:00</lastmod>
|
||||||
<priority>0</priority>
|
<priority>0</priority>
|
||||||
</url>
|
</url>
|
||||||
|
|
||||||
<url>
|
<url>
|
||||||
<loc>https://alanorth.github.io/cgspace-notes/tags/</loc>
|
<loc>https://alanorth.github.io/cgspace-notes/tags/</loc>
|
||||||
<lastmod>2018-05-15T18:16:33+03:00</lastmod>
|
<lastmod>2018-05-16T14:17:54+03:00</lastmod>
|
||||||
<priority>0</priority>
|
<priority>0</priority>
|
||||||
</url>
|
</url>
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user