Update notes for 2018-07-23

This commit is contained in:
Alan Orth 2018-07-23 10:49:14 +03:00
parent 23b1887019
commit a8a7e077b8
Signed by: alanorth
GPG Key ID: 0FB860CC9C45B1B9
3 changed files with 59 additions and 8 deletions

View File

@ -457,4 +457,28 @@ webui.itemlist.sort-option.3 = dateaccessioned:dc.date.accessioned:date
- I finally informed Atmire that we're ready to proceed with deploying this to CGSpace and that they should advise whether we should wait about the SNAPSHOT versions in `pom.xml`
- There is no word on the issue I reported with Tomcat 8.5.32 yet, though...
## 2018-07-23
- Still discussing dates with IWMI
- I looked in the database to see the breakdown of date formats used in `dc.date.issued`, ie YYYY, YYYY-MM, or YYYY-MM-DD:
```
dspace=# select count(text_value) from metadatavalue where resource_type_id=2 and metadata_field_id=15 and text_value ~ '^[0-9]{4}$';
count
-------
53292
(1 row)
dspace=# select count(text_value) from metadatavalue where resource_type_id=2 and metadata_field_id=15 and text_value ~ '^[0-9]{4}-[0-9]{2}$';
count
-------
3818
(1 row)
dspace=# select count(text_value) from metadatavalue where resource_type_id=2 and metadata_field_id=15 and text_value ~ '^[0-9]{4}-[0-9]{2}-[0-9]{2}$';
count
-------
17357
```
- So it looks like YYYY is the most numerious, followed by YYYY-MM-DD, then YYYY-MM
<!-- vim: set sw=2 ts=2: -->

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-22T17:10:13&#43;03:00"/>
<meta property="article:modified_time" content="2018-07-22T17:10:44&#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": "3238",
"wordCount": "3330",
"datePublished": "2018-07-01T12:56:54&#43;03:00",
"dateModified": "2018-07-22T17:10:13&#43;03:00",
"dateModified": "2018-07-22T17:10:44&#43;03:00",
"author": {
"@type": "Person",
"name": "Alan Orth"
@ -652,6 +652,33 @@ X-XSS-Protection: 1; mode=block
<li>There is no word on the issue I reported with Tomcat 8.5.32 yet, though&hellip;</li>
</ul>
<h2 id="2018-07-23">2018-07-23</h2>
<ul>
<li>Still discussing dates with IWMI</li>
<li>I looked in the database to see the breakdown of date formats used in <code>dc.date.issued</code>, ie YYYY, YYYY-MM, or YYYY-MM-DD:</li>
</ul>
<pre><code>dspace=# select count(text_value) from metadatavalue where resource_type_id=2 and metadata_field_id=15 and text_value ~ '^[0-9]{4}$';
count
-------
53292
(1 row)
dspace=# select count(text_value) from metadatavalue where resource_type_id=2 and metadata_field_id=15 and text_value ~ '^[0-9]{4}-[0-9]{2}$';
count
-------
3818
(1 row)
dspace=# select count(text_value) from metadatavalue where resource_type_id=2 and metadata_field_id=15 and text_value ~ '^[0-9]{4}-[0-9]{2}-[0-9]{2}$';
count
-------
17357
</code></pre>
<ul>
<li>So it looks like YYYY is the most numerious, followed by YYYY-MM-DD, then YYYY-MM</li>
</ul>
<!-- vim: set sw=2 ts=2: -->

View File

@ -4,7 +4,7 @@
<url>
<loc>https://alanorth.github.io/cgspace-notes/2018-07/</loc>
<lastmod>2018-07-22T17:10:13+03:00</lastmod>
<lastmod>2018-07-22T17:10:44+03:00</lastmod>
</url>
<url>
@ -174,7 +174,7 @@
<url>
<loc>https://alanorth.github.io/cgspace-notes/</loc>
<lastmod>2018-07-22T17:10:13+03:00</lastmod>
<lastmod>2018-07-22T17:10:44+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-22T17:10:13+03:00</lastmod>
<lastmod>2018-07-22T17:10:44+03:00</lastmod>
<priority>0</priority>
</url>
@ -197,13 +197,13 @@
<url>
<loc>https://alanorth.github.io/cgspace-notes/posts/</loc>
<lastmod>2018-07-22T17:10:13+03:00</lastmod>
<lastmod>2018-07-22T17:10:44+03:00</lastmod>
<priority>0</priority>
</url>
<url>
<loc>https://alanorth.github.io/cgspace-notes/tags/</loc>
<lastmod>2018-07-22T17:10:13+03:00</lastmod>
<lastmod>2018-07-22T17:10:44+03:00</lastmod>
<priority>0</priority>
</url>