Update notes for 2019-08-31

content/posts/2019-08.md

@@ -338,4 +338,25 @@ $ find dspace/modules/xmlui-mirage2/src/main/webapp/themes -iname "*.xsl" -exec
 
 - So this is the same issue we had before, where Altmetric *knows* this Handle is associated with a DOI that has a score, but the client-side JavaScript code doesn't show it because it seems to a secondary handle or something
 
+## 2019-08-31
+
+- Run system updates on DSpace Test (linode19) and reboot the server 
+- Run the author fixes on DSpace Test and CGSpace and start a full Discovery re-index:
+
+```
+$ time schedtool -B -e ionice -c2 -n7 nice -n19 dspace index-discovery -b
+ 
+real    90m47.967s
+user    8m12.826s
+sys     2m27.496s
+```
+
+- I set up a test environment for CG Core v2 on my local environment and ran all the field migrations
+  - DSpace comes up and runs, but there are some graphical issues, like missing community names
+  - It turns out that my sed script was replacing some XSL code that was responsible for printing community names
+  - See: `dspace/modules/xmlui-mirage2/src/main/webapp/themes/0_CGIAR/xsl/preprocess/custom/communitylist.xsl`
+  - After reading the code I see that XSLT is reading the community titles from the DIM representation (stored in the `$dim` variable) created from METS
+  - I modified the patterns in my sed script so that those lines are not replaced and then the community list works again
+  - This is actually not a problem at all because this metadata is only used in the HTML meta tags in XMLUI community lists and has nothing to do with item metadata
+
 <!-- vim: set sw=2 ts=2: -->