mirror of
https://github.com/alanorth/cgspace-notes.git
synced 2025-01-27 05:49:12 +01:00
Add notes for 2019-11-28
This commit is contained in:
@ -444,7 +444,7 @@ Buck/2.2; (+https://app.hypefactors.com/media-monitoring/about.html)
|
||||
|
||||
## 2019-11-26
|
||||
|
||||
- Visit CodeObie to discuss future of OpenRXV and AReS
|
||||
- Visit CodeObia to discuss future of OpenRXV and AReS
|
||||
- I started working on categorizing and validating the feedback that Jane collated into a spreadsheet last week
|
||||
- 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
|
||||
@ -465,4 +465,12 @@ Buck/2.2; (+https://app.hypefactors.com/media-monitoring/about.html)
|
||||
- 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
|
||||
|
||||
## 2019-11-28
|
||||
|
||||
- File an issue with CG Core v2 project to ask Marie-Angelique about expanding the scope of `cg.peer-reviewed` to include other types of review, and possibly to change the field name to something more generic like `cg.review-status` ([#14](https://github.com/AgriculturalSemantics/cg-core/issues/14))
|
||||
- More review of AReS feedback
|
||||
- I clarified some of the feedback
|
||||
- I added status of "Issue Filed", "Duplicate" and "No Action Required" to several items
|
||||
- I filed a handful more GitHub issues in AReS and OpenRXV GitHub trackers
|
||||
|
||||
<!-- vim: set sw=2 ts=2: -->
|
||||
|
Reference in New Issue
Block a user