Date

Call-in Information

Time: 10:00 am, Eastern Daylight Time (New York), 4pm Central European Summer Time

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

Calendar invitation - ICS file

Slack

Attendees

(star)  Indicating note-taker

  1. Dragan Ivanovic (star) 
  2. Brian Lowe 
  3. Georgy Litvinov  
  4. Ivan Mrsulja 
  5. Miloš Popović 
  6. Santhosh Anand Ramia

Agenda

Notes 

VIVO - ElasticSearch integration

Dragan expressed uncertainty about the specific benefits and challenges of this switch, and clear specification of VIVO customers' expectations. However, the issue of replacing Solr with ElasticSearch has been mentioned a couple of times in the recent period. Dragan discussed the potential replacement of Solr with ElasticSearch for the Brazilian team's in-house solution. He suggested that this change could simplify their architecture (https://brcris.ibict.br/en/about), potentially reducing issues with resource management and server monitoring. However, he also noted that this decision to replace Solr with ElasticSearch might be driven by a preference for some VIVO customers. Dragan and Ivan discussed the implementation of a search engine and the testing of an older version of an API. Ivan agreed to test the system with version 7.0 and update the configuration accordingly. Dragan suggested that Ivan include instructions on how to test the system in the description of pull request (https://github.com/vivo-project/Vitro/pull/469). 

VIVO 1.14.3

The release candidate was tested by both Dragan and Christian. It has been released. 

VIVO demo site

Dragan proposed the idea of establishing a demo site for the current version of VIVO, to replace the https://openvivo.org/, which is no longer fully functional. He hopes that this site could be hosted by Lyrasis and could include a continuous integration approach (synchronization with main branch and reloading data). However, Brian expressed concerns about maintaining a continuously integrated demo site and suggested instead having two sites - one for promotional purposes with the latest stable release and another for testing purposes. Dragan agreed to discuss these ideas with the relevant Lyrasis team members and update Brian on the progress. 

VIVO 1.15.0

Dragan reported progress on VIVO 1.15.0, with plans to soon close all pull requests, which included 47 tickets. He highlighted the need to update documentation and prepare a Google form for collecting test results, specifically for testing new features. Dragan expressed his hope to publish something before the summer break, which is likely to occur from mid-July to mid-August. An approach from the previous year, where bi-weekly calls were held during the summer break, was suggested as a potential solution.

Draft notes in Google Docs

Task List

  • Dragan Ivanovic to coordinate the VIVO 1.15.0 documentation update
  • Ivan Mrsulja to test the Elasticsearch integration with Vivo 1.15.0 using ElasticSearch version 7.0 and provide an update on the testing process in the PR description
  • Dragan Ivanovic to discuss with the Lyrasis team the potential for having separate demo and testing sites for VIVO

Previous Tasks 

  • Dragan Ivanovic to add columns in the project board for Priority and Difficulty.
  • Sprint participants to read description of issues and think about their preferences. 
  • No labels

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