diff --git a/content/2016-02.md b/content/2016-02.md
index 9931a8635..4210641c9 100644
--- a/content/2016-02.md
+++ b/content/2016-02.md
@@ -263,3 +263,11 @@ Bitstream: tést señora alimentación.pdf
- Seems it could be something with the HFS+ filesystem actually, as it's not UTF-8 ([it's something like UCS-2](http://www.cio.com/article/2868393/linus-torvalds-apples-hfs-is-probably-the-worst-file-system-ever.html))
- HFS+ stores filenames as a string, and filenames with accents get stored as [character+accent](https://blog.vrypan.net/2012/11/13/hfsplus-unicode-and-accented-chars/) whereas Linux's ext4 stores them as an array of bytes
- Running the SAFBuilder on Mac OS X works if you're going to import the resulting bundle on Mac OS X, but if your DSpace is running on Linux you need to run the SAFBuilder there where the filesystem's encoding matches
+
+## 2016-02-29
+
+- Got notified by some CIFOR colleagues that the Google Scholar team had contacted them about CGSpace's incorrect ordering of authors in Google Scholar metadata
+- Turns out there is a patch, and it was merged in DSpace 5.4: https://jira.duraspace.org/browse/DS-2679
+- I've merged it into our `5_x-prod` branch that is currently based on DSpace 5.1
+- We found a bug when a user searches from the homepage, sorts the results, and then tries to click "View More" in a sidebar facet
+- I am not sure what causes it yet, but I opened an issue for it: https://github.com/ilri/DSpace/issues/179
diff --git a/public/2016-02/index.html b/public/2016-02/index.html
index 913b2859f..969ca0d05 100644
--- a/public/2016-02/index.html
+++ b/public/2016-02/index.html
@@ -377,6 +377,16 @@ Bitstream: tést señora alimentación.pdf
Seems it could be something with the HFS+ filesystem actually, as it’s not UTF-8 (it’s something like UCS-2)
HFS+ stores filenames as a string, and filenames with accents get stored as character+accent whereas Linux’s ext4 stores them as an array of bytes
Running the SAFBuilder on Mac OS X works if you’re going to import the resulting bundle on Mac OS X, but if your DSpace is running on Linux you need to run the SAFBuilder there where the filesystem’s encoding matches
+
+
+2016-02-29
+
+
+- Got notified by some CIFOR colleagues that the Google Scholar team had contacted them about CGSpace’s incorrect ordering of authors in Google Scholar metadata
+- Turns out there is a patch, and it was merged in DSpace 5.4: https://jira.duraspace.org/browse/DS-2679
+- I’ve merged it into our
5_x-prod branch that is currently based on DSpace 5.1
+- We found a bug when a user searches from the homepage, sorts the results, and then tries to click “View More” in a sidebar facet
+- I am not sure what causes it yet, but I opened an issue for it: https://github.com/ilri/DSpace/issues/179
diff --git a/public/index.xml b/public/index.xml
index 80fa65dc8..09b251516 100644
--- a/public/index.xml
+++ b/public/index.xml
@@ -316,6 +316,16 @@ Bitstream: tést señora alimentación.pdf
<li>HFS+ stores filenames as a string, and filenames with accents get stored as <a href="https://blog.vrypan.net/2012/11/13/hfsplus-unicode-and-accented-chars/">character+accent</a> whereas Linux’s ext4 stores them as an array of bytes</li>
<li>Running the SAFBuilder on Mac OS X works if you’re going to import the resulting bundle on Mac OS X, but if your DSpace is running on Linux you need to run the SAFBuilder there where the filesystem’s encoding matches</li>
</ul>
+
+<h2 id="2016-02-29:124a59adbaa8ef13e1518d003fc03981">2016-02-29</h2>
+
+<ul>
+<li>Got notified by some CIFOR colleagues that the Google Scholar team had contacted them about CGSpace’s incorrect ordering of authors in Google Scholar metadata</li>
+<li>Turns out there is a patch, and it was merged in DSpace 5.4: <a href="https://jira.duraspace.org/browse/DS-2679">https://jira.duraspace.org/browse/DS-2679</a></li>
+<li>I’ve merged it into our <code>5_x-prod</code> branch that is currently based on DSpace 5.1</li>
+<li>We found a bug when a user searches from the homepage, sorts the results, and then tries to click “View More” in a sidebar facet</li>
+<li>I am not sure what causes it yet, but I opened an issue for it: <a href="https://github.com/ilri/DSpace/issues/179">https://github.com/ilri/DSpace/issues/179</a></li>
+</ul>
diff --git a/public/tags/notes/index.xml b/public/tags/notes/index.xml
index 011944cc7..d0e69f2c8 100644
--- a/public/tags/notes/index.xml
+++ b/public/tags/notes/index.xml
@@ -316,6 +316,16 @@ Bitstream: tést señora alimentación.pdf
<li>HFS+ stores filenames as a string, and filenames with accents get stored as <a href="https://blog.vrypan.net/2012/11/13/hfsplus-unicode-and-accented-chars/">character+accent</a> whereas Linux’s ext4 stores them as an array of bytes</li>
<li>Running the SAFBuilder on Mac OS X works if you’re going to import the resulting bundle on Mac OS X, but if your DSpace is running on Linux you need to run the SAFBuilder there where the filesystem’s encoding matches</li>
</ul>
+
+<h2 id="2016-02-29:124a59adbaa8ef13e1518d003fc03981">2016-02-29</h2>
+
+<ul>
+<li>Got notified by some CIFOR colleagues that the Google Scholar team had contacted them about CGSpace’s incorrect ordering of authors in Google Scholar metadata</li>
+<li>Turns out there is a patch, and it was merged in DSpace 5.4: <a href="https://jira.duraspace.org/browse/DS-2679">https://jira.duraspace.org/browse/DS-2679</a></li>
+<li>I’ve merged it into our <code>5_x-prod</code> branch that is currently based on DSpace 5.1</li>
+<li>We found a bug when a user searches from the homepage, sorts the results, and then tries to click “View More” in a sidebar facet</li>
+<li>I am not sure what causes it yet, but I opened an issue for it: <a href="https://github.com/ilri/DSpace/issues/179">https://github.com/ilri/DSpace/issues/179</a></li>
+</ul>