Date
13
Call-in Information
Time: 10:00 am, Eastern Time
Join Zoom Meeting
https://lyrasis.zoom.us/j/81398228834?pwd=SE0wdFN3NnFVbEhYVUhuM3BtQmVUQT09Meeting ID: 813 9822 8834
Passcode: 728426
Attendees
Indicating note-taker
Agenda
...
- VIVO 1.14.0
- Release AnnouncementSonatype Lift reportsVIVO - https://sbom.lift.sonatype.com/report/T1-118f0f57da8c6b3097cc-5c65f36277df-1688553698-5e77ced0b59241b2b152ad8f4b1f27fd
- Vitro - https://sbom.lift.sonatype.com/report/T1-118f0f57da8c6b3097cc-5c65f36277df-1688553504-100eac36d1c041d0add87254fa18fd07 CodeQL analysis
- Release process
- VIVO Release Process
- decoupling scripts for publishing Vitro release from VIVO release??
- not yet fixed
- removing tags and branches ??
- done
- decoupling scripts for publishing Vitro release from VIVO release??
- VIVO Release Process
- features
- REST API (person, org unit, research)
- Search filters (extended search)
- Audit module (change tracking)
- Improvements
- Advanced role management system (ABAC)
- Jena 4
- Improved build and deployment process
- Code style improvements
- JIRA filters for old JIRA repository
...
- When this PR should be merged?
Notes
The issue with CodeQL action is still not resolved (https://github.com/vivo-project/VIVO/blob/main/.github/workflows/codeql-analysis.yml), Dragan will work on that.
We should consider moving https://github.com/chenejac/VIVO-release-publisher to the vivo-project organization (https://github.com/vivo-project/VIVO-release-publisher). We will think a little bit about that, and if there is no objection about that at the next meeting, we will transfer repository to the vivo-project organization.
The building of Code style improvements PR might fail after merging some of the active PR which are adding new Java classes. We should think about the order of merging PRs for the next minor release. If Code style improvements PR is merging the last, the suppression xml file should be extended with new classes from other PRs.
William started a short discussion about adding interoperability with other platforms as a feature for the next minor release. It is not just about REST API endpoint for adding data, it can also include options in UI for harvesting and transforming data from other sources (ORCID, Scopus, WoS, etc.).
Actions
Previous actions
- Dragan Ivanovic to prepare VIVO 1.14.0 release
- Dragan Ivanovic to prepare release candidate 4
- Georgy Litvinov to align https://vivo.tib.eu/vivorc/ with release candidate 4
- Dragan Ivanovic to respond to slack messages
- Dragan Ivanovic will try to collect wiki pages where strategy, vision and roadmap for development of VIVO were discussed in the past
- Georgy Litvinov will try to address the issue https://github.com/vivo-project/VIVO/issues/3871
- Dragan Ivanovic will ask Michael to open a GitHub ticket for the issue about UF performance during login (https://vivo-project.slack.com/archives/C8RL9L98A/p1684174222986709), Brian Lowe and others can continue discussion about this issue once a ticket is open
- Dragan Ivanovic will ask Rodrigo to open a GitHub ticket for the issue about custom theme and VIVO Docker (https://vivo-project.slack.com/archives/C8RL9L98A/p1684962021101889), William Welling and others can continue discussion about this issue once a ticket is open
- Brian Lowe to open a GitHub issue for index page exception
- https://github.com/vivo-project/VIVO/issues/3867
- add sample (minimal RDF to reproduce the issue)
- Miloš Popović or Ivan Mrsulja to review (https://github.com/vivo-project/VIVO/issues/3862)
- Georgy Litvinov to review (https://github.com/vivo-project/VIVO/issues/3847)
- Review (https://github.com/vivo-project/VIVO/issues/3865)
- Review (https://github.com/vivo-project/VIVO/issues/3864)
- Review (https://github.com/vivo-project/VIVO/issues/3858)
- Review (https://github.com/vivo-project/VIVO/issues/3859)
- Review (https://github.com/vivo-project/VIVO/issues/3855)
- Review (https://github.com/vivo-project/VIVO/security/dependabot/3)
...