Date

Call-in Information

Time: 10:00 am, Eastern Standard Time, or 4:00 pm, Central European Time

Attendees

(star)  Indicating note-taker

  1. Dragan Ivanovic (star) 
  2. Georgy Litvinov   
  3. William Welling
  4. Brian Lowe  
  5. Benjamin Gross 

Agenda

  1. Taking notes
  2. Extended search 
    1. presentation 
    2. documentation
  3. M1 mac chip and VIVO
    1. https://github.com/vivo-project/VIVO/issues/3915
    2. github action - build 
      1. https://github.blog/2023-10-02-introducing-the-new-apple-silicon-powered-m1-macos-larger-runner-for-github-actions/
  4. I forgot my password
    1. https://github.com/vivo-project/Vitro/pull/421
  5. Avoid lock on graph uri update in RdfServiceSparql
    1. https://github.com/vivo-project/Vitro/pull/424
  6. ABAC
    1. https://github.com/vivo-project/Vitro/pull/398 

Notes

Taking notes

We will try to organize manual and Zoom AI taking notes in parallel in the next couple of weeks (till end of the year), and then we will decide whether we can switch to using only Zoom AI summary for the purpose of taking notes. 

Extended Search

Georgy is willing to help in documenting and presentation of the Extended Search feature. At the moment, he is busy and will contact Dragan back when his availability is better to arrange a presentation at some of the regular tech calls.  

M1 mac chip and VIVO

Benjamin continued to experience issues with the VIVO platform not booting up at his Mac laptop, despite a fix in a PR (https://github.com/vivo-project/Vitro/pull/425). Dragan also mentioned that they were waiting for Michael's (Bentz) feedback. 

I forgot my password

The team discussed the implementation of a Captcha feature in VIVO and its potential issues. Dragan clarified that the system was not perfect and should be improved. Welling, raised a question about the uniqueness of the hash. The team agreed that further investigation was needed.The group also acknowledged the possibility of bypassing the system. They also identified an issue with the way they were sending data between the front end and the server.

Avoid lock on graph uri update in RdfServiceSparql

Brian will try to find time to review this PR (https://github.com/vivo-project/Vitro/pull/424). 

ABAC

We need testing of this large PR, and it would be nice to review the ontology behind this feature.  

vitro:modTime property - update after changes through SPARQL update API

The issue is described at https://github.com/vivo-project/VIVO/issues/3917. It is possible to define a listener which will update modTime property even in the case an object is changed through SPARQLupdate API. Brian expressed doubts about the consistency of the modTime property, suggesting it might be best to remove it entirely if it was not consistently being updated. The team also discussed the possibility of creating a new solution to track modifications. William thinks we might even investigate if this might be done on behalf of triplestore. 

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.