Add notes for 2018-06-10

This commit is contained in:
Alan Orth 2018-06-10 14:12:07 +03:00
parent dde6a7adac
commit 75a7f8dc55
Signed by: alanorth
GPG Key ID: 0FB860CC9C45B1B9
3 changed files with 37 additions and 8 deletions

View File

@ -79,3 +79,16 @@ $ ./fix-metadata-values.py -i /tmp/2018-06-08-CIP-Authors.csv -db dspace -u dspa
- It's pretty annoying, but the JVM monitoring for Munin was never set up when I migrated DSpace Test to its new server a few months ago - It's pretty annoying, but the JVM monitoring for Munin was never set up when I migrated DSpace Test to its new server a few months ago
- I ran the tomcat and munin-node tags in Ansible again and now the stuff is all wired up and recording stats properly - I ran the tomcat and munin-node tags in Ansible again and now the stuff is all wired up and recording stats properly
- I applied the CIP author corrections on CGSpace and DSpace Test and re-ran the Discovery indexing - I applied the CIP author corrections on CGSpace and DSpace Test and re-ran the Discovery indexing
## 2018-06-10
- I spent some time removing the Atmire Metadata Quality Module (MQM) from the proposed DSpace 5.8 changes
- After removing all code mentioning MQM, mqm, metadata-quality, batchedit, duplicatechecker, etc, I think I got most of it removed, but there is a Spring error during Tomcat startup:
```
INFO [org.dspace.servicemanager.DSpaceServiceManager] Shutdown DSpace core service manager
Failed to startup the DSpace Service Manager: failure starting up spring service manager: Error creating bean with name 'org.dspace.servicemanager.spring.DSpaceBeanPostProcessor#0' defined in class path resource [spring/spring-dspace-applicationContext.xml]: Unsatisfied dependency expressed through constructor argument with index 0 of type [org.dspace.servicemanager.config.DSpaceConfigurationService]: : Cannot find class [com.atmire.dspace.discovery.ItemCollectionPlugin] for bean with name 'itemCollectionPlugin' defined in file [/home/aorth/dspace/config/spring/api/discovery.xml];
```
- I can fix this by commenting out the `ItemCollectionPlugin` line of `discovery.xml`, but from looking at the git log I'm not actually sure if that is related to MQM or not
- I will have to ask Atmire

View File

@ -41,7 +41,7 @@ sys 2m7.289s
<meta property="article:published_time" content="2018-06-04T19:49:54-07:00"/> <meta property="article:published_time" content="2018-06-04T19:49:54-07:00"/>
<meta property="article:modified_time" content="2018-06-08T11:04:27&#43;02:00"/> <meta property="article:modified_time" content="2018-06-09T11:48:41&#43;03:00"/>
@ -93,9 +93,9 @@ sys 2m7.289s
"@type": "BlogPosting", "@type": "BlogPosting",
"headline": "June, 2018", "headline": "June, 2018",
"url": "https://alanorth.github.io/cgspace-notes/2018-06/", "url": "https://alanorth.github.io/cgspace-notes/2018-06/",
"wordCount": "487", "wordCount": "628",
"datePublished": "2018-06-04T19:49:54-07:00", "datePublished": "2018-06-04T19:49:54-07:00",
"dateModified": "2018-06-08T11:04:27&#43;02:00", "dateModified": "2018-06-09T11:48:41&#43;03:00",
"author": { "author": {
"@type": "Person", "@type": "Person",
"name": "Alan Orth" "name": "Alan Orth"
@ -253,6 +253,22 @@ update schema_version set version = '5.8.2015.12.03.3' where version = '5.5.2015
<li>I applied the CIP author corrections on CGSpace and DSpace Test and re-ran the Discovery indexing</li> <li>I applied the CIP author corrections on CGSpace and DSpace Test and re-ran the Discovery indexing</li>
</ul> </ul>
<h2 id="2018-06-10">2018-06-10</h2>
<ul>
<li>I spent some time removing the Atmire Metadata Quality Module (MQM) from the proposed DSpace 5.8 changes</li>
<li>After removing all code mentioning MQM, mqm, metadata-quality, batchedit, duplicatechecker, etc, I think I got most of it removed, but there is a Spring error during Tomcat startup:</li>
</ul>
<pre><code> INFO [org.dspace.servicemanager.DSpaceServiceManager] Shutdown DSpace core service manager
Failed to startup the DSpace Service Manager: failure starting up spring service manager: Error creating bean with name 'org.dspace.servicemanager.spring.DSpaceBeanPostProcessor#0' defined in class path resource [spring/spring-dspace-applicationContext.xml]: Unsatisfied dependency expressed through constructor argument with index 0 of type [org.dspace.servicemanager.config.DSpaceConfigurationService]: : Cannot find class [com.atmire.dspace.discovery.ItemCollectionPlugin] for bean with name 'itemCollectionPlugin' defined in file [/home/aorth/dspace/config/spring/api/discovery.xml];
</code></pre>
<ul>
<li>I can fix this by commenting out the <code>ItemCollectionPlugin</code> line of <code>discovery.xml</code>, but from looking at the git log I&rsquo;m not actually sure if that is related to MQM or not</li>
<li>I will have to ask Atmire</li>
</ul>

View File

@ -4,7 +4,7 @@
<url> <url>
<loc>https://alanorth.github.io/cgspace-notes/2018-06/</loc> <loc>https://alanorth.github.io/cgspace-notes/2018-06/</loc>
<lastmod>2018-06-08T11:04:27+02:00</lastmod> <lastmod>2018-06-09T11:48:41+03:00</lastmod>
</url> </url>
<url> <url>
@ -169,7 +169,7 @@
<url> <url>
<loc>https://alanorth.github.io/cgspace-notes/</loc> <loc>https://alanorth.github.io/cgspace-notes/</loc>
<lastmod>2018-06-08T11:04:27+02:00</lastmod> <lastmod>2018-06-09T11:48:41+03:00</lastmod>
<priority>0</priority> <priority>0</priority>
</url> </url>
@ -180,7 +180,7 @@
<url> <url>
<loc>https://alanorth.github.io/cgspace-notes/tags/notes/</loc> <loc>https://alanorth.github.io/cgspace-notes/tags/notes/</loc>
<lastmod>2018-06-08T11:04:27+02:00</lastmod> <lastmod>2018-06-09T11:48:41+03:00</lastmod>
<priority>0</priority> <priority>0</priority>
</url> </url>
@ -192,13 +192,13 @@
<url> <url>
<loc>https://alanorth.github.io/cgspace-notes/posts/</loc> <loc>https://alanorth.github.io/cgspace-notes/posts/</loc>
<lastmod>2018-06-08T11:04:27+02:00</lastmod> <lastmod>2018-06-09T11:48:41+03:00</lastmod>
<priority>0</priority> <priority>0</priority>
</url> </url>
<url> <url>
<loc>https://alanorth.github.io/cgspace-notes/tags/</loc> <loc>https://alanorth.github.io/cgspace-notes/tags/</loc>
<lastmod>2018-06-08T11:04:27+02:00</lastmod> <lastmod>2018-06-09T11:48:41+03:00</lastmod>
<priority>0</priority> <priority>0</priority>
</url> </url>