Update notes for 2017-02-09

content/post/2017-02.md

@@ -39,3 +39,15 @@ DELETE 1
 ```
 $ ./fix-metadata-values.py -i /tmp/CCAFS-Authors-Feb-7.csv -f dc.contributor.author -t 'correct name' -m 3 -d dspace -u dspace -p fuuu
 ```
+
+## 2017-02-09
+
+- More work on CCAFS Phase II stuff
+- Looks like simply adding a new metadata field to `dspace/config/registries/cgiar-types.xml` and restarting DSpace causes the field to get added to the rregistry
+- It requires a restart but at least it allows you to manage the registry programmatically
+- It's not a very good way to manage the registry, though, as removing one there doesn't cause it to be removed from the registry, and we always restore from database backups so there would never be a scenario when we needed these to be created
+- Testing some corrections on CCAFS Phase II flagships (`cg.subject.ccafs`):
+
+```
+$ ./fix-metadata-values.py -i ccafs-flagships-feb7.csv -f cg.subject.ccafs -t correct -m 210 -d dspace -u dspace -p fuuu
+```

public/2017-02/index.html

@@ -92,7 +92,7 @@ Looks like we’ll be using cg.identifier.ccafsprojectpii as the field name
   
   "headline": "February, 2017",
   "url": "https://alanorth.github.io/cgspace-notes/2017-02/",
-  "wordCount": "188",
+  "wordCount": "303",
   
   
   "datePublished": "2017-02-07T07:04:52-08:00",
@@ -209,6 +209,19 @@ DELETE 1
 <pre><code>$ ./fix-metadata-values.py -i /tmp/CCAFS-Authors-Feb-7.csv -f dc.contributor.author -t 'correct name' -m 3 -d dspace -u dspace -p fuuu
 </code></pre>
 
+<h2 id="2017-02-09">2017-02-09</h2>
+
+<ul>
+<li>More work on CCAFS Phase II stuff</li>
+<li>Looks like simply adding a new metadata field to <code>dspace/config/registries/cgiar-types.xml</code> and restarting DSpace causes the field to get added to the rregistry</li>
+<li>It requires a restart but at least it allows you to manage the registry programmatically</li>
+<li>It&rsquo;s not a very good way to manage the registry, though, as removing one there doesn&rsquo;t cause it to be removed from the registry, and we always restore from database backups so there would never be a scenario when we needed these to be created</li>
+<li>Testing some corrections on CCAFS Phase II flagships (<code>cg.subject.ccafs</code>):</li>
+</ul>
+
+<pre><code>$ ./fix-metadata-values.py -i ccafs-flagships-feb7.csv -f cg.subject.ccafs -t correct -m 210 -d dspace -u dspace -p fuuu
+</code></pre>
+
   
 
   

public/index.xml

@@ -55,6 +55,19 @@ DELETE 1
 </ul>
 
 <pre><code>$ ./fix-metadata-values.py -i /tmp/CCAFS-Authors-Feb-7.csv -f dc.contributor.author -t 'correct name' -m 3 -d dspace -u dspace -p fuuu
+</code></pre>
+
+<h2 id="2017-02-09">2017-02-09</h2>
+
+<ul>
+<li>More work on CCAFS Phase II stuff</li>
+<li>Looks like simply adding a new metadata field to <code>dspace/config/registries/cgiar-types.xml</code> and restarting DSpace causes the field to get added to the rregistry</li>
+<li>It requires a restart but at least it allows you to manage the registry programmatically</li>
+<li>It’s not a very good way to manage the registry, though, as removing one there doesn’t cause it to be removed from the registry, and we always restore from database backups so there would never be a scenario when we needed these to be created</li>
+<li>Testing some corrections on CCAFS Phase II flagships (<code>cg.subject.ccafs</code>):</li>
+</ul>
+
+<pre><code>$ ./fix-metadata-values.py -i ccafs-flagships-feb7.csv -f cg.subject.ccafs -t correct -m 210 -d dspace -u dspace -p fuuu
 &lt;/code&gt;&lt;/pre&gt;</description>
     </item>
     

public/post/index.xml

@@ -55,6 +55,19 @@ DELETE 1
 </ul>
 
 <pre><code>$ ./fix-metadata-values.py -i /tmp/CCAFS-Authors-Feb-7.csv -f dc.contributor.author -t 'correct name' -m 3 -d dspace -u dspace -p fuuu
+</code></pre>
+
+<h2 id="2017-02-09">2017-02-09</h2>
+
+<ul>
+<li>More work on CCAFS Phase II stuff</li>
+<li>Looks like simply adding a new metadata field to <code>dspace/config/registries/cgiar-types.xml</code> and restarting DSpace causes the field to get added to the rregistry</li>
+<li>It requires a restart but at least it allows you to manage the registry programmatically</li>
+<li>It’s not a very good way to manage the registry, though, as removing one there doesn’t cause it to be removed from the registry, and we always restore from database backups so there would never be a scenario when we needed these to be created</li>
+<li>Testing some corrections on CCAFS Phase II flagships (<code>cg.subject.ccafs</code>):</li>
+</ul>
+
+<pre><code>$ ./fix-metadata-values.py -i ccafs-flagships-feb7.csv -f cg.subject.ccafs -t correct -m 210 -d dspace -u dspace -p fuuu
 &lt;/code&gt;&lt;/pre&gt;</description>
     </item>
     

public/tags/notes/index.xml

@@ -54,6 +54,19 @@ DELETE 1
 </ul>
 
 <pre><code>$ ./fix-metadata-values.py -i /tmp/CCAFS-Authors-Feb-7.csv -f dc.contributor.author -t 'correct name' -m 3 -d dspace -u dspace -p fuuu
+</code></pre>
+
+<h2 id="2017-02-09">2017-02-09</h2>
+
+<ul>
+<li>More work on CCAFS Phase II stuff</li>
+<li>Looks like simply adding a new metadata field to <code>dspace/config/registries/cgiar-types.xml</code> and restarting DSpace causes the field to get added to the rregistry</li>
+<li>It requires a restart but at least it allows you to manage the registry programmatically</li>
+<li>It’s not a very good way to manage the registry, though, as removing one there doesn’t cause it to be removed from the registry, and we always restore from database backups so there would never be a scenario when we needed these to be created</li>
+<li>Testing some corrections on CCAFS Phase II flagships (<code>cg.subject.ccafs</code>):</li>
+</ul>
+
+<pre><code>$ ./fix-metadata-values.py -i ccafs-flagships-feb7.csv -f cg.subject.ccafs -t correct -m 210 -d dspace -u dspace -p fuuu
 &lt;/code&gt;&lt;/pre&gt;</description>
     </item>