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
- Self-register at: http://bit.ly/vivo-slack
Attendees
Indicating note-taker
Agenda
- Questions/Issues/Pull requests/Announcements
- VIVO 1.13.0 release candidate -
- Release Testing - 1.13.0
- Release Notes
- https://github.com/vivo-project/Vitro/pull/296
- Also, 1.13.0 RC available at https://vivo.tib.eu/vivo113rc
- VIVO conference
- VIVO load issue - https://vivo-project.slack.com/archives/C8RL9L98A/p1655300922154729
- 3 tier build - https://vivo-project.slack.com/archives/C8SDQQYJ2/p1655317852767919
- VIVO 1.13.0 release candidate -
- Completed sprint
- 2022-06-21 - Dynamic API retrospective sprint meeting
- PRs reviews
- https://github.com/vivo-project/Vitro/pull/302 - Brian
- https://github.com/vivo-project/Vitro/pull/297 - William and Georgy
- https://github.com/vivo-project/Vitro/pull/306 - Veljko and William
- https://github.com/vivo-project/Vitro/pull/311 - Georgy and Veljko
- A problem with initially loaded data - https://vivo-project.slack.com/archives/C03DDJKA4SY/p1655749326711429
- https://github.com/vivo-project/Vitro/pull/310 - will be used for demo, but reorganized before merging, review is postponed
- https://github.com/vivo-project/Vitro-angular/pull/21 - William will talk with Mark how to reorganize contribution
- https://github.com/vivo-project/Vitro-angular/pull/22 (when it is ready) - Georgy and Dragan
- The next sprint
- When?
- What?
- Who?
- Summer vacation period
Notes
- Questions/Issues/Pull requests/Announcements
- VIVO 1.13.0 release candidate -
- Release Testing - 1.13.0
- Release Notes
- https://github.com/vivo-project/Vitro/pull/296
- Also, 1.13.0 RC available at https://vivo.tib.eu/vivo113rc
Vivo RC 13 had an error that Georgy noticed, and it should be fixed before the release. Other than that, feedback from the community was non-existent.
- VIVO conference
- VIVO load issue - https://vivo-project.slack.com/archives/C8RL9L98A/p1655300922154729
Brian: Indexing is a few magnitudes slower than it should be. The Sparql query itself works as fast as expected. Loading of 1.2 million triples triggered this slow indexing. Tbox extensions that were present when this issue popped up will be also added, so that the problem will be easier to recreate.
- Completed sprint
- Questions/Issues/Pull requests/Announcements
Dragan: The sprint was successful, and people were motivated to finish their features. The bad is that PR’s created at the end of the sprint were not reviewed and the sprint wasnt properly closed as everyone was focused on finishing their tasks throughout the entire sprint. Also, onboarding new members to the community isn't easy. 50-60% of tasks were finished, the base project for UI is setup, there is login endpoint, conditional steps, and crud operations.
This one is already merged
- https://github.com/vivo-project/Vitro/pull/297 - William and Georgy
This PR probably needs to be decomposed to smaller PRs as it is 25+ new files long
- https://github.com/vivo-project/Vitro/pull/306 - Veljko and William
Tests for SPARQL operation. If additional tests are needed, they should be implemented in new issue/PR, and this PR should be merged
- https://github.com/vivo-project/Vitro/pull/311 - Georgy and Veljko
This PR contains n3 templates that represent dynamic actions for crud operations. It is useful for demonstration of what we have built so far, as well as development of the UI. The question is whether we want to use those n3 files and operations as test data or not, especially if we will change the structure of DynamicAPI components such as Parameters and OperationData, that would render these n3 files incorrect.
- Sprint planning
- August or September?
- Running into following sprint if we choose September. Dragan is available for both.
- Topic for next sprint?
Although only 2 sprints were planned for the DynamicAPI, we will probably need 2 more sprints, which means that data ingestion will have to be postponed for the next year.
- Who can participate? We’ll follow up in the next couple weeks.
- Work over summer
- Regular meetings over July, then biweekly meetings?
- Or biweekly for July and August
- For now the plan is to have biweekly meetings from July 15th-August 15th.
- Issue posted to vivo-tech
- https://groups.google.com/g/vivo-tech/c/0fyz7yRnJ9Y
- Why are they using v1.9?
Task List
Previous Tasks
- Dragan Ivanovic to open an issue for a reverse proxy (redirecting) - https://vivo-project.slack.com/archives/C8RL9L98A/p1651739159126489
- Dragan Ivanovic to contact Andrew Wood for resolving the issue with registration for the Slack channel
- All to consider participation in the sprint and if decide to participate to register for the sprint - link
- Dragan Ivanovic to send a require to add in the Leadership group agenda a topic for discussing Copyright owner in License
- All please help in filling this document - spreadsheet
- Dragan Ivanovic to create a draft version of a Google Spreadsheet document with labeled columns representing requirements and to share with committers
- Committers to review the structure of the document and to fill it with data for JS and CSS frameworks