Update notes for 2018-05-17

This commit is contained in:
Alan Orth 2018-05-17 18:11:18 +03:00
parent 00dc8241fc
commit 5ac1d88cbf
Signed by: alanorth
GPG Key ID: 0FB860CC9C45B1B9
3 changed files with 18 additions and 8 deletions

View File

@ -287,3 +287,8 @@ ga('send', 'pageview', {
- And actually I'm not entirely sure about the order of filtering before tokenizing, etc...
- Ah, I see that `charFilter` must be before the tokenizer because it works on a stream, whereas `filter` operates on tokenized input so it must come after the tokenizer
- Regarding the use of the `charFilter` vs the `filter` class before and after the tokenizer, respectively, I think it's better to use the `charFilter` to normalize the input stream before tokenizing it as I have no idea what kinda stuff might get removed by the tokenizer
- Skype with Geoffrey from IITA in Nairobi who wants to deposit records to CGSpace via the REST API but I told him that this skips the submission workflows and because we cannot guarantee the data quality we would not allow anyone to use it this way
- I finished making the XMLUI changes for anonymization of IP addresses in Google Analytics and merged the changes to the `5_x-prod` branch ([#375](https://github.com/ilri/DSpace/pull/375)
- Also, I think we might be able to implement [opt-out functionality for Google Analytics using a window property](https://developers.google.com/analytics/devguides/collection/analyticsjs/user-opt-out) that could be managed by [storing its status in a cookie](https://webgilde.com/en/analytics-opt-out/)
- This cookie could be set by a user clicking a link in a privacy policy, for example
- The additional Javascript could be easily added to our existing `googleAnalytics` template in each XMLUI theme

View File

@ -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&#43;03:00"/>
<meta property="article:modified_time" content="2018-05-17T12:37:21&#43;03:00"/>
<meta property="article:modified_time" content="2018-05-17T13:14:29&#43;03:00"/>
@ -65,9 +65,9 @@ Also, I switched it to use OpenJDK instead of Oracle Java, as well as re-worked
"@type": "BlogPosting",
"headline": "May, 2018",
"url": "https://alanorth.github.io/cgspace-notes/2018-05/",
"wordCount": "2313",
"wordCount": "2444",
"datePublished": "2018-05-01T16:43:54&#43;03:00",
"dateModified": "2018-05-17T12:37:21&#43;03:00",
"dateModified": "2018-05-17T13:14:29&#43;03:00",
"author": {
"@type": "Person",
"name": "Alan Orth"
@ -470,6 +470,11 @@ $ ./bin/post -c countries ~/src/git/DSpace/2018-05-10-countries.csv
<li>And actually I&rsquo;m not entirely sure about the order of filtering before tokenizing, etc&hellip;</li>
<li>Ah, I see that <code>charFilter</code> must be before the tokenizer because it works on a stream, whereas <code>filter</code> operates on tokenized input so it must come after the tokenizer</li>
<li>Regarding the use of the <code>charFilter</code> vs the <code>filter</code> class before and after the tokenizer, respectively, I think it&rsquo;s better to use the <code>charFilter</code> to normalize the input stream before tokenizing it as I have no idea what kinda stuff might get removed by the tokenizer</li>
<li>Skype with Geoffrey from IITA in Nairobi who wants to deposit records to CGSpace via the REST API but I told him that this skips the submission workflows and because we cannot guarantee the data quality we would not allow anyone to use it this way</li>
<li>I finished making the XMLUI changes for anonymization of IP addresses in Google Analytics and merged the changes to the <code>5_x-prod</code> branch (<a href="https://github.com/ilri/DSpace/pull/375">#375</a></li>
<li>Also, I think we might be able to implement <a href="https://developers.google.com/analytics/devguides/collection/analyticsjs/user-opt-out">opt-out functionality for Google Analytics using a window property</a> that could be managed by <a href="https://webgilde.com/en/analytics-opt-out/">storing its status in a cookie</a></li>
<li>This cookie could be set by a user clicking a link in a privacy policy, for example</li>
<li>The additional Javascript could be easily added to our existing <code>googleAnalytics</code> template in each XMLUI theme</li>
</ul>

View File

@ -4,7 +4,7 @@
<url>
<loc>https://alanorth.github.io/cgspace-notes/2018-05/</loc>
<lastmod>2018-05-17T12:37:21+03:00</lastmod>
<lastmod>2018-05-17T13:14:29+03:00</lastmod>
</url>
<url>
@ -164,7 +164,7 @@
<url>
<loc>https://alanorth.github.io/cgspace-notes/</loc>
<lastmod>2018-05-17T12:37:21+03:00</lastmod>
<lastmod>2018-05-17T13:14:29+03:00</lastmod>
<priority>0</priority>
</url>
@ -175,7 +175,7 @@
<url>
<loc>https://alanorth.github.io/cgspace-notes/tags/notes/</loc>
<lastmod>2018-05-17T12:37:21+03:00</lastmod>
<lastmod>2018-05-17T13:14:29+03:00</lastmod>
<priority>0</priority>
</url>
@ -187,13 +187,13 @@
<url>
<loc>https://alanorth.github.io/cgspace-notes/posts/</loc>
<lastmod>2018-05-17T12:37:21+03:00</lastmod>
<lastmod>2018-05-17T13:14:29+03:00</lastmod>
<priority>0</priority>
</url>
<url>
<loc>https://alanorth.github.io/cgspace-notes/tags/</loc>
<lastmod>2018-05-17T12:37:21+03:00</lastmod>
<lastmod>2018-05-17T13:14:29+03:00</lastmod>
<priority>0</priority>
</url>