Update notes for 2017-03-05

content/post/2017-03.md

@@ -59,6 +59,12 @@ $ identify -format '%r\n' Africa\ group\ of\ negotiators.pdf\[0\]
 DirectClass sRGB Alpha
 ```
 
+## 2017-03-04
+
+- Spent more time looking at the ImageMagick CMYK issue
+- The `default_cmyk.icc` and `default_rgb.icc` files are both part of the Ghostscript GPL distribution, but according to DSpace's `LICENSES_THIRD_PARTY` file, DSpace doesn't allow distribution of dependencies that are licensed solely under the GPL
+- So this issue is kinda pointless now, as the ICC profiles are absolutely necessary to make a meaningful CMYK→sRGB conversion
+
 ## 2017-03-05
 
 - Look into helping developers from landportal.info with a query for items related to LAND on the REST API
@@ -70,3 +76,42 @@ $ curl -s -H "accept: application/json" -H "Content-Type: application/json" -X P
 ```
 
 - But there are hundreds of combinations of fields and values (like `dc.subject` and all the center subjects), and we can't use wildcards in REST!
+- Reading about enabling multiple handle prefixes in DSpace
+- There is a mailing list thread from 2011 about it: http://dspace.2283337.n4.nabble.com/Multiple-handle-prefixes-merged-DSpace-instances-td3427192.html
+- And a comment from Atmire's Bram about it on the DSpace wiki: https://wiki.duraspace.org/display/DSDOC5x/Installing+DSpace?focusedCommentId=78163296#comment-78163296
+- Bram mentions an undocumented configuration option `handle.plugin.checknameauthority`, but I noticed another one in `dspace.cfg`: 
+
+```
+# List any additional prefixes that need to be managed by this handle server
+# (as for examle handle prefix coming from old dspace repository merged in
+# that repository)
+# handle.additional.prefixes = prefix1[, prefix2]
+```
+
+- Because of this I noticed that our Handle server's `config.dct` was potentially misconfigured!
+- We had some default values still present:
+
+```
+"300:0.NA/YOUR_NAMING_AUTHORITY"
+```
+
+- I've changed them to the following and restarted the handle server:
+
+```
+"300:0.NA/10568"
+```
+
+- In looking at all the configs I just noticed that we are not providing a DOI in the Google-specific metadata crosswalk
+- From `dspace/config/crosswalks/google-metadata.properties`:
+
+```
+google.citation_doi = cg.identifier.doi
+```
+
+- This works, and makes DSpace output the following metadata on the item view page:
+
+```
+<meta content="https://dx.doi.org/10.1186/s13059-017-1153-y" name="citation_doi">
+```
+
+- Submitted and merged pull request for this: https://github.com/ilri/DSpace/pull/305

public/2017-03/index.html

@@ -37,7 +37,7 @@ $ identify ~/Desktop/alc_contrastes_desafios.jpg
 
 
 <meta property="article:published_time" content="2017-03-01T17:08:52&#43;02:00"/>
-<meta property="article:modified_time" content="2017-03-04T01:15:47&#43;02:00"/>
+<meta property="article:modified_time" content="2017-03-05T12:39:09&#43;02:00"/>
 
 
 
@@ -94,13 +94,13 @@ $ identify ~/Desktop/alc_contrastes_desafios.jpg
   
   "headline": "March, 2017",
   "url": "https://alanorth.github.io/cgspace-notes/2017-03/",
-  "wordCount": "465",
+  "wordCount": "692",
   
   
   "datePublished": "2017-03-01T17:08:52&#43;02:00",
   
   
-  "dateModified": "2017-03-04T01:15:47&#43;02:00",
+  "dateModified": "2017-03-05T12:39:09&#43;02:00",
   
   
   "author": {
@@ -232,6 +232,14 @@ $ identify -format '%r\n' Africa\ group\ of\ negotiators.pdf\[0\]
 DirectClass sRGB Alpha
 </code></pre>
 
+<h2 id="2017-03-04">2017-03-04</h2>
+
+<ul>
+<li>Spent more time looking at the ImageMagick CMYK issue</li>
+<li>The <code>default_cmyk.icc</code> and <code>default_rgb.icc</code> files are both part of the Ghostscript GPL distribution, but according to DSpace&rsquo;s <code>LICENSES_THIRD_PARTY</code> file, DSpace doesn&rsquo;t allow distribution of dependencies that are licensed solely under the GPL</li>
+<li>So this issue is kinda pointless now, as the ICC profiles are absolutely necessary to make a meaningful CMYK→sRGB conversion</li>
+</ul>
+
 <h2 id="2017-03-05">2017-03-05</h2>
 
 <ul>
@@ -245,6 +253,50 @@ DirectClass sRGB Alpha
 
 <ul>
 <li>But there are hundreds of combinations of fields and values (like <code>dc.subject</code> and all the center subjects), and we can&rsquo;t use wildcards in REST!</li>
+<li>Reading about enabling multiple handle prefixes in DSpace</li>
+<li>There is a mailing list thread from 2011 about it: <a href="http://dspace.2283337.n4.nabble.com/Multiple-handle-prefixes-merged-DSpace-instances-td3427192.html">http://dspace.2283337.n4.nabble.com/Multiple-handle-prefixes-merged-DSpace-instances-td3427192.html</a></li>
+<li>And a comment from Atmire&rsquo;s Bram about it on the DSpace wiki: <a href="https://wiki.duraspace.org/display/DSDOC5x/Installing+DSpace?focusedCommentId=78163296#comment-78163296">https://wiki.duraspace.org/display/DSDOC5x/Installing+DSpace?focusedCommentId=78163296#comment-78163296</a></li>
+<li>Bram mentions an undocumented configuration option <code>handle.plugin.checknameauthority</code>, but I noticed another one in <code>dspace.cfg</code>:</li>
+</ul>
+
+<pre><code># List any additional prefixes that need to be managed by this handle server
+# (as for examle handle prefix coming from old dspace repository merged in
+# that repository)
+# handle.additional.prefixes = prefix1[, prefix2]
+</code></pre>
+
+<ul>
+<li>Because of this I noticed that our Handle server&rsquo;s <code>config.dct</code> was potentially misconfigured!</li>
+<li>We had some default values still present:</li>
+</ul>
+
+<pre><code>&quot;300:0.NA/YOUR_NAMING_AUTHORITY&quot;
+</code></pre>
+
+<ul>
+<li>I&rsquo;ve changed them to the following and restarted the handle server:</li>
+</ul>
+
+<pre><code>&quot;300:0.NA/10568&quot;
+</code></pre>
+
+<ul>
+<li>In looking at all the configs I just noticed that we are not providing a DOI in the Google-specific metadata crosswalk</li>
+<li>From <code>dspace/config/crosswalks/google-metadata.properties</code>:</li>
+</ul>
+
+<pre><code>google.citation_doi = cg.identifier.doi
+</code></pre>
+
+<ul>
+<li>This works, and makes DSpace output the following metadata on the item view page:</li>
+</ul>
+
+<pre><code>&lt;meta content=&quot;https://dx.doi.org/10.1186/s13059-017-1153-y&quot; name=&quot;citation_doi&quot;&gt;
+</code></pre>
+
+<ul>
+<li>Submitted and merged pull request for this: <a href="https://github.com/ilri/DSpace/pull/305">https://github.com/ilri/DSpace/pull/305</a></li>
 </ul>
 
   

public/index.xml

@@ -78,6 +78,14 @@ $ identify -format '%r\n' Africa\ group\ of\ negotiators.pdf\[0\]
 DirectClass sRGB Alpha
 </code></pre>
 
+<h2 id="2017-03-04">2017-03-04</h2>
+
+<ul>
+<li>Spent more time looking at the ImageMagick CMYK issue</li>
+<li>The <code>default_cmyk.icc</code> and <code>default_rgb.icc</code> files are both part of the Ghostscript GPL distribution, but according to DSpace’s <code>LICENSES_THIRD_PARTY</code> file, DSpace doesn’t allow distribution of dependencies that are licensed solely under the GPL</li>
+<li>So this issue is kinda pointless now, as the ICC profiles are absolutely necessary to make a meaningful CMYK→sRGB conversion</li>
+</ul>
+
 <h2 id="2017-03-05">2017-03-05</h2>
 
 <ul>
@@ -91,6 +99,50 @@ DirectClass sRGB Alpha
 
 <ul>
 <li>But there are hundreds of combinations of fields and values (like <code>dc.subject</code> and all the center subjects), and we can’t use wildcards in REST!</li>
+<li>Reading about enabling multiple handle prefixes in DSpace</li>
+<li>There is a mailing list thread from 2011 about it: <a href="http://dspace.2283337.n4.nabble.com/Multiple-handle-prefixes-merged-DSpace-instances-td3427192.html">http://dspace.2283337.n4.nabble.com/Multiple-handle-prefixes-merged-DSpace-instances-td3427192.html</a></li>
+<li>And a comment from Atmire’s Bram about it on the DSpace wiki: <a href="https://wiki.duraspace.org/display/DSDOC5x/Installing+DSpace?focusedCommentId=78163296#comment-78163296">https://wiki.duraspace.org/display/DSDOC5x/Installing+DSpace?focusedCommentId=78163296#comment-78163296</a></li>
+<li>Bram mentions an undocumented configuration option <code>handle.plugin.checknameauthority</code>, but I noticed another one in <code>dspace.cfg</code>:</li>
+</ul>
+
+<pre><code># List any additional prefixes that need to be managed by this handle server
+# (as for examle handle prefix coming from old dspace repository merged in
+# that repository)
+# handle.additional.prefixes = prefix1[, prefix2]
+</code></pre>
+
+<ul>
+<li>Because of this I noticed that our Handle server’s <code>config.dct</code> was potentially misconfigured!</li>
+<li>We had some default values still present:</li>
+</ul>
+
+<pre><code>"300:0.NA/YOUR_NAMING_AUTHORITY"
+</code></pre>
+
+<ul>
+<li>I’ve changed them to the following and restarted the handle server:</li>
+</ul>
+
+<pre><code>"300:0.NA/10568"
+</code></pre>
+
+<ul>
+<li>In looking at all the configs I just noticed that we are not providing a DOI in the Google-specific metadata crosswalk</li>
+<li>From <code>dspace/config/crosswalks/google-metadata.properties</code>:</li>
+</ul>
+
+<pre><code>google.citation_doi = cg.identifier.doi
+</code></pre>
+
+<ul>
+<li>This works, and makes DSpace output the following metadata on the item view page:</li>
+</ul>
+
+<pre><code><meta content="https://dx.doi.org/10.1186/s13059-017-1153-y" name="citation_doi">
+</code></pre>
+
+<ul>
+<li>Submitted and merged pull request for this: <a href="https://github.com/ilri/DSpace/pull/305">https://github.com/ilri/DSpace/pull/305</a></li>
 &lt;/ul&gt;</description>
     </item>
     

public/post/index.xml

@@ -78,6 +78,14 @@ $ identify -format '%r\n' Africa\ group\ of\ negotiators.pdf\[0\]
 DirectClass sRGB Alpha
 </code></pre>
 
+<h2 id="2017-03-04">2017-03-04</h2>
+
+<ul>
+<li>Spent more time looking at the ImageMagick CMYK issue</li>
+<li>The <code>default_cmyk.icc</code> and <code>default_rgb.icc</code> files are both part of the Ghostscript GPL distribution, but according to DSpace’s <code>LICENSES_THIRD_PARTY</code> file, DSpace doesn’t allow distribution of dependencies that are licensed solely under the GPL</li>
+<li>So this issue is kinda pointless now, as the ICC profiles are absolutely necessary to make a meaningful CMYK→sRGB conversion</li>
+</ul>
+
 <h2 id="2017-03-05">2017-03-05</h2>
 
 <ul>
@@ -91,6 +99,50 @@ DirectClass sRGB Alpha
 
 <ul>
 <li>But there are hundreds of combinations of fields and values (like <code>dc.subject</code> and all the center subjects), and we can’t use wildcards in REST!</li>
+<li>Reading about enabling multiple handle prefixes in DSpace</li>
+<li>There is a mailing list thread from 2011 about it: <a href="http://dspace.2283337.n4.nabble.com/Multiple-handle-prefixes-merged-DSpace-instances-td3427192.html">http://dspace.2283337.n4.nabble.com/Multiple-handle-prefixes-merged-DSpace-instances-td3427192.html</a></li>
+<li>And a comment from Atmire’s Bram about it on the DSpace wiki: <a href="https://wiki.duraspace.org/display/DSDOC5x/Installing+DSpace?focusedCommentId=78163296#comment-78163296">https://wiki.duraspace.org/display/DSDOC5x/Installing+DSpace?focusedCommentId=78163296#comment-78163296</a></li>
+<li>Bram mentions an undocumented configuration option <code>handle.plugin.checknameauthority</code>, but I noticed another one in <code>dspace.cfg</code>:</li>
+</ul>
+
+<pre><code># List any additional prefixes that need to be managed by this handle server
+# (as for examle handle prefix coming from old dspace repository merged in
+# that repository)
+# handle.additional.prefixes = prefix1[, prefix2]
+</code></pre>
+
+<ul>
+<li>Because of this I noticed that our Handle server’s <code>config.dct</code> was potentially misconfigured!</li>
+<li>We had some default values still present:</li>
+</ul>
+
+<pre><code>"300:0.NA/YOUR_NAMING_AUTHORITY"
+</code></pre>
+
+<ul>
+<li>I’ve changed them to the following and restarted the handle server:</li>
+</ul>
+
+<pre><code>"300:0.NA/10568"
+</code></pre>
+
+<ul>
+<li>In looking at all the configs I just noticed that we are not providing a DOI in the Google-specific metadata crosswalk</li>
+<li>From <code>dspace/config/crosswalks/google-metadata.properties</code>:</li>
+</ul>
+
+<pre><code>google.citation_doi = cg.identifier.doi
+</code></pre>
+
+<ul>
+<li>This works, and makes DSpace output the following metadata on the item view page:</li>
+</ul>
+
+<pre><code><meta content="https://dx.doi.org/10.1186/s13059-017-1153-y" name="citation_doi">
+</code></pre>
+
+<ul>
+<li>Submitted and merged pull request for this: <a href="https://github.com/ilri/DSpace/pull/305">https://github.com/ilri/DSpace/pull/305</a></li>
 &lt;/ul&gt;</description>
     </item>
     

public/sitemap.xml

@@ -3,7 +3,7 @@
   
   <url>
     <loc>https://alanorth.github.io/cgspace-notes/2017-03/</loc>
-    <lastmod>2017-03-04T01:15:47+02:00</lastmod>
+    <lastmod>2017-03-05T12:39:09+02:00</lastmod>
   </url>
   
   <url>
@@ -88,19 +88,19 @@
   
   <url>
     <loc>https://alanorth.github.io/cgspace-notes/</loc>
-    <lastmod>2017-03-04T01:15:47+02:00</lastmod>
+    <lastmod>2017-03-05T12:39:09+02:00</lastmod>
     <priority>0</priority>
   </url>
   
   <url>
     <loc>https://alanorth.github.io/cgspace-notes/tags/notes/</loc>
-    <lastmod>2017-03-04T01:15:47+02:00</lastmod>
+    <lastmod>2017-03-05T12:39:09+02:00</lastmod>
     <priority>0</priority>
   </url>
   
   <url>
     <loc>https://alanorth.github.io/cgspace-notes/post/</loc>
-    <lastmod>2017-03-04T01:15:47+02:00</lastmod>
+    <lastmod>2017-03-05T12:39:09+02:00</lastmod>
     <priority>0</priority>
   </url>
   

public/tags/notes/index.xml

@@ -77,6 +77,14 @@ $ identify -format '%r\n' Africa\ group\ of\ negotiators.pdf\[0\]
 DirectClass sRGB Alpha
 </code></pre>
 
+<h2 id="2017-03-04">2017-03-04</h2>
+
+<ul>
+<li>Spent more time looking at the ImageMagick CMYK issue</li>
+<li>The <code>default_cmyk.icc</code> and <code>default_rgb.icc</code> files are both part of the Ghostscript GPL distribution, but according to DSpace’s <code>LICENSES_THIRD_PARTY</code> file, DSpace doesn’t allow distribution of dependencies that are licensed solely under the GPL</li>
+<li>So this issue is kinda pointless now, as the ICC profiles are absolutely necessary to make a meaningful CMYK→sRGB conversion</li>
+</ul>
+
 <h2 id="2017-03-05">2017-03-05</h2>
 
 <ul>
@@ -90,6 +98,50 @@ DirectClass sRGB Alpha
 
 <ul>
 <li>But there are hundreds of combinations of fields and values (like <code>dc.subject</code> and all the center subjects), and we can’t use wildcards in REST!</li>
+<li>Reading about enabling multiple handle prefixes in DSpace</li>
+<li>There is a mailing list thread from 2011 about it: <a href="http://dspace.2283337.n4.nabble.com/Multiple-handle-prefixes-merged-DSpace-instances-td3427192.html">http://dspace.2283337.n4.nabble.com/Multiple-handle-prefixes-merged-DSpace-instances-td3427192.html</a></li>
+<li>And a comment from Atmire’s Bram about it on the DSpace wiki: <a href="https://wiki.duraspace.org/display/DSDOC5x/Installing+DSpace?focusedCommentId=78163296#comment-78163296">https://wiki.duraspace.org/display/DSDOC5x/Installing+DSpace?focusedCommentId=78163296#comment-78163296</a></li>
+<li>Bram mentions an undocumented configuration option <code>handle.plugin.checknameauthority</code>, but I noticed another one in <code>dspace.cfg</code>:</li>
+</ul>
+
+<pre><code># List any additional prefixes that need to be managed by this handle server
+# (as for examle handle prefix coming from old dspace repository merged in
+# that repository)
+# handle.additional.prefixes = prefix1[, prefix2]
+</code></pre>
+
+<ul>
+<li>Because of this I noticed that our Handle server’s <code>config.dct</code> was potentially misconfigured!</li>
+<li>We had some default values still present:</li>
+</ul>
+
+<pre><code>"300:0.NA/YOUR_NAMING_AUTHORITY"
+</code></pre>
+
+<ul>
+<li>I’ve changed them to the following and restarted the handle server:</li>
+</ul>
+
+<pre><code>"300:0.NA/10568"
+</code></pre>
+
+<ul>
+<li>In looking at all the configs I just noticed that we are not providing a DOI in the Google-specific metadata crosswalk</li>
+<li>From <code>dspace/config/crosswalks/google-metadata.properties</code>:</li>
+</ul>
+
+<pre><code>google.citation_doi = cg.identifier.doi
+</code></pre>
+
+<ul>
+<li>This works, and makes DSpace output the following metadata on the item view page:</li>
+</ul>
+
+<pre><code><meta content="https://dx.doi.org/10.1186/s13059-017-1153-y" name="citation_doi">
+</code></pre>
+
+<ul>
+<li>Submitted and merged pull request for this: <a href="https://github.com/ilri/DSpace/pull/305">https://github.com/ilri/DSpace/pull/305</a></li>
 &lt;/ul&gt;</description>
     </item>