diff --git a/content/2016-06.md b/content/2016-06.md index a358d9eb5..0f0221edb 100644 --- a/content/2016-06.md +++ b/content/2016-06.md @@ -23,3 +23,15 @@ UPDATE 14 ``` - Fix a few minor miscellaneous issues in `dspace.cfg` ([#227](https://github.com/ilri/DSpace/pull/227)) + +## 2016-06-02 + +- Testing the configuration and theme changes for the upcoming metadata migration and I found some issues with `cg.coverage.admin-unit` +- Seems that the Browse configuration in `dspace.cfg` can't handle the '-' in the field name: + +``` +webui.browse.index.12 = subregion:metadata:cg.coverage.admin-unit:text +``` + +- But actually, I think since DSpace 4 or 5 (we are 5.1) the Browse indexes come from Discovery (defined in discovery.xml) so this is really just a parsing error +- I've sent a message to the DSpace mailing list to ask about the Browse index definition diff --git a/public/2016-06/index.html b/public/2016-06/index.html index dd733d7fc..3ffcac1da 100644 --- a/public/2016-06/index.html +++ b/public/2016-06/index.html @@ -98,6 +98,21 @@ UPDATE 14 + +

2016-06-02

+ + + +
webui.browse.index.12 = subregion:metadata:cg.coverage.admin-unit:text
+
+ + diff --git a/public/index.xml b/public/index.xml index 5ebf53069..d4b97c34a 100644 --- a/public/index.xml +++ b/public/index.xml @@ -344,6 +344,21 @@ UPDATE 14 <ul> <li>Fix a few minor miscellaneous issues in <code>dspace.cfg</code> (<a href="https://github.com/ilri/DSpace/pull/227">#227</a>)</li> </ul> + +<h2 id="2016-06-02:6783872e82b68b1517e00f494e6b6504">2016-06-02</h2> + +<ul> +<li>Testing the configuration and theme changes for the upcoming metadata migration and I found some issues with <code>cg.coverage.admin-unit</code></li> +<li>Seems that the Browse configuration in <code>dspace.cfg</code> can&rsquo;t handle the &lsquo;-&rsquo; in the field name:</li> +</ul> + +<pre><code>webui.browse.index.12 = subregion:metadata:cg.coverage.admin-unit:text +</code></pre> + +<ul> +<li>But actually, I think since DSpace 4 or 5 (we are 5.1) the Browse indexes come from Discovery (defined in discovery.xml) so this is really just a parsing error</li> +<li>I&rsquo;ve sent a message to the DSpace mailing list to ask about the Browse index definition</li> +</ul> diff --git a/public/tags/notes/index.xml b/public/tags/notes/index.xml index 46581014d..3d3b5372a 100644 --- a/public/tags/notes/index.xml +++ b/public/tags/notes/index.xml @@ -344,6 +344,21 @@ UPDATE 14 <ul> <li>Fix a few minor miscellaneous issues in <code>dspace.cfg</code> (<a href="https://github.com/ilri/DSpace/pull/227">#227</a>)</li> </ul> + +<h2 id="2016-06-02:6783872e82b68b1517e00f494e6b6504">2016-06-02</h2> + +<ul> +<li>Testing the configuration and theme changes for the upcoming metadata migration and I found some issues with <code>cg.coverage.admin-unit</code></li> +<li>Seems that the Browse configuration in <code>dspace.cfg</code> can&rsquo;t handle the &lsquo;-&rsquo; in the field name:</li> +</ul> + +<pre><code>webui.browse.index.12 = subregion:metadata:cg.coverage.admin-unit:text +</code></pre> + +<ul> +<li>But actually, I think since DSpace 4 or 5 (we are 5.1) the Browse indexes come from Discovery (defined in discovery.xml) so this is really just a parsing error</li> +<li>I&rsquo;ve sent a message to the DSpace mailing list to ask about the Browse index definition</li> +</ul>