Versions Compared

Old Version 4

changes.mady.by.user Benjamin Gross

Saved on

compared with

New Version Current

changes.mady.by.user Dragan Ivanovic

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Questions/Issues/Pull requests/Announcements
    1. VIVO 1.13.0 release candidate -
      1. Release Testing - 1.13.0
      2. Release Notes
      3. https://github.com/vivo-project/Vitro/pull/296
      4. Also, 1.13.0 RC available at https://vivo.tib.eu/vivo113rc
    2. VIVO conference
    3. VIVO load issue - https://vivo-project.slack.com/archives/C8RL9L98A/p1655300922154729
    4. 3 tier build - https://vivo-project.slack.com/archives/C8SDQQYJ2/p1655317852767919
  2. Completed sprint
    1. 2022-06-21 - Dynamic API retrospective sprint meeting
    2. PRs reviews
      1. https://github.com/vivo-project/Vitro/pull/302 - Brian
      2. https://github.com/vivo-project/Vitro/pull/297 - William and Georgy
      3. https://github.com/vivo-project/Vitro/pull/306 - Veljko and William
      4. https://github.com/vivo-project/Vitro/pull/311 - Georgy and Veljko
        1. A problem with initially loaded data - https://vivo-project.slack.com/archives/C03DDJKA4SY/p1655749326711429
      5. https://github.com/vivo-project/Vitro/pull/310 - will be used for demo, but reorganized before merging, review is postponed
      6. https://github.com/vivo-project/Vitro-angular/pull/21 - William will talk with Mark how to reorganize contribution
      7. https://github.com/vivo-project/Vitro-angular/pull/22 (when it is ready) - Georgy and Dragan
  3. The next sprint
    1. When?
    2. What?
    3. Who?
  4. Summer vacation period

Notes

  • Publishing 1.13.
    • One PRGeorgy: There is a regression with new PR that creates a regression in editing of labels with string data types. We need to resolve the regression.
    • Brian: We might not have enough time to test it one more time https://vivo-project.atlassian.net/browse/VIVO-1983
    • Georgy: We need more testing


    1. Questions/Issues/Pull requests/Announcements

      1. VIVO 1.13.0 release candidate -
        1. Release Testing - 1.13.0
        2. Release Notes
        3. https://github.com/vivo-project/Vitro/pull/296
        4. Also, 1.13.0 RC available athttps://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.

    1. VIVO conference
    2. 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.

    1. Completed sprint

  • 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.

    1. 2022-06-21 - Dynamic API retrospective sprint meeting
    2. PRs reviews
      1. https://github.com/vivo-project/Vitro/pull/302 - Brian 

    This one is already merged

    1. 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

    1. 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

    1. 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

  • Deletion needs more documentation
  • Jena issue. We need to create a ticket for Jena

    .

  • 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

Draft notes in Google Docs

...