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. William Welling
  3. Bridget Almas  
  4. Michel Héon 
  5. Benjamin Kampe 

Agenda

  • Conferences 
  • Issues
    • vivo-solr issue reported by Tom Misilio
      • docker - Solr 7.x (log4j)
    • Upload of images reported by Benjamin Gross 
      • " Anyone having trouble with image uploads with recent versions of VIVO? I'm getting these errors in the logs:

        2024-05-13 19:09:33,509 ERROR [FileInfo] File had no filename: 'https://researchers.mydomain.edu/individual/n23090'
        2024-05-13 19:09:33,510 INFO [FileServingServlet] Failed to serve the file at '/file/n50145/thumbnail_totoro.jpg' -- edu.cornell.mannlib.vitro.webapp.filestorage.serving.FileServingServlet$FileServingException: The request path is not valid for the File servlet: '/file/n50145/thumbnail_totoro.jpg'Images work if I'm logged in as an admin and do a hard refresh, otherwise they appear broken.

        Wondering if its somehow related to the new enhanced permissions rules?

        "
  • Depositing releases on Zenodo
  • #reviewers channel
    • increased number of members

Notes  

Dragan introduced Bridget Almas, the new director of operations for community-supported technologies at Lyrasis, who took over Lauri's role who should focus on higher-level issues. Bridget, a software developer with a background in open-source projects, offered to contribute her technical expertise to the Vivo project. Other members of the VIVO community introduced themselves.                            

CRIS 2024 conference

https://cris2024.eurocris.org/

Dragan briefly reported about the event with almost 200 participants. There were a couple of VIVO community members. The VIVO platform has been mentioned in a couple of presentations including the “VIVO new features” presentation presented by Dragan and Michelle Mennielli. Some event participants expressed the interest to join the VIVO community. 

vivo-solr issue 

This has been reported by Tom Misilio. The issue is linked with Docker which is running Solr 7.x which is using the log4j version affected by a security vulnerability. There is a branch which is mitigating this vulnerability - https://github.com/vivo-project/vivo-solr/commits/solr-8.11/. Dragan informed Tom about this branch. 

The Upload of images issue

The issue has been reported by Benjamin Gross via Slack. The issue might be linked with the new role management system.  Dragan will talk with Georgy about this. https://github.com/vivo-project/VIVO/issues/3987 

JIRA tickets links

Santhosh Anand Ramia reported broken links at https://wiki.lyrasis.org/display/VIVODOC111x/Release+Notes. JIRA tickets are in read only mode, because we switched to GitHub tickets in 2022. However, we need access to JIRA tickets for older versions of releases. The JIRA tickets were not public, Dragan fixed this. Santhosh confirmed this is fixed (accessible) now. 

Solr vs ElasticSearch

Dragan and Michele discussed whether Solr can be replaced with ElasticSearch. It should be possible and it might be that the University of Colorado (Don Elsborg) is using that. Dragan will try to contact Don to find more information. 

Depositing releases on Zenodo

Is there any sense in publishing VIVO releases also in Zenodo (not just in maven repository and in GitHub). There is some sense in terms of citation and assigning DOI. Dragan investigate integration of github and Zenodo for automatic depositing VIVO releases in Zenodo.

https://github.com/vivo-project/VIVO/pull/247#issuecomment-2122036907

#reviewers channel

The channel is growing, which is a great news.

Draft notes in Google Docs

Task List

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