...
- Rachid Belkouch
- William Welling
- Benjamin Gross
- Brian Lowe
- Andrew Woods
- Don Elsborg
- Alexander (Sacha) Jerabek
- Huda Khan
...
- Three unassigned bugs need to get looked at.
- 1a. VIVO-1837: looks like there is a clear path forward
- Andrew wonders whether there is specific functionality (such as frontend decoupling) that will help surface and address some of these issues.
- William thinks a new dependency injection approach is required first in order to avoid perpetuating bad patterns on both sides of the decoupling.
- Huda has a good sense of where the cleavage points are for surfacing data to the API.
- Raises issues of setters/getters where things are not always set and you don’t know when to expect null.
- Brian will create an issue to review the newly-added RDFService.get/setVitroRequest() methods and ideally eliminate them.
- Other longer-term issues to address similar problems with tight coupling / undesirable references to other objects elsewhere in the codebase:
- Andrew wonders whether there is specific functionality (such as frontend decoupling) that will help surface and address some of these issues.
- William thinks a new dependency injection approach is required first in order to avoid perpetuating bad patterns on both sides of the decoupling. Huda has a good sense of where the cleavage points are for surfacing data to the API.
- 1b. Need to examine files that have been touched by both the sprint branch and recent core development to make sure that core changes have not been lost/reverted.
- 1c. Might be a matter of making sure that the initial RDF file loader recognizes the .nt (N-Triples) file extension and doesn’t try to parse as RDF/XML.
- Sacha: need to figure out how to address backlog of documentation tasks.
...