Date

Call-in Information

Time: 11:00 am, Eastern Time

Attendees

(star)  Indicating note-taker

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

Agenda

  1. M1 mac chip and VIVO
    1. https://github.com/vivo-project/VIVO/issues/3915
  2. VIVO 1.15
    1. Issues
      1. https://github.com/vivo-project/VIVO/issues/3885 
      2. Avoid lock on graph uri update in RdfServiceSparql
    2. PRs
      1. https://github.com/vivo-project/VIVO/pulls
      2. https://github.com/vivo-project/Vitro/pulls

Notes

Dragan expressed his intention to start using the AI summary Zoom option for helping note-taking. T

Apache Solr 9 and VIVO

William shared that he has been experimenting with an upgrade of the vivo-solr project for Apache Solr 9 - https://github.com/vivo-project/vivo-solr/tree/upgrade. Dragan asked whether this solution might be backward compatible, meaning the new version of vivo-solr (including docker) might work for all versions of Apache Solr used with VIVO. William doubts it is a case, but we can try when the branch is completed. If it is not backward compatible, we will have to publish the vivo-solr release 1.0.0 which is working for Apache Solr 7 and 8, and the release 2.0.0 which is working for Apache Solr 9. 

Avoid lock on graph uri update in RdfServiceSparql PR

Georgy created a PR which is an extension of previously closed issue https://github.com/vivo-project/VIVO/issues/3885. Basically, Georgy moved part of the code from RDFServiceJena in the abstract root class RDFServiceImpl,   and adopted that also in other subclasses (RDFServiceSparql). Dragan noted his intention to explore the topic further, and its link to an issue they had previously closed. Dragan will review PR as soon as possible. Georgy clarified that the previous fix only applied to a specific service implementation and suggested that using an external triple store would not resolve the issue. 

Captcha Implementation and Security Concerns within the “I forgot my password” PR

Dragan discussed the implementation of a Captcha on the platform and pointed out some issues with the current setup. He explained that the Captcha sends from the frontend the hash value of the text in the image and the input back to the backend for verification, which could potentially be exploited to cheat the system. The team agreed that an option to turn off the “I forgot my password” feature would be beneficial and also discussed the needs for making thread safe a request history and frequency hash set.

Bootstrap's Impact on Extended Search

The team discussed the use of Bootstrap in the Wilma theme and its impact on the extended search feature. The plan moving forward is to merge the extended search PR with the Bootstrap 3 into the main branch, and then to align the responsive Wilma theme PR.

Progress and Future Steps for Ongoing Projects

The team evaluated the progress and future steps for several ongoing projects. They agreed to prioritize the merging of an extended search feature developed seven months prior. Attribute-based access control, which was completed, was found ready for the second round of review. 

Draft notes on Google Drive

Actions

Previous actions 

  • No labels

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