diff --git a/content/2016-03.md b/content/2016-03.md
index f5670f250..611e7466f 100644
--- a/content/2016-03.md
+++ b/content/2016-03.md
@@ -49,3 +49,9 @@ Exception in thread "Lucene Merge Thread #19" org.apache.lucene.index.MergePolic
- I did some major cleanup work on Discovery and XMLUI stuff related to the `dc.type` indexes ([#187](https://github.com/ilri/DSpace/pull/187))
- We had been confusing `dc.type` (a Dublin Core value) with `dc.type.output` (a value we invented) for a few years and it had permeated all aspects of our data, indexes, item displays, etc.
- There is still some more work to be done to remove references to old `outputtype` and `output`
+
+## 2016-03-14
+
+- Fix some items that had invalid dates (I noticed them in the log during a re-indexing)
+- Reset `search.index.*` to the default, as it is only used by Lucene (deprecated by Discovery in DSpace 5.x): [#188](https://github.com/ilri/DSpace/pull/188)
+- Make titles in Discovery and Browse by more consistent (singular, sentence case, etc)
diff --git a/public/2016-03/index.html b/public/2016-03/index.html
index 01e7fbec9..d1db764ae 100644
--- a/public/2016-03/index.html
+++ b/public/2016-03/index.html
@@ -132,6 +132,14 @@
I did some major cleanup work on Discovery and XMLUI stuff related to the dc.type
indexes (#187)
We had been confusing dc.type
(a Dublin Core value) with dc.type.output
(a value we invented) for a few years and it had permeated all aspects of our data, indexes, item displays, etc.
There is still some more work to be done to remove references to old outputtype
and output
+
+
+2016-03-14
+
+
+- Fix some items that had invalid dates (I noticed them in the log during a re-indexing)
+- Reset
search.index.*
to the default, as it is only used by Lucene (deprecated by Discovery in DSpace 5.x): #188
+- Make titles in Discovery and Browse by more consistent (singular, sentence case, etc)
diff --git a/public/index.xml b/public/index.xml
index 8c40c0233..0e6e131fd 100644
--- a/public/index.xml
+++ b/public/index.xml
@@ -71,6 +71,14 @@
<li>We had been confusing <code>dc.type</code> (a Dublin Core value) with <code>dc.type.output</code> (a value we invented) for a few years and it had permeated all aspects of our data, indexes, item displays, etc.</li>
<li>There is still some more work to be done to remove references to old <code>outputtype</code> and <code>output</code></li>
</ul>
+
+<h2 id="2016-03-14:5a28ddf3ee658c043c064ccddb151717">2016-03-14</h2>
+
+<ul>
+<li>Fix some items that had invalid dates (I noticed them in the log during a re-indexing)</li>
+<li>Reset <code>search.index.*</code> to the default, as it is only used by Lucene (deprecated by Discovery in DSpace 5.x): <a href="https://github.com/ilri/DSpace/pull/188">#188</a></li>
+<li>Make titles in Discovery and Browse by more consistent (singular, sentence case, etc)</li>
+</ul>
diff --git a/public/tags/notes/index.xml b/public/tags/notes/index.xml
index fd29b154a..6217b41e3 100644
--- a/public/tags/notes/index.xml
+++ b/public/tags/notes/index.xml
@@ -71,6 +71,14 @@
<li>We had been confusing <code>dc.type</code> (a Dublin Core value) with <code>dc.type.output</code> (a value we invented) for a few years and it had permeated all aspects of our data, indexes, item displays, etc.</li>
<li>There is still some more work to be done to remove references to old <code>outputtype</code> and <code>output</code></li>
</ul>
+
+<h2 id="2016-03-14:5a28ddf3ee658c043c064ccddb151717">2016-03-14</h2>
+
+<ul>
+<li>Fix some items that had invalid dates (I noticed them in the log during a re-indexing)</li>
+<li>Reset <code>search.index.*</code> to the default, as it is only used by Lucene (deprecated by Discovery in DSpace 5.x): <a href="https://github.com/ilri/DSpace/pull/188">#188</a></li>
+<li>Make titles in Discovery and Browse by more consistent (singular, sentence case, etc)</li>
+</ul>