Add notes for 2019-10-15

content/posts/2019-10.md

@@ -176,4 +176,38 @@ dspacetest=# select handle from item, handle where handle.resource_id = item.ite
 
 - So I'm still not sure where these weird authors in the "Top Author" stats are coming from
 
+## 2019-10-14
+
+- I talked to Peter about the Bioversity items and he said that we should add the institutional authors back to `dc.contributor.author`, because I had moved them to `cg.contributor.affiliation`
+  - Otherwise he said the data looks good
+
+## 2019-10-15
+
+- I did a test export / import of the Bioversity migration items on DSpace Test
+  - First export them:
+
+```
+$ export JAVA_OPTS='-Dfile.encoding=UTF-8 -Xmx512m'
+$ mkdir 2019-10-15-Bioversity
+$ dspace export -i 10568/108684 -t COLLECTION -m -n 0 -d 2019-10-15-Bioversity
+$ sed -i '/<dcvalue element="identifier" qualifier="uri">/d' 2019-10-15-Bioversity/*/dublin_core.xml
+```
+
+- It's really stupid, but for some reason the handles are included even though I specified the `-m` option, so after the export I removed the `dc.identifier.uri` metadata values from the items
+- Then I imported a test subset of them in my local test environment:
+
+```
+$ ~/dspace/bin/dspace import -a -c 10568/104049 -e fuu@cgiar.org -m 2019-10-15-Bioversity.map -s /tmp/2019-10-15-Bioversity
+```
+
+- I had forgotten (again) that the `dspace export` command doesn't preserve collection ownership or mappings, so I will have to create a temporary collection on CGSpace to import these to, then do the mappings again after import...
+- On CGSpace I will increase the RAM of the command line Java process for good luck before import...
+
+```
+$ export JAVA_OPTS="-Dfile.encoding=UTF-8 -Xmx1024m"
+$ dspace import -a -c 10568/104057 -e a.orth@cgiar.org -m 2019-10-15-Bioversity.map -s 2019-10-15-Bioversity
+```
+
+- After importing them I re-exported the metadata, changed the owning collections to those based on their type, then re-imported them
+
 <!-- vim: set sw=2 ts=2: -->

docs/2019-10/index.html

@@ -11,7 +11,7 @@
 <meta property="og:type" content="article" />
 <meta property="og:url" content="https://alanorth.github.io/cgspace-notes/2019-10/" />
 <meta property="article:published_time" content="2019-10-01T13:20:51+03:00" />
-<meta property="article:modified_time" content="2019-10-13T11:59:11+03:00" />
+<meta property="article:modified_time" content="2019-10-13T21:17:22+03:00" />
 
 <meta name="twitter:card" content="summary"/>
 <meta name="twitter:title" content="October, 2019"/>
@@ -27,9 +27,9 @@
   "@type": "BlogPosting",
   "headline": "October, 2019",
   "url": "https:\/\/alanorth.github.io\/cgspace-notes\/2019-10\/",
-  "wordCount": "1250",
+  "wordCount": "1478",
   "datePublished": "2019-10-01T13:20:51+03:00",
-  "dateModified": "2019-10-13T11:59:11+03:00",
+  "dateModified": "2019-10-13T21:17:22+03:00",
   "author": {
     "@type": "Person",
     "name": "Alan Orth"
@@ -328,6 +328,49 @@ handle
 <li><p>So I&rsquo;m still not sure where these weird authors in the &ldquo;Top Author&rdquo; stats are coming from</p></li>
 </ul>
 
+<h2 id="2019-10-14">2019-10-14</h2>
+
+<ul>
+<li>I talked to Peter about the Bioversity items and he said that we should add the institutional authors back to <code>dc.contributor.author</code>, because I had moved them to <code>cg.contributor.affiliation</code>
+
+<ul>
+<li>Otherwise he said the data looks good</li>
+</ul></li>
+</ul>
+
+<h2 id="2019-10-15">2019-10-15</h2>
+
+<ul>
+<li><p>I did a test export / import of the Bioversity migration items on DSpace Test</p>
+
+<ul>
+<li><p>First export them:</p>
+
+<pre><code>$ export JAVA_OPTS='-Dfile.encoding=UTF-8 -Xmx512m'
+$ mkdir 2019-10-15-Bioversity
+$ dspace export -i 10568/108684 -t COLLECTION -m -n 0 -d 2019-10-15-Bioversity
+$ sed -i '/&lt;dcvalue element=&quot;identifier&quot; qualifier=&quot;uri&quot;&gt;/d' 2019-10-15-Bioversity/*/dublin_core.xml
+</code></pre></li>
+</ul></li>
+
+<li><p>It&rsquo;s really stupid, but for some reason the handles are included even though I specified the <code>-m</code> option, so after the export I removed the <code>dc.identifier.uri</code> metadata values from the items</p></li>
+
+<li><p>Then I imported a test subset of them in my local test environment:</p>
+
+<pre><code>$ ~/dspace/bin/dspace import -a -c 10568/104049 -e fuu@cgiar.org -m 2019-10-15-Bioversity.map -s /tmp/2019-10-15-Bioversity
+</code></pre></li>
+
+<li><p>I had forgotten (again) that the <code>dspace export</code> command doesn&rsquo;t preserve collection ownership or mappings, so I will have to create a temporary collection on CGSpace to import these to, then do the mappings again after import&hellip;</p></li>
+
+<li><p>On CGSpace I will increase the RAM of the command line Java process for good luck before import&hellip;</p>
+
+<pre><code>$ export JAVA_OPTS=&quot;-Dfile.encoding=UTF-8 -Xmx1024m&quot;
+$ dspace import -a -c 10568/104057 -e a.orth@cgiar.org -m 2019-10-15-Bioversity.map -s 2019-10-15-Bioversity
+</code></pre></li>
+
+<li><p>After importing them I re-exported the metadata, changed the owning collections to those based on their type, then re-imported them</p></li>
+</ul>
+
 <!-- vim: set sw=2 ts=2: -->
 
 

docs/sitemap.xml

@@ -4,27 +4,27 @@
   
   <url>
     <loc>https://alanorth.github.io/cgspace-notes/</loc>
-    <lastmod>2019-10-13T11:59:11+03:00</lastmod>
+    <lastmod>2019-10-13T21:17:22+03:00</lastmod>
   </url>
   
   <url>
     <loc>https://alanorth.github.io/cgspace-notes/tags/notes/</loc>
-    <lastmod>2019-10-13T11:59:11+03:00</lastmod>
+    <lastmod>2019-10-13T21:17:22+03:00</lastmod>
   </url>
   
   <url>
     <loc>https://alanorth.github.io/cgspace-notes/2019-10/</loc>
-    <lastmod>2019-10-13T11:59:11+03:00</lastmod>
+    <lastmod>2019-10-13T21:17:22+03:00</lastmod>
   </url>
   
   <url>
     <loc>https://alanorth.github.io/cgspace-notes/posts/</loc>
-    <lastmod>2019-10-13T11:59:11+03:00</lastmod>
+    <lastmod>2019-10-13T21:17:22+03:00</lastmod>
   </url>
   
   <url>
     <loc>https://alanorth.github.io/cgspace-notes/tags/</loc>
-    <lastmod>2019-10-13T11:59:11+03:00</lastmod>
+    <lastmod>2019-10-13T21:17:22+03:00</lastmod>
   </url>
   
   <url>