Versions Compared

Key

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

...

(star)  Indicating note-taker

  1. Dragan Ivanovic (star) Georgy Litvinov    
  2. William Welling  

Agenda

  1. VIVO 1.15.0
    • Release Testing - 1.15.0
      • Five people tested new features - response summary
        • 1 of those 5 didn't manage to test hide faux object property successfully. Taking into account that 4 others testers did that, I think this feature is working (I have also tested that), but we should give our best in documenting how this should be done
        • 2 of 5 testers complained on message when they are providing a non-existing user email in I forgot my password page. The message is that an email has been sent, and it is desired feature. Initially, Ivan implemented two type of messages, no user account associated with that email and an email has been sent, but then we concluded in this way we are revealing existing account of a VIVO instance.
      • Three persons tested standard features - response summary
        • Add research areas using vocabulary services for UMLS is not working. The configuration is needed - Configuring External Vocabularies#ConfiguringtheUMLSExternalVocabularyService 
        • Visualizations issues
          • Map of Science
              google maps should be replaced with open street map
            • limited list of journals
          • Capability map
            • a lot of debug messages in the console
          • Publication sparkline
            • last 10 full years (2014-2023, no publications from 2024)
            • show numbers even when publications are hidden (is this bug or feature)
  2. Clean up of the previous tasks list
  3. VIVO demo site
    1. data
      1. https://github.com/vivo-project/sample-data
      2. https://github.com/chenejac/sample-data/tree/reorganization
    2. accounts
    3. docker
      1. https://hub.docker.com/r/vivoweb/vivo/tags
      2. vivo-home/config/runtime.properties
      3. https://github.com/vivo-project/VIVO/blob/main/docker-compose.yml

Notes

Draft notes on Google Drive

...

VIVO 1.15.0

Release candidate has been tested. There was a potential bug with importing UMLS vocabulary entries. Dragan tested that and concluded it is not a bug, an additional configuration is needed - Configuring External Vocabularies#ConfiguringtheUMLSExternalVocabularyService for the purpose of this import. Dragan will update google forms for collecting feedback in the testing procedure for forthcoming releases. 

VIVO demo site

Dragan and William discussed the potential use of a Docker image for the VIVO demo site. They debated the inclusion of sample data, the frequency of database cleaning. The possibility of creating a separate Docker project for the demo instance was considered. They delved into their system and discovered a Docker action that had successfully pushed an image but also recognized issues with their current tag management system causing overwrites. They agreed on the necessity for a more stable system and considered triggering actions when new releases are published. They also discussed the idea of allowing users to select different sample data sets for their operations, with a focus on ensuring consistency in format and URL. Lastly, William clarified the difference between the host machine and the containerized application, and how Docker uses .env files and Docker Compose to substitute variables. Dragan will open a ticket for making Docker image based on publishing a release.

The next meeting will be organized in two weeks (25th of July)

Draft notes on Google Drive

Actions

  •  Dragan to create an issue for updating the GitHub action to create a Docker image on release instead of on push to main branch - https://github.com/vivo-project/VIVO/issues/3995
  •  Dragan to consult with the Leadership group on which sample data should be included in the demo site
  •  Dragan to update the Google form instructions for testing the UMLS configuration in the next release candidate 

Previous actions 

...