diff --git a/content/posts/2018-07.md b/content/posts/2018-07.md index 0326792e1..a1300414c 100644 --- a/content/posts/2018-07.md +++ b/content/posts/2018-07.md @@ -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 diff --git a/docs/2018-07/index.html b/docs/2018-07/index.html index d02693ad8..7f654d64b 100644 --- a/docs/2018-07/index.html +++ b/docs/2018-07/index.html @@ -30,7 +30,7 @@ There is insufficient memory for the Java Runtime Environment to continue. - + @@ -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+03:00", - "dateModified": "2018-07-18T17:47:36+03:00", + "dateModified": "2018-07-19T11:23:52+03:00", "author": { "@type": "Person", "name": "Alan Orth" @@ -628,6 +628,10 @@ 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)
  • 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
  • +
  • IWMI asked why all the dates in their OpenSearch RSS feed 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
  • diff --git a/docs/sitemap.xml b/docs/sitemap.xml index 35441454e..10c9e724b 100644 --- a/docs/sitemap.xml +++ b/docs/sitemap.xml @@ -4,7 +4,7 @@ https://alanorth.github.io/cgspace-notes/2018-07/ - 2018-07-18T17:47:36+03:00 + 2018-07-19T11:23:52+03:00 @@ -174,7 +174,7 @@ https://alanorth.github.io/cgspace-notes/ - 2018-07-18T17:47:36+03:00 + 2018-07-19T11:23:52+03:00 0 @@ -185,7 +185,7 @@ https://alanorth.github.io/cgspace-notes/tags/notes/ - 2018-07-18T17:47:36+03:00 + 2018-07-19T11:23:52+03:00 0 @@ -197,13 +197,13 @@ https://alanorth.github.io/cgspace-notes/posts/ - 2018-07-18T17:47:36+03:00 + 2018-07-19T11:23:52+03:00 0 https://alanorth.github.io/cgspace-notes/tags/ - 2018-07-18T17:47:36+03:00 + 2018-07-19T11:23:52+03:00 0