Date
Call-in Information
Time: 10:00 am, Eastern Daylight Time, or 4:00 pm, Central European Summer Time
Join Zoom Meeting
https://lyrasis.zoom.us/j/81398228834?pwd=SE0wdFN3NnFVbEhYVUhuM3BtQmVUQT09Meeting ID: 813 9822 8834
Passcode: 728426- calendar invitation - ics
Attendees
Indicating note-taker
Agenda
- Correction of estimations for short term tasks
- REST API approach
- Progress on the implementation/review
- Corresponding author
- Dockerized VIVO update and vivo-home
- https://github.com/vivo-project/VIVO/issues/3997
- https://github.com/vivo-project/VIVO/pull/4003
- https://github.com/vivo-project/Vitro/pull/471
- https://github.com/vivo-project/vivo-solr/pull/8
- It doesn't do any docker stuff as it covers only deployment/installation decoupling. I am going to work on Docker stuff, but would like first to be sure that it is a correct approach.
https://github.com/vivo-project/VIVO/compare/main...litvinovg:VIVO:decouple-install-deploy?expand=1
https://github.com/vivo-project/Vitro/compare/main...litvinovg:Vitro:decouple-install-deploy?expand=1
I just changed deployment of war from unpacking to copying war file into tomcat if tomcat dir is provided.
So in case tomcat-dir is provided, war file will also be deployed. If not, it will retain in installer/webapp/target/{app-name}.war to be used manually.
Also home directory is not copied into vivo-dir, instead it is copied inside war artifact and then used by ApplicationSetup, which runs populate method on VitroHomeDirectory to copy home contents excluding "rdf" directory into vivo-dir. FileGraphSetup and RDFFilesLoader were changed to use rdf directory located in tomcat webapp instead of vivo-dir.
- It doesn't do any docker stuff as it covers only deployment/installation decoupling. I am going to work on Docker stuff, but would like first to be sure that it is a correct approach.
- https://github.com/vivo-project/VIVO/issues/3997
- Docker demo images
- Make willow responsive theme
- Elastic Search integration with VIVO
- Managed and not-managed authors - https://github.com/vivo-project/VIVO/issues/2613#issuecomment-2329446335
- Browse filters on custom page - https://github.com/vivo-project/VIVO/issues/4006
- Custom context path configuration
- https://github.com/vivo-project/VIVO/issues/3846
- https://github.com/vivo-project/VIVO/pull/4011
- https://github.com/vivo-project/Vitro/pull/475
- proxy (nginx, apache httpd) needed for testing
- https://github.com/vivo-project/VIVO/issues/3846
- Reconciliation API and Unicode
- https://github.com/vivo-project/VIVO/issues/4012
- https://github.com/vivo-project/Vitro/pull/476
- OpenRefine needed for testing
- https://github.com/vivo-project/VIVO/issues/4012
- JSON-like REST API for software
Notes
Correction of estimations for short term tasks
Brian and Dragan estimated short term tasks at the previous week meeting. It has been presented to the VIVO Strategic group. Dragan presented briefly the feedback. The out-of-the-box analytics via Kibana are expected. There are some security vulnerabilities with this approach which Georgy reported at the last tech meeting.
REST API approach
Team discussed which approach should be used for building REST API endpoints. Brian and Dragan discussed the challenges of using a semantic web approach for data retrieval and the need for a more user-friendly interface. Brian suggested the development of a hybrid system that would allow users to interact with the ontology and generate REST API endpoints without needing to write Java code. He emphasized the importance of promoting the benefits of the ontology and graph approach to avoid being seen as an impediment. The team decided to continue the discussion in future meetings to make the ideas more concrete and estimate the time needed for implementation.
Progress on the implementation/review
Georgy worked on decoupling building and deployment processes. The idea is similar to William's idea, but simplified. The unpacking was file into tomcat creates vivo-home directory if it is not already created and copying there bin and config directories. The RDF subdirectory stays in the tomcat/webapps, not in vivo-home. This should be discussed with William.
DOCKER improvements were suggested in different tickets, we need to consolidate them. Dragan will start working on specifications for a unique Docker ticket.
Actions
- @All to read estimations and provide feedback, if any, via Slack #committers group till Monday 7th of October 2pm CEST
Previous actions
- Georgy Litvinov to create a GitHub ticket describing the issue with Docker deployment breaking existing Vivo instances.
- William Welling to investigate potential solutions for the Docker deployment issue.
- Dragan Ivanovic to summarize the discussion about the demo site for the next meeting.
- Georgy Litvinov to review/improve the first two wiki pages of Dragan's documentation draft next week (
https://wiki.lyrasis.org/display/VIVODOC115x/Using+Search and https://wiki.lyrasis.org/display/VIVODOC115x/Authorization )
- William Welling to consider adding indexing performance discussion to the next meeting's agenda.
- Dragan to create an issue for updating the GitHub action to create a Docker image on release instead of on push to main branch - https://github.com/vivo-project/VIVO/issues/3995
- Dragan to consult with the Leadership group on which sample data should be included in the demo site
- Dragan to update the Google form instructions for testing the UMLS configuration in the next release candidate
- All to test VIVO 1.15.0 release candidate 1