alanorth/cgspace-notes
1
0
Fork 0
mirror of https://github.com/alanorth/cgspace-notes.git synced 2024-06-25 07:33:49 +02:00
Code Issues Projects Releases Wiki Activity

Update notes for 2018-07-19

Browse Source
This commit is contained in:
Alan Orth 2018-07-19 16:16:43 +03:00
parent 197b49878a
commit b23fc39188
Signed by: alanorth
GPG Key ID: 0FB860CC9C45B1B9
3 changed files with 16 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
content/posts/2018-07.md
View File

@ -437,5 +437,9 @@ X-XSS-Protection: 1; mode=block
- In addition to testing DSpace 5.8, I specifically wanted to see if the issue with specifying collections in metadata instead of on the command line would work ([DS-3583](https://jira.duraspace.org/browse/DS-3583))
- Post a note on Yammer about Altmetric and Handle best practices
- Update PostgreSQL JDBC jar from 42.2.2 to 42.2.4 in the [RMG Ansible playbooks](https://github.com/ilri/rmg-ansible-public)
- IWMI asked why all the dates in their [OpenSearch RSS feed](https://cgspace.cgiar.org/open-search/discover?query=dateIssued:2018&scope=10568/16814&sort_by=2&order=DESC&rpp=100&format=rss) show up as January 01, 2018
- On closer inspection I notice that many of their items use "2018" as their `dc.date.issued`, which is a valid ISO 8601 date but it's not very specific so DSpace assumes it is January 01, 2018 00:00:00...
- I told her that they need to start using more accurate dates for their issue dates
- In the example item I looked at the DOI has a publish date of 2018-03-16, so they should really try to capture that
<!-- vim: set sw=2 ts=2: -->

10
docs/2018-07/index.html
View File

@ -30,7 +30,7 @@ There is insufficient memory for the Java Runtime Environment to continue.
<meta property="article:published_time" content="2018-07-01T12:56:54&#43;03:00"/>
<meta property="article:modified_time" content="2018-07-18T17:47:36&#43;03:00"/>
<meta property="article:modified_time" content="2018-07-19T11:23:52&#43;03:00"/>
@ -71,9 +71,9 @@ There is insufficient memory for the Java Runtime Environment to continue.
"@type": "BlogPosting",
"headline": "July, 2018",
"url": "https://alanorth.github.io/cgspace-notes/2018-07/",
"wordCount": "2963",
"wordCount": "3055",
"datePublished": "2018-07-01T12:56:54&#43;03:00",
"dateModified": "2018-07-18T17:47:36&#43;03:00",
"dateModified": "2018-07-19T11:23:52&#43;03:00",
"author": {
"@type": "Person",
"name": "Alan Orth"
@ -628,6 +628,10 @@ X-XSS-Protection: 1; mode=block
<li>In addition to testing DSpace 5.8, I specifically wanted to see if the issue with specifying collections in metadata instead of on the command line would work (<a href="https://jira.duraspace.org/browse/DS-3583">DS-3583</a>)</li>
<li>Post a note on Yammer about Altmetric and Handle best practices</li>
<li>Update PostgreSQL JDBC jar from 42.2.2 to 42.2.4 in the <a href="https://github.com/ilri/rmg-ansible-public">RMG Ansible playbooks</a></li>
<li>IWMI asked why all the dates in their <a href="https://cgspace.cgiar.org/open-search/discover?query=dateIssued:2018&amp;scope=10568/16814&amp;sort_by=2&amp;order=DESC&amp;rpp=100&amp;format=rss">OpenSearch RSS feed</a> show up as January 01, 2018</li>
<li>On closer inspection I notice that many of their items use &ldquo;2018&rdquo; as their <code>dc.date.issued</code>, which is a valid ISO 8601 date but it&rsquo;s not very specific so DSpace assumes it is January 01, 2018 00:00:00&hellip;</li>
<li>I told her that they need to start using more accurate dates for their issue dates</li>
<li>In the example item I looked at the DOI has a publish date of 2018-03-16, so they should really try to capture that</li>
</ul>
<!-- vim: set sw=2 ts=2: -->

10
docs/sitemap.xml
View File

@ -4,7 +4,7 @@
<url>
<loc>https://alanorth.github.io/cgspace-notes/2018-07/</loc>
<lastmod>2018-07-18T17:47:36+03:00</lastmod>
<lastmod>2018-07-19T11:23:52+03:00</lastmod>
</url>
<url>
@ -174,7 +174,7 @@
<url>
<loc>https://alanorth.github.io/cgspace-notes/</loc>
<lastmod>2018-07-18T17:47:36+03:00</lastmod>
<lastmod>2018-07-19T11:23:52+03:00</lastmod>
<priority>0</priority>
</url>
@ -185,7 +185,7 @@
<url>
<loc>https://alanorth.github.io/cgspace-notes/tags/notes/</loc>
<lastmod>2018-07-18T17:47:36+03:00</lastmod>
<lastmod>2018-07-19T11:23:52+03:00</lastmod>
<priority>0</priority>
</url>
@ -197,13 +197,13 @@
<url>
<loc>https://alanorth.github.io/cgspace-notes/posts/</loc>
<lastmod>2018-07-18T17:47:36+03:00</lastmod>
<lastmod>2018-07-19T11:23:52+03:00</lastmod>
<priority>0</priority>
</url>
<url>
<loc>https://alanorth.github.io/cgspace-notes/tags/</loc>
<lastmod>2018-07-18T17:47:36+03:00</lastmod>
<lastmod>2018-07-19T11:23:52+03:00</lastmod>
<priority>0</priority>
</url>