Date
Call-in Information
Time: 10:00 am, Eastern Time (New York, GMT-04:00)
To join the online meeting:
https://lyrasis.zoom.us/j/84378615572?pwd=bGUxSjlyRTdjOGl5U1B6L0Yva3RQdz09
Meeting ID: 843 7861 5572
Passcode: 556561
One tap mobile
+16699006833,,84378615572#,,,,*556561# US (San Jose)
+19292056099,,84378615572#,,,,*556561# US (New York)Dial by your location
+1 669 900 6833 US (San Jose)
+1 929 205 6099 US (New York)
+1 253 215 8782 US (Tacoma)
+1 301 715 8592 US (Washington DC)
+1 312 626 6799 US (Chicago)
+1 346 248 7799 US (Houston)
877 853 5257 US Toll-free
888 475 4499 US Toll-free
Meeting ID: 843 7861 5572
Passcode: 556561
Find your local number: https://lyrasis.zoom.us/u/kerqtGDrJ4
Slack
- https://vivo-project.slack.com
- Self-register at: http://bit.ly/vivo-slack
Attendees
Resources
Agenda
- Organization improvements
- Tickets - https://github.com/orgs/vivo-project/projects/2/views/1
- Ontology
- REST endpoint
- Action execution
- Testing strategy
- Blockers
- PRs - https://github.com/vivo-project/Vitro/pulls
- Documentation - VIVO Dynamic API
Notes
- Dragan Ivanovic it is still not clear how input and output of a dynamic action will look like and be handled. William Welling Some idea is to support flat structure for the input, but not sure it is the most elegant way for API users to provide data. Dragan Ivanovic : Let's try to reconsider our decision and to investigate how to support more structured input data. Dragan Ivanovic will try to design a solution.
- Kevin Day has presented the testing strategy. It should cover integration tests, however it is request scope, not context scope. Not perfect, but a big improvement and good enough for the needs of Vitro/VIVO. The implementation of tests would be much easier if we have an integrated spring framework. Kevin Day presented this strategy on the example of RCPEndpointIntegrationTest. Not real test, because RCP endpoint is not capable to accept and produce real data at the moment. The testing strategy has been approved.
- William Welling is not sure which approach should be applied for implementation of REST endpoints for custom REST actions. Namely, it is usually implemented to support only POST methods, and basically custom rest actions are forwarding requests to RCP endpoints which support only POST methods. However, there is hasDefaultHTTPMethod data property in the customRESTAction RDF class, and probably Georgy Litvinov had something on top of his mind when he defined that. Dragan Ivanovic thinks it is not clear how those custom REST actions will be used, not sure how often it will be used, and probably is not a high priority feature to be supported. Therefore, if we don’t have a clear picture for what purpose those actions will be used, it is not easy to select the right approach at the moment. The team concluded to keep current implementation while waiting for clarification from Georgy Litvinov or receiving needs requests from the Vitro/VIVO community.
- Benjamin Kampe is working on ChangeActionListener, and there is progress.
- Matthias Lühr is working on the definition of real case studies for using dynamic api. William Welling : please inform us when there is some progress, it would be nice to use more expressive example for testing our approach.
- Veljko Maksimovic is close to complete the SolrOperation componente, and already started analyzing how to implement N3Operation. It would be helpful if someone could introduce Veljko Maksimovic in the structure of the module which is executing N3 templates in Vitro/VIVO to speed up the implementation of N3Operation. Brian Lowe Benjamin Gross or Huda Khan might be the right persons to give directions. Veljko Maksimovic will contact them via Slack.
