diff --git a/content/2016-06.md b/content/2016-06.md
index 0f0221edb..55d01b3a4 100644
--- a/content/2016-06.md
+++ b/content/2016-06.md
@@ -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
diff --git a/public/2016-06/index.html b/public/2016-06/index.html
index 3ffcac1da..163f8ec73 100644
--- a/public/2016-06/index.html
+++ b/public/2016-06/index.html
@@ -113,6 +113,9 @@ UPDATE 14
- 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
diff --git a/public/index.xml b/public/index.xml
index d4b97c34a..7a92d58b8 100644
--- a/public/index.xml
+++ b/public/index.xml
@@ -358,6 +358,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’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>
diff --git a/public/tags/notes/index.xml b/public/tags/notes/index.xml
index 3d3b5372a..957e093f8 100644
--- a/public/tags/notes/index.xml
+++ b/public/tags/notes/index.xml
@@ -358,6 +358,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’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>