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

Attendees

(star)  Indicating note-taker

  1. Dragan Ivanovic 
  2. Georgy Litvinov
  3. Brian Lowe 
  4. Benjamin Kampe 
  5. Mark Vanin (star)
  6. Michel Héon 
  7. Veljko Maksimovic 

Agenda

  1. Questions/Issues/Pull requests/Announcements
    1. https://github.com/vivo-project/VIVO/pull/3724
      1. https://github.com/vivo-project/VIVO/issues/3723
    2. https://github.com/vivo-project/VIVO/pull/3725
      1. https://github.com/vivo-project/VIVO/issues/3717
    3. https://github.com/vivo-project/VIVO/issues/3726
    4. https://github.com/vivo-project/Vitro/pull/296
  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
          1. Continents and geographic locations
            1. labels loaded into one graph - https://github.com/vivo-project/VIVO/blob/main/home/src/main/resources/rdf/abox/firsttime/geopolitical.ver1.1-11-18-11-individual-labels.rdf
            2. types in the another graph - https://github.com/vivo-project/VIVO/blob/main/home/src/main/resources/rdf/abox/filegraph/continents.n3
          2. Us-states
            1. everything in one graph - https://github.com/vivo-project/VIVO/blob/main/home/src/main/resources/rdf/abox/filegraph/us-states.rdf
      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. Demo meeting 
      1. When
        1. 07.07.2022. at 10am Eastern Time
      2. What
        1. Scenario???
      3. Who
        1. Dragan will present
  3. The next sprint
    1. When?
      1. 19.09. - 07.10. ???
    2. What?
    3. Who?
  4. Summer vacation period
    1. 05, 12, 26 of July, 2022
    2. 09, 23, 30 of August, 2022

Notes

Georgy contribution for publishing minor release:

  • Georgy fixed a small bug with language duplication in i18n. Was applied to vivo.tib.eu/vivo113rc.
  • From hardcoded xsd:string to rdf:langString, where you can decide the values. Also applied to vivo.tib.eu/vivo113rc
  • Basically Georgy fixed bugs left from internalization (i18n) sprint.

If Georgy’s merge requests would be merged, Dragan could start making the release candidate 2. Non-developers are very welcome to test merge requests above.

Sprint demo

How should we organize, that labels of some geolocations, continents are not in the same file, not for every (USA every information in one file). 

  • Georgy: we are able to use models even now, like temporary models. 
  • Dragan: when you have everything in one file you could use relative path to model and not full model every time. Can’t use full union for entry deletions.

What could be demonstrated (preferable): 

  • CRUD operations;
  • Frontend part with dynamic api;
  • Is it a good part to add some dynamic action endpoint, that is not valid (question?)

From 12 July to 23 August we would have biweekly spring, from 23 August regular one week sprints.

3rd Sprint in 2022, maybe from 19.09 to 07.10 - main idea to continue with dynamic api. 

Consider dates of sprint, due to usual summer vacations

Draft notes in Google Docs

Task List

Previous Tasks 

  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.