alanorth/cgspace-notes
1
0
Fork 0
mirror of https://github.com/alanorth/cgspace-notes.git synced 2024-12-22 13:12:19 +01:00
Code Issues Projects Releases Wiki Activity

Add notes for 2019-11-27

Browse Source
This commit is contained in:
Alan Orth 2019-11-27 14:56:00 +02:00
parent f74c7223d6
commit 1f2be05583
Signed by: alanorth
GPG Key ID: 0FB860CC9C45B1B9
3 changed files with 51 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
content/posts/2019-11.md
View File

@ -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: -->

33
docs/2019-11/index.html
View File

@ -34,7 +34,7 @@ Let&rsquo;s see how many of the REST API requests were for bitstreams (because t
<meta property="og:type" content="article" />
<meta property="og:url" content="https://alanorth.github.io/cgspace-notes/2019-11/" />
<meta property="article:published_time" content="2019-11-04T12:20:30+02:00" />
<meta property="article:modified_time" content="2019-11-25T10:21:13+02:00" />
<meta property="article:modified_time" content="2019-11-26T15:53:57+02:00" />
<meta name="twitter:card" content="summary"/>
<meta name="twitter:title" content="November, 2019"/>
@ -73,9 +73,9 @@ Let&rsquo;s see how many of the REST API requests were for bitstreams (because t
"@type": "BlogPosting",
"headline": "November, 2019",
"url": "https:\/\/alanorth.github.io\/cgspace-notes\/2019-11\/",
"wordCount": "3212",
"wordCount": "3381",
"datePublished": "2019-11-04T12:20:30+02:00",
"dateModified": "2019-11-25T10:21:13+02:00",
"dateModified": "2019-11-26T15:53:57+02:00",
"author": {
"@type": "Person",
"name": "Alan Orth"
@ -714,6 +714,33 @@ $ tidy -xml -utf8 -iq -m -w 0 dspace/config/controlled-vocabularies/cg-creator-i
</ul></li>
</ul>
<h2 id="2019-11-27">2019-11-27</h2>
<ul>
<li>Minor updates on the <a href="https://github.com/ilri/dspace-statistics-api">dspace-statistics-api</a>
<ul>
<li>Introduce isort for import sorting</li>
<li>Introduce black for code formatting according to PEP8</li>
<li>Fix some minor issues raised by flake8</li>
<li>Release <a href="https://github.com/ilri/dspace-statistics-api/releases/tag/v1.1.1">version 1.1.1</a> and deploy to DSpace Test (linode19)</li>
<li>I realize that I never deployed version 1.1.0 (with falcon 2.0.0) on CGSpace (linode18) so I did that as well</li>
</ul></li>
<li>File a ticket (242418) with Altmetric about DCTERMS migration to see if there is anything we need to be careful about</li>
<li>Make a pull request against cg-core schema to fix inconsistent references to <code>cg.embargoDate</code> (<a href="https://github.com/AgriculturalSemantics/cg-core/pull/13">#13</a>)</li>
<li>Review the AReS feedback again after Peter made some comments
<ul>
<li>I standardized the GitHub issue labels in both OpenRXV and AReS issue trackers, using labels like &ldquo;P-low&rdquo; for priority</li>
<li>I filed another handful of issues in both trackers and added them to the spreadsheet</li>
</ul></li>
<li>I need to ask Marie-Angelique about the <code>cg.peer-reviewed</code> field
<ul>
<li>We currently use <code>dc.description.version</code> with values like &ldquo;Internal Review&rdquo; and &ldquo;Peer Review&rdquo;, and CG Core v2 currently recommends using &ldquo;True&rdquo; if the field is peer reviewed</li>
</ul></li>
</ul>
<!-- vim: set sw=2 ts=2: -->

10
docs/sitemap.xml
View File

@ -4,27 +4,27 @@
<url>
<loc>https://alanorth.github.io/cgspace-notes/categories/</loc>
<lastmod>2019-11-25T10:21:13+02:00</lastmod>
<lastmod>2019-11-26T15:53:57+02:00</lastmod>
</url>
<url>
<loc>https://alanorth.github.io/cgspace-notes/</loc>
<lastmod>2019-11-25T10:21:13+02:00</lastmod>
<lastmod>2019-11-26T15:53:57+02:00</lastmod>
</url>
<url>
<loc>https://alanorth.github.io/cgspace-notes/categories/notes/</loc>
<lastmod>2019-11-25T10:21:13+02:00</lastmod>
<lastmod>2019-11-26T15:53:57+02:00</lastmod>
</url>
<url>
<loc>https://alanorth.github.io/cgspace-notes/2019-11/</loc>
<lastmod>2019-11-25T10:21:13+02:00</lastmod>
<lastmod>2019-11-26T15:53:57+02:00</lastmod>
</url>
<url>
<loc>https://alanorth.github.io/cgspace-notes/posts/</loc>
<lastmod>2019-11-25T10:21:13+02:00</lastmod>
<lastmod>2019-11-26T15:53:57+02:00</lastmod>
</url>
<url>