Date

16 Feb 2022

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

1. Dragan Ivanovic 
2. Benjamin Kampe 
3. Matthias Lühr 
4. Veljko Maksimovic 
5. Georgy Litvinov 
6. Brian Lowe 
7. William Welling 
8. Kevin Day 
9. Benjamin Gross 

Resources

• Sprint board
• 2022-02 Sprint Stand-up Reports

Agenda

1. Goals:

   1. Surface any fundamental issues

2. Sprint logistics / scheduling

   1. Daily stand-up report in Slack - #dynamic-api-sprint-february-2022 channel
   2. Regional kickoffs for: final ticket assignments, dev env setup, dev process, etc
      1. European kick-off meeting: 9am CET - same Zoom
      2. North American kick-off meeting: 10am ET - same Zoom
3. Tools and resources 
   1. Branches
   2. Test datasets
   3. General, manual tests
   4. Development processes
      1. Git / GitHub processes
      2. GitHub issues process
   5. Dev environment... please take as first task to establish this

4. Tickets - https://github.com/orgs/vivo-project/projects/2/views/1

5. Documentation - VIVO Dynamic API

Slack stand-up template

Notes 

Key discussion points:

1. Custom action endpoint request body

1. initially accept application/json
2. use of rdf content types open for future planning

1. use rdf model for context (inputs and outputs) throughout action

1. earlier preparation could be transform of json to rdf using blank nodes (@Brian Lowe can describe better)
2. deferred for future planning

1. Block vs Non-blocking custom action endpoint

1. ability to run action asynchronously for long running actions

1. Action and Step context scope

1. @Georgy has some ideas on how to afford/improve
2. some construct defining which steps require which context values

1. allow for cleanup of context values no longer needed

1. is considered for development this sprint

1. Meta Actions

1. @Georgy has some ideas on how to ensure extensibility to afford meta actions
2. implementation deferred for future planning

1. Thread safety

1. Currently request thread perform entire action
2. Is there a need for better thread management?
3. Is there a need for action and/or step queue?
4. Possibility of Action and/or step running on independent threads
5. Are ActionPool and ResourcePool thread safe?

1. Testing

1. @Kevin Day and myself (@William Welling) will have PRs for review either on start of sprint or shortly after

1. Availability

1. @Brian Lowe will have low availability until week two of sprint
2. @Georgy will have low availability at beginning of sprint
3. @Kevin Day will be selecting issue Monday, likely relating to endpoints as was the focus of his testing work
4. @William Welling will be selecting issue Monday, likely related to ActionPool and ResourcePool as is the focus of my testing work