mirror of
https://github.com/alanorth/cgspace-notes.git
synced 2025-01-27 05:49:12 +01:00
Add notes for 2018-02-15
This commit is contained in:
@ -23,7 +23,7 @@ I copied the logic in the jmx_tomcat_dbpools provided by Ubuntu’s munin-pl
|
||||
|
||||
<meta property="article:published_time" content="2018-02-01T16:28:54+02:00"/>
|
||||
|
||||
<meta property="article:modified_time" content="2018-02-14T13:56:18+02:00"/>
|
||||
<meta property="article:modified_time" content="2018-02-14T16:45:03+02:00"/>
|
||||
|
||||
|
||||
|
||||
@ -57,9 +57,9 @@ I copied the logic in the jmx_tomcat_dbpools provided by Ubuntu’s munin-pl
|
||||
"@type": "BlogPosting",
|
||||
"headline": "February, 2018",
|
||||
"url": "https://alanorth.github.io/cgspace-notes/2018-02/",
|
||||
"wordCount": "3527",
|
||||
"wordCount": "3581",
|
||||
"datePublished": "2018-02-01T16:28:54+02:00",
|
||||
"dateModified": "2018-02-14T13:56:18+02:00",
|
||||
"dateModified": "2018-02-14T16:45:03+02:00",
|
||||
"author": {
|
||||
"@type": "Person",
|
||||
"name": "Alan Orth"
|
||||
@ -710,6 +710,20 @@ UPDATE 1
|
||||
<li>Then the cleanup process will continue for awhile and hit another foreign key conflict, and eventually it will complete after you manually resolve them all</li>
|
||||
</ul>
|
||||
|
||||
<h2 id="2018-02-15">2018-02-15</h2>
|
||||
|
||||
<ul>
|
||||
<li>Altmetric seems to be indexing DSpace Test for some reason:
|
||||
|
||||
<ul>
|
||||
<li>See this item on DSpace Test: <a href="https://dspacetest.cgiar.org/handle/10568/78450">https://dspacetest.cgiar.org/handle/10568/78450</a></li>
|
||||
<li>See the corresponding page on Altmetric: <a href="https://www.altmetric.com/details/handle/10568/78450">https://www.altmetric.com/details/handle/10568/78450</a></li>
|
||||
</ul></li>
|
||||
<li>And this item doesn’t even exist on CGSpace!</li>
|
||||
<li>Start working on XMLUI item display code for ORCIDs</li>
|
||||
<li>Send emails to Macaroni Bros and Usman at CIFOR about ORCID metadata</li>
|
||||
</ul>
|
||||
|
||||
|
||||
|
||||
|
||||
|
Reference in New Issue
Block a user