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. Brian Lowe 
  5. Georgy Litvinov  
  6. Ivan Mrsulja 
  7. Santhosh Anand Ramia

Agenda

    • Multiple h1 tags
    • VIVO - ElasticSearch integration
    • VIVO ORCID integration
      • Reynard Lee - Thoughtworks
    • VIVO upgrade - 1.9 -> 1.10
      • Santosh:
        • While upgrading to Vivo 1.10, I noticed that 1.10 jai_codec-1.1.3.jar and jai_core-1.1.3.jar are removed. However, I have some customisation in our code and would like to retain these jar. I am trying to pull them from Maven repo but not find them in repo. I am wondering how Vivo/Vitro was able to do it in version 1.9? Any suggestions?
    • VIVO 1.15.0
      • preparing release
      • PR review
    • VIVO 1.16.x
      • UI improvements
        • Responsiveness
        • WCAG compatibility
        • Branding (logo, colors) 
        • JQuery upgrade, bootstrap upgrade
        • SEO
    • VIVO 1.17.x
      • Data ingestion
        • Excel based
        • OpenRefine based

Notes 

Multiple h1 tags

Georgy opened a new issue - https://github.com/vivo-project/VIVO/issues/3989. This is SEO related issue, and there is at least one more linked with redirection wrong HTTP code which might confuse search engine crawlers. 

VIVO - ElasticSearch integration

Dragan discussed this issue with Don Elsborg (University of Colorado Boulder), and  Benjamin Gross (Clarivate) about this issue, but unfortunately they don’t have any example of replacement of Solr with ElasticSearch as a search engine in VIVO. The Brazilian team (BrCRIS) is interested in this topic. Ivan Mršulja started investigating this issue and here is the draft PR - https://github.com/vivo-project/Vitro/pull/469. Ivan developed a parser for elastic search queries. The team discussed the transition from Solr to ElasticSearch, with an emphasis on testing and ensuring all functionalities are covered. They agreed to refactor some code to make it elastic search specific and considered the option of releasing an experimental version for early testing. The decision on which version of elastic search to support was left open for further discussion. The team discussed the licensing changes of Elasticsearch, which they learned had become proprietary. The team concluded that if Elasticsearch were included as a third-party software, it should not affect their current licenses. The team decided to investigate further and revisit the topic in the coming days. 

VIVO ORCID integration

Reynard Lee didn’t participate in the call.

VIVO upgrade - 1.9 -> 1.10

Santhosh brought up an issue with upgrading from version 1.9 to 1.10, he couldn't find the 'scimapcore jar' in the Maven Central platform. Brian suggested that the jar might be from the Indiana team for the map of science and recommended Santosh to look for it here - https://github.com/vivo-project/dependencies/tree/main/org/vivoweb/dependencies/oim.vivo.scimapcore/1.0.

VIVO 1.15.0

The team is working on preparation for the VIVO 1.15.0  release. Moreover, during the next week a patch for 1.14 should be released (1.14.3) addressing the following bugs:

The future releases

The plan for VIVO 1.16 is to be focused on UI improvements

  • Responsiveness
  • WCAG compatibility
  • Branding (logo, colors) 
  • JQuery upgrade, bootstrap upgrade
  • SEO

while VIVO 1.17.x is to be around data ingestion improvements

  • Excel based
  • OpenRefine based

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

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