Date

Call-in Information

Time: 10:00 am, Eastern Time (New York, GMT-04:00)

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

Slack

Attendees

(star)  Indicating note-taker

  1. Dragan Ivanovic 
  2. Georgy Litvinov (star)
  3. Benjamin Kampe
  4. Veljko Maksimovic 
  5. Huda Khan 
  6. Florian Kotschka
  7. Santhosh
  8. Christian Hauschke 

Agenda

  1. Questions/Issues/Pull requests/Announcements
    1. Altmetric popover issue/question - https://vivo-project.slack.com/archives/C8RL9L98A/p1650482974398349 
    2. The license issues - https://github.com/vivo-project/VIVO/issues/3690, https://github.com/vivo-project/VIVO/issues/3692
    3. Prevent copying pom file to home directory - https://github.com/vivo-project/Vitro/pull/288
    4. an i18n regression fix - https://github.com/vivo-project/Vitro/pull/289
    5. Duplicated faux properties every time - https://github.com/vivo-project/VIVO/issues/3680
    6. Ontology editing sometimes stops working - https://github.com/vivo-project/VIVO/issues/3685
    7. orcid-api-client mitigation of vulnerability - https://github.com/vivo-project/VIVO/pull/3694
  2. DSpace-VIVO integration
    1. DSpace-VIVO integration task force
  3. Publishing of a minor release 
    1. Completion of PR reviews and merging
    2. Preparation of a release candidate
    3. Updating of technical documentation - VIVO 1.13.x Documentation 
      1. Uploading files associated with individuals
      2. Developing a New Interface Language for VIVO
      3. SPARQL Update API
      4. Minimum Configuration
    4. Testing
      1. Standard features test - https://forms.gle/BsAz3ongzU1BR5nE7
      2. Advanced features test - https://forms.gle/BX7o8gwwVfCujWes5
      3. New Features test - https://forms.gle/35hNEjMnfcYC1ZpMA
  4. The next sprint
    1. date
      1. May 30th - June 17th
    2. Registration
      1. please register until May 15th, 2022 
      2. link
    3. Topics 
      1. Update the ontology
        1. GET all and GET one - two dynamic actions or one
      2. Implement more complex workflows
        1. iteration step,
        2. conditional step
        3. Implement N3Template deletion and modification
      3. User interface for execution of a dynamic action
      4. User interface for definition of a dynamic action
      5. Validation of dynamic action
      6. Authorization - roles
    4. Selection of the frontend technology/framework
      1. https://docs.google.com/document/d/1n2vZNN5YEIh9UhF44KahHnclkRiK3p8dZbY0VnaRAsk/edit?usp=sharing

Notes

  1. Questions/Issues/Pull requests/Announcements

    1. Altmetric popover issue/question - https://vivo-project.slack.com/archives/C8RL9L98A/p1650482974398349 

Santhosh: It is resolved now.

    1. The license issues - https://github.com/vivo-project/VIVO/issues/3690, https://github.com/vivo-project/VIVO/issues/3692

Updating of the year.

Dragan: How we resolved that before?

Christian: Someone from Lyrasis could investigate if we can relicense it so we don’t have a dependency.

Dragan: So you suggest to use the VIVO project.

Chistian: That should be moved to Leadership group.

Dragan: I discussed this with Mike Conlon. He wasn’t sure who could help with this.

Christian: I think this should be delegated to Leadership group. If you could move the question there, I would explain the issue and provide suggestions. This is just a fast solution for now. We should sort out this with licenses. We need something now, but this is a long term question and could be resolved later.

  1. Prevent copying pom file to home directory - https://github.com/vivo-project/Vitro/pull/288

Georgy:  This should fix copying files to vivo home directory

  1. an i18n regression fix - https://github.com/vivo-project/Vitro/pull/289

Georgy: My PR should revert changes lost during i18n sprint.

  1. Duplicated faux properties every time - https://github.com/vivo-project/VIVO/issues/3680
  2. Ontology editing sometimes stops working - https://github.com/vivo-project/VIVO/issues/3685
  3. orcid-api-client mitigation of vulnerability - https://github.com/vivo-project/VIVO/pull/3694

Dragan: I updated orcid api client dependency. This library like others depends on jackson databind, which was recently addressed. We tried to align VIVO to use the same version of this library. Now the situation is much better, but there is still 2 vulnerabilities. But jena arq didn’t address this issues jet. I am not sure whether we are going to patch old versions or move to new jena version. This PR is just aligning used jackson databind libraries. Previous versions had more than 40 vulnerabilities. 

  1. DSpace-VIVO integration
    1. DSpace-VIVO integration task force

Basically massive migration, harvesting has been implemented. Some transformation and loading into vivo graphs is in progress. We are still discussing issues with transforming. Will see what would be the final implementation, at the moment this migration should result in viewing articles, books and so on from DSpace. At the moment this information is not ready, we will discuss this in our DSpace integration group. We should be able to deposit files in DSpace, not on VIVO side.

  1. Publishing of a minor release 

Dragan: Probably it will be delayed but released before the summer.

  1. Completion of PR reviews and merging
  2. Preparation of a release candidate
  3. Updating of technical documentation - VIVO 1.13.x Documentation 
    1. Uploading files associated with individuals
    2. Developing a New Interface Language for VIVO
    3. SPARQL Update API
    4. Minimum Configuration
  4. Testing

You could help us test the VIVO release. There are three groups of tests. We hope to automate testing in the future. New features should also be covered by tests. Basically new feature tests are manual testing. 

In this release there are updates for SPARQL Endpoint, Localization improvements, Files uploading and option to configure external smtp server with authorization.

  1. Standard features test - https://forms.gle/BsAz3ongzU1BR5nE7
  2. Advanced features test - https://forms.gle/BX7o8gwwVfCujWes5
  3. New Features test - https://forms.gle/35hNEjMnfcYC1ZpMA


  1. The next sprint

Dragan: The idea is to continue working on dynamic api, this time we plan to focus on fronted. We fixed the dates. Check the dates in your calendar and inform us if you are able to participate by filling the form.

First question is how to select frontend technology. We created a spreadsheet for this purpose, to specify what we are expecting from the frontend and make a decision which framework should be adopted. We have a responsive user interface, support localization and SEO. 

One year ago Lyrasis paid for assessment of support accessibility in VIVO. 

We also need server side rendering and hope to have a generic user interface to have dynamic forms with a button to submit forms. If you have some experience in javascript frameworks please do not hesitate to fill in the table. If you have suggestions to improve this table, feel free to add comments in this table. 

I think this sprint is quite important for all. Please feel free to participate in the Sprint. 

Santhosh: I learned something from the scratch for freemarker.

Draft notes in Google Docs

Task List

  • Dragan Ivanovic to send a require to add in the Leadership group agenda a topic for discussing Copyright owner in Licence
  • All please help in filling this document - spreadsheet

Previous Tasks 

  •  Dragan Ivanovic to create a draft version of a Google Spreadsheet document with labeled columns representing requirements and to share with committers
  • Committers to review the structure of the document and to fill it with data for JS and CSS frameworks
  • Dragan Ivanovic to make demo of what we have developed as a result of the sprint
  • No labels

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