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. Brian Lowe 
  3. Ivan Mrsulja 
  4. Miloš Popović 
  5. Georgy Litvinov (star)
  6. William Welling 
  7. Yuji Shinozaki
  8. Samantha Emerson
  9. B. Henderson
  10. Rishabh Tatiraju
  11. Kshitij Sinha

Agenda

Notes

Yuji: Hi, I am with the University of Virginia. We have a home-build network of research in humanities and looking for more standardized implementation.
Dragan: Let us know if you have any question.

Dragan: There was a short discussion about forgotten passwords. It is possible for a system administrator to restore password, but the user is unable to do that without admin assistance.
Brian reported that it shouldn’t be complicated.
Brian: It is definitely something we should have in core and I would be happy to implement that.

William: should we inform the system administrator and log password update even.

Dragan: The last week we discussed shortcomings of current docker and the issue has been created. I already assigned that to William.
William: I suggest doing some improvement on docker.

Dragan: Last week we discussed other Solr problem and I tried to move discussion to Slack, but haven’t got a response yet.
Dragan: New issue has been reported about removing data. This is only the case with massive removal. Does anyone have experience with that?
I tried to upload the data and it works, it occurs only while removing the data. I will try to investigate that further.
Dragan: Two new issues are opened about faux properties.

https://github.com/vivo-project/VIVO/issues/3858
https://github.com/vivo-project/VIVO/issues/3859 

Brian: I suggest increasing priority for those issues.

Dragan: In the last week there was a complaint about upgrading VIVO 1.10 to VIVO 1.13.
If you are targeting 1.13 you can find information about upgrades in one place.

Dragan: Copying theme directory leads to broken UI labels. The UI labels are in the home directory, so they also should be copied and the theme name should be replaced.

Dragan: Regarding creation of scriptable dump/restore Ivan made some progress. I created one comment to rename files, script location and suggestion to introduce an environment file where variables could be specified once. I tested it and it works for me. Please test it on different environments and if there is any comment about it, it should be improved.
Ivan: I need to update instructions on how to run it and now it is slightly different.
William: I wanted to ask if we are going to have a follow-up issue. It would be nice to have the same functionality in java, it might be tedious to maintain that in scripts. It might be nice to have that in java, have automatic dump and restore.

Dragan: Thank you, it is interesting. Please write that down in a comment. 

Dragan: Last time we started discussion about priorities. My idea for today is to continue discussion about priorities. The interoperability might be a topic for this meeting.

It would be nice to have a json like REST endpoint besides SPRARQL API. Also, OAI PMH protocol is very popular in Europe, it should be supported as well. It would be also good to make it possible cross-linking and searching, meaning make it possible to create a network from VIVO instances.
William: That is a very interesting feature, instance when someone wants to cite someone on another instance how that should be saved. 

Dragan: As it is a semantic web it shouldn’t be stored locally.
William: You need to ensure that data integrity remains on another system. We should have protection from deletion for data that is cited from other instances.

Brian: I wonder how much we plan to create VIVO specific closed systems to dynamically bring data for any semantic web sources. If you want to dynamically link data you take the risk, if no, you have to store the data. WWW allowed links to break, overprotecting systems data integrity might be too complicated.

William: If instance is meant to maintain it’s internal integrity it has to check if the link is still available, how does VIVO do that currently? Does it use it?
Brian: I don't use it currently. I am not sure it is the most important thing currently.
How much does any institution want to store and how much dynamically link?
There are a lot of simple things before we got to fancy solutions. 

William: If there is an effort to integrate multiple instances is it possible to have an endpoint where you ask for external graph queries? How much a VIVO system can handle?

Dragan: In Europe there is OpenAIRE Graph, that offers some services, it is possible to join this network. If you provide data, then you can be registered there, if it has more information about the article, then it can enrich your data in VIVO.

Dragan: I suggest to stop here and continue next time. It would be nice if you could think about some topics and discuss that. Thank you very much for today and see you next Tuesday.

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.