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. Georgy Litvinov (star)  
  3. Kshitij Sinha
  4. Michel Héon 
  5. Brian Lowe 
  6. Benjamin Kampe 
  7. Ivan Mrsulja 
  8. Miloš Popović 
  9. Mark Vanin 
  10. William Welling 

Agenda

Notes

Dragan:
There are plans to organize a Dynamic API webinar.
Brazil contacted us to organize the Brazil CRIS demonstration. It would be nice to have a representative from the Brazilian team.
We should start preparations for VIVO 1.15. There are already some requests in review now. Also REST API from Persons is in implementation.
We plan to review and apply those PRs in August and September.
Maybe we postpone the Jena 4 update and maybe we should plan an update to the future Jena 5.
There might be small modifications, like restoring the VIVO password. To provide an email and provide a way to reset password.
When you log in as an administrator you have a button to send email for the user to reset a new password.
Brian: allowing users to do so should be simple, but if you try to reset your passwords too many times we might want to have some security settings. Or if we don’t need that, then it should be a fairly simple thing.
Dragan: I was afraid of that strategy to generate a password to admin space, then you can change someone else’s password.
Brian: No, you can just spam someone with emails to reset your password.
Dragan: We can also work on compatibility guidelines. Like replacing color in css files. But before we work on that guideline we should first merge all themes into one.
I will try to work on that together with Milos and Ivan. The idea is to keep wilma as a theme, but adopt changes from tenderfoot theme.
We would be able to reduce maintenance by leaving only one theme.

Dragan: This week I started reviewing PRs:

Started working on Audit PR.
We planned to enrich Extended search PR with more configurations.
Dragan: Georgy, do you remember that you proposed to make presentations about ABAC and other new features.
In an ideal scenario that presentation can be recorded and documented in the wiki.
Any other presentations are more than welcome too.
Kshitij : we plan to work on upgrades in the next weeks.
Dragan: It would be great if you would be able to share experience.
Michael: Sounds good. I will reach out to you.

Dragan: Regarding some conferences I keep invitations for the conferences: first one is SWIB23 which will take place in September, (Germany), then Pamplona euroCRIS meeting in November.
Dragan: There are some slack questions, thanks to Brian for the responses.
Also an issue was reported about migration of faux properties, Brian responded to that too.
Brian: I suggest mentioning display model where faux properties are stored on the ontology page in the VIVO wiki.
Dragan: we are getting back to weekly meeting mode. I prepared an ISC file, you can use it. I am also going to share calendars on Slack too.
We are trying to keep our meeting short and discuss topics in specific groups. If you have technical issues, we can discuss that on Slack and not require participants in these calls to have any technical skills.

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