Date

Call-in Information

Time: 10:00 am, Eastern Time

Attendees

(star)  Indicating note-taker

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

Agenda

  1. Release candidate 3 (VIVO 1.14.0)
    1. https://github.com/vivo-project/VIVO/issues/3870
    2. https://github.com/vivo-project/VIVO/issues/3871 
  2. VIVO 1.15.0
  3. Audit / data provenance
    1. https://github.com/vivo-project/Vitro/pull/369#pullrequestreview-1424672241
    2. https://github.com/litvinovg/Vitro/tree/audit_tool
    3. https://github.com/litvinovg/VIVO/tree/audit_tool
  4. VIVO REST API
    1. Multilingual content
      1. fetching
        1. Content language HTTP header parameter 
          1. more than one?
      2. json represnation
name_en_US : "some text in English"

vs


name : {

value: "some text in English"

languageTag: "en_US"

}


    1.  Versioning
    2. Fetching data
      • pagination
        • limit and offset
        • stats data in response
          • size (usually the same as limit, except it is at the end of list), total, pagesCount, index (offset)
      • sorting
        • sort by (data property name), order (ASC or DESC)
  1. External graph base

Notes

The issue https://github.com/vivo-project/VIVO/issues/3870 has been introduced by https://github.com/vivo-project/Vitro/pull/385. There is no easy solution for the issue at the moment which might work in all cases for existing VIVO adopters. Therefore, we decided to revert PR, and resolve this issue and the issue https://github.com/vivo-project/VIVO/issues/3858 later. 

There was also discussion about publishing documentation for VIVO REST API. The question is whether OpenAPI specification might be enough for the VIVO community. 

Draft notes on Google Drive

Actions

Previous actions 

  • No labels