Date

Call-in Information

Time: 10:00 am, Eastern Time

Attendees

(star)  Indicating note-taker

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

Agenda

  1. Release candidate 3 (VIVO 1.14.0)
    1. https://github.com/vivo-project/VIVO/issues/3871 
  2. Michael Bentz issue (login performance) - https://vivo-project.slack.com/archives/C8RL9L98A/p1684174222986709
  3. Rodrigo Villagran Mikacic issue (custom theme and docker) - https://vivo-project.slack.com/archives/C8RL9L98A/p1684962021101889
  4. Audit / data provenance
    1. https://github.com/vivo-project/Vitro/pull/390
    2. https://github.com/vivo-project/VIVO/pull/3879
      1. failing github action
  5. VIVO REST API
    1. Multilingual content
      1. Representation of resource
        1. JSONContainer and SPARQLJSONContainer
        2. HTTP header Accept
          1. application/json
          2. application/sparql-results+json - SPARQL Query API#SELECTtoJSONexample
name : [ "some text in English@en_US", "neki tekst na Srpskom@sr_Lang_RS"]

vs


name : [

{value: "some text in English", xml:lang:"en_US"}

,

{value:"neki tekst na Srpskom", xml:lang: "sr_Lang_RS"}

]




Notes

VIVO leadership group (VIVO LG) meeting

Dragan informed committers about the VIVO leadership group (VIVO LG) meeting discussion related to strategy for further development of VIVO. VIVO LG thinks simplification of VIVO for usage and modernization of technology steck are needed. A virtual meeting on this topic might be organized in the near future. The available discussions about roadmap for VIVO development can be found at different wiki  pages - 



Release candidate 3 (VIVO 1.14.0)
 https://github.com/vivo-project/VIVO/issues/3871 is not a simple for resolving, we should consider whether we should wait for its resolving or publish VIVO 1.14.0 without that. Georgy would like to give a try to resolve the issue and we will discuss his progress next week. 

Michael Bentz issue (login performance) - https://vivo-project.slack.com/archives/C8RL9L98A/p1684174222986709

Brian thinks the issue might be linked with getting names of models. It is the issue which might be linked with amount of data in the graph and it is linked only with TDB, not with SDB, which is explaining why UF has that issue now after switching from SDB to TDB. Dragan will suggest Michael to open a GitHub ticket about this.

 Rodrigo Villagran Mikacic issue (custom theme and docker) - https://vivo-project.slack.com/archives/C8RL9L98A/p1684962021101889

William thinks this issue is resolvable by a little bit of scripting. Dragan will suggest Rodrigo to open a GitHub ticket where we can continue discussion.

Audit / data provenance

The build GitHub action for VIVO is failing because it is building VIVO by cloning the Vitro main branch. Once when https://github.com/vivo-project/Vitro/pull/390 is merged to main branch, we can re-run the VIVO build GitHub action again over https://github.com/vivo-project/VIVO/pull/3879

VIVO REST API

This topic will be discussed at the next Dynamic API meeting.

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.