Update notes for 2016-06-02

This commit is contained in:
Alan Orth 2016-06-02 14:55:43 +03:00
parent f01c86b4e9
commit 338415b9d9
Signed by: alanorth
GPG Key ID: 0FB860CC9C45B1B9
4 changed files with 12 additions and 0 deletions

View File

@ -35,3 +35,6 @@ 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
- A user was having problems with submission and from the stacktrace it looks like a Sherpa/Romeo issue
- I found a thread on the mailing list talking about it and there is bug report and a patch: https://jira.duraspace.org/browse/DS-2740
- The patch applies successfully on DSpace 5.1 so I will try it later

View File

@ -113,6 +113,9 @@ UPDATE 14
<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>
<li>A user was having problems with submission and from the stacktrace it looks like a Sherpa/Romeo issue</li>
<li>I found a thread on the mailing list talking about it and there is bug report and a patch: <a href="https://jira.duraspace.org/browse/DS-2740">https://jira.duraspace.org/browse/DS-2740</a></li>
<li>The patch applies successfully on DSpace 5.1 so I will try it later</li>
</ul>
</section>

View File

@ -358,6 +358,9 @@ UPDATE 14
&lt;ul&gt;
&lt;li&gt;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&lt;/li&gt;
&lt;li&gt;I&amp;rsquo;ve sent a message to the DSpace mailing list to ask about the Browse index definition&lt;/li&gt;
&lt;li&gt;A user was having problems with submission and from the stacktrace it looks like a Sherpa/Romeo issue&lt;/li&gt;
&lt;li&gt;I found a thread on the mailing list talking about it and there is bug report and a patch: &lt;a href=&#34;https://jira.duraspace.org/browse/DS-2740&#34;&gt;https://jira.duraspace.org/browse/DS-2740&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;The patch applies successfully on DSpace 5.1 so I will try it later&lt;/li&gt;
&lt;/ul&gt;
</description>
</item>

View File

@ -358,6 +358,9 @@ UPDATE 14
&lt;ul&gt;
&lt;li&gt;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&lt;/li&gt;
&lt;li&gt;I&amp;rsquo;ve sent a message to the DSpace mailing list to ask about the Browse index definition&lt;/li&gt;
&lt;li&gt;A user was having problems with submission and from the stacktrace it looks like a Sherpa/Romeo issue&lt;/li&gt;
&lt;li&gt;I found a thread on the mailing list talking about it and there is bug report and a patch: &lt;a href=&#34;https://jira.duraspace.org/browse/DS-2740&#34;&gt;https://jira.duraspace.org/browse/DS-2740&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;The patch applies successfully on DSpace 5.1 so I will try it later&lt;/li&gt;
&lt;/ul&gt;
</description>
</item>