Add notes for 2018-06-10

content/posts/2018-06.md

@@ -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
 - 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
+
+## 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