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
VM created one N3Template related PR (https://github.com/vivo-project/Vitro/pull/286) which is ready for review. GL already performed a review and provided some comments.
DI has almost completed converting JSON to OperationData and creation of a JSON response in accordance with description of provided parameters (and types) in the rdf description of an action. Tests are failing, WW will help to fix tests or any other issues with this PR.
WW and KD have made progress in generating YAML files, but not yet ready for a review.
GL will review open PRs and analyze what is merged in the last couple of days, and continue implementation of computation of parameter scopes.
ML is working on description of real use cases in the form of dynamic action. ML asked how to test when define some dynamic action. WW: one solution is by writing and running integration tests, the other is to run VIVO/Vitro and generate a http request (curl, Postman, etc.). DI: if VIVO should be started, Initializer startup listener should be added in the startup_listener.txt of the VIVO application. GL: if Vitro should be started, Vitro-languages should be fetched, and installer/webapp pom.xml file should be adjusted (packaging should be war instead of pom - https://github.com/vivo-project/Vitro/pull/269/commits/af0e28455628d204b20850175b7ab4a84906ea43)
