Add notes for 2019-11-27

content/posts/2019-11.md

@@ -449,4 +449,20 @@ Buck/2.2; (+https://app.hypefactors.com/media-monitoring/about.html)
   - I added GitHub issues for eight of the items so far, tagging them by "bug", "search", "feature", "graphics", "low-priority", etc
   - I moved AReS v2 to be available on CGSpace
 
+## 2019-11-27
+
+- Minor updates on the [dspace-statistics-api](https://github.com/ilri/dspace-statistics-api)
+  - Introduce isort for import sorting
+  - Introduce black for code formatting according to PEP8
+  - Fix some minor issues raised by flake8
+  - Release [version 1.1.1](https://github.com/ilri/dspace-statistics-api/releases/tag/v1.1.1) and deploy to DSpace Test (linode19)
+  - I realize that I never deployed version 1.1.0 (with falcon 2.0.0) on CGSpace (linode18) so I did that as well
+- File a ticket (242418) with Altmetric about DCTERMS migration to see if there is anything we need to be careful about
+- Make a pull request against cg-core schema to fix inconsistent references to `cg.embargoDate` ([#13](https://github.com/AgriculturalSemantics/cg-core/pull/13))
+- Review the AReS feedback again after Peter made some comments
+  - I standardized the GitHub issue labels in both OpenRXV and AReS issue trackers, using labels like "P-low" for priority
+  - I filed another handful of issues in both trackers and added them to the spreadsheet
+- I need to ask Marie-Angelique about the `cg.peer-reviewed` field
+  - We currently use `dc.description.version` with values like "Internal Review" and "Peer Review", and CG Core v2 currently recommends using "True" if the field is peer reviewed
+
 <!-- vim: set sw=2 ts=2: -->