Date

Call-in Information

Time: 10:00 am, Eastern Time (New York), 4pm Central European Summer Time

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. Miloš Popović 
  3. Georgy Litvinov (star) 
  4. Mel M
  5. Doug Chestnut
  6. Samantha Emerson
  7. Michael Bentz
  8. Kshitij Sinha
  9. William Welling 
  10. Yuji Shinozaki
  11. Christopher P. Barnes 
  12. Ivan Mrsulja 
  13. Michel Héon 

Agenda

Notes

Dragan: there is a plan to resolve WCAG Compliance issues in future 1.15 release.

Also it would be nice to brand VIVO easily. 

Regarding the login error issue, TDB is recommended to be used. SDB support is going to be discontinued.
There is a group member from Austria announced  international project.

Chris Barnes: We are experiencing login errors on SDB. The app looks to be serving pages fine, but if someone uses login then the app hangs for 10 seconds.
Michael Bentz: We were running this in a container. Even the root user account couldn’t login for some time. It is not a network problem. Not sure where to look for.

Replication might depend on data. The question is if the issue with the logging in is related to the data.

Dragan: Is it slow once you sign in?
Michael Bentz: No, it was fast. I will try to replicate it with a smaller dataset.

Dragan: VIVO 1.14rc3  is going to be published soon.
There was a GitHub issue today. RC should be ready and announced tomorrow.
If there are any more issues, we will fix that and make another release candidate.
Some suggestion in Lyrasis group was to organize 2 releases per year.
If we publish 1.14 in May, it would be good to publish the next release in October.

We also started preparation for 1.15 and as we are closer to publishing the release we will try to prepare some milestones. My first idea for the next release might be extended search. We also plan to organize an update to Jena 4.
There might be some unexpected issue with Jena upgrades.
It would be nice to improve compatibility with WCAG.
Role management upgrade was mentioned recently by Georgy.
For release 1.14 it is too late, but for 1.15 we can discuss some specific requirements.
A feature to reset user passwords might be implemented.
Michel: I think json like REST API endpoints would be very interesting to retrieve information in JSON format. I have some ideas on that and probably will explore some solutions. Is it the type of feature we might implement in 1.15.
Dragan: JSON REST API is a topic discussed in dynamic API. Once we get to that and new endpoints we can call that VIVO 2.0.
If we complete dynamic API activities it might be ready.
Michel: There is a VIVO proxy to transform data from a database and this implementation is another application in a tomcat container. I am looking to integrate that inside a VIVO instance and give this API as a frontend to do batch processing, retrieve data and push data into VIVO. This is a type of thing I would like to explore. It would be interesting to investigate that.
Dragan: Do you already have some specified API?
Michel: Yes, I can send you the YAML file.
Dragan: Idea is to implement that with dynamic API, we could investigate what is the missing part compared to your solution. It might be interesting to define requirements for dynamic api.
Michel: I made a presentation at the last VIVO conference about VIVO proxy. 

Dragan: It would be nice to improve performance of working with external graph. 

Michel: It is very complicated and it is very hard to improve that. If we think of using VIVO as a service it is a major issue.
Dragan: Not sure how and when we can resolve this, but that would be very good to fix that.

Yuji: Can you briefly describe the last items in the agenda?

Dragan: It is just a general discussion.
One item is a reporting instruments in VIVO. It would be nice to integrate UI with reporting instruments. Regarding reporting TIB created one project to create sets of reports.
So the question is how we can improve the reporting aspect of VIVO?

It would be nice to provide this opportunity to regular vivo users, not only semantic experts.
Project centered VIVO is one of the aims of the Berlin Alliance. It would be nice to integrate that into the VIVO code base.

Dragan: It might be that a reporting tool will be contributed from TIB.

Dragan: We have some support for grants and projects, but there could be improvements.
I have one item for you to think about. Last year we tried to organize work in the form of sprints, but now we have more than one topic. There are members of the community who would like to participate, but others would prefer more continuous work.
I think we can continue working on project boards and the question is how to select the topic for the sprint.
Last time we worked with two project boards. It might be done in a format of continuous work. So it is a question for some institutions work in sprints is more appropriate, but for others it might be easier to work in a form of continuous development.

Dragan: Yuji, do you have any updates?
Yuji: We are still in a phase of planning. There are two use cases we are trying to apply on a database we inherited. It is more of a social network type and that’s where the questions come. I am worried about the source of the data and if it is community based we need to think about it.

Draft notes in Google Docs

Task List

Previous Tasks 

  • Dragan Ivanovic to add columns in the project board for Priority and Difficulty.
  • Sprint participants to read description of issues and think about their preferences. 
  • No labels

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