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
- Dragan Ivanovic
- Benjamin Kampe
- Matthias Lühr
- Veljko Maksimovic
- Georgy Litvinov
- Brian Lowe
- William Welling
- Kevin Day
- Benjamin Gross
Resources
Agenda
Goals:
- Surface any fundamental issues
Sprint logistics / scheduling
- Daily stand-up report in Slack - #dynamic-api-sprint-february-2022 channel
- Regional kickoffs for: final ticket assignments, dev env setup, dev process, etc
- European kick-off meeting: 9am CET - same Zoom
- North American kick-off meeting: 10am ET - same Zoom
- Tools and resources
- Branches
- Test datasets
- General, manual tests
- Development processes
- Dev environment... please take as first task to establish this
Tickets - https://github.com/orgs/vivo-project/projects/2/views/1
Documentation - VIVO Dynamic API
Slack stand-up template
[VIVO Dynamic API Standup]
Finished yesterday:
{ticket titles and associated GitHub links}
{AND please include brief textual description}
Working on today:
{ticket titles and associated GitHub links}
{AND please include brief textual description}
Blockers:
{brief textual description}
Notes
Key discussion points:
- Custom action endpoint request body
- initially accept application/json
- use of rdf content types open for future planning
- use rdf model for context (inputs and outputs) throughout action
- earlier preparation could be transform of json to rdf using blank nodes (@Brian Lowe can describe better)
- deferred for future planning
- Block vs Non-blocking custom action endpoint
- ability to run action asynchronously for long running actions
- Action and Step context scope
- @Georgy has some ideas on how to afford/improve
- some construct defining which steps require which context values
- allow for cleanup of context values no longer needed
- is considered for development this sprint
- Meta Actions
- @Georgy has some ideas on how to ensure extensibility to afford meta actions
- implementation deferred for future planning
- Thread safety
- Currently request thread perform entire action
- Is there a need for better thread management?
- Is there a need for action and/or step queue?
- Possibility of Action and/or step running on independent threads
- Are ActionPool and ResourcePool thread safe?
- Testing
- @Kevin Day and myself (@William Welling) will have PRs for review either on start of sprint or shortly after
- Availability
- @Brian Lowe will have low availability until week two of sprint
- @Georgy will have low availability at beginning of sprint
- @Kevin Day will be selecting issue Monday, likely relating to endpoints as was the focus of his testing work
- @William Welling will be selecting issue Monday, likely related to ActionPool and ResourcePool as is the focus of my testing work