...
Indicating note-taker
- Brian Lowe
- Ralph O'Flinn
- Georgy Litvinov
- Nicolas Dickner
- Alexander (Sacha) JerabekSandra Mierz
- William Welling
Agenda
- Slack questions
- 1.12 release status
- Open pull requests:
- Blocker issues
Jira server LYRASIS JIRA jqlQuery project = VIVO AND fixVersion = v1.12 AND priority = Blocker AND (status = Open OR status = "In Review" OR status = "In Progress" ) serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
- Open pull requests:
- Future search indexing improvements: foolproof custom URI finders?
Jira server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1975 - Defining a "VIVO in a Box" project
- Updates from leadership group
View file name VIVOInABoxProjectOutline1.pptx height 250 - Discussion / questions / refining the idea
- Updates from leadership group
- Other forward-looking topics:
- frameworks: Spring / Spring Boot / alternatives
- Horizontal scalability
- Deployment
- Configuration : files / environment variables / GUI settings
- Editing / form handling
- Adding custom theming without customizing build
- Post-i18n priorities
- Ingest / Kafka
- Advanced Role Management
- Moving Scholars closer to core - next steps
...
Status of In-Review tickets
Expand Jira server DuraSpace JIRA jqlQuery filter=14416 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
Notes
- Slack questions
- William: compatibility issue between war file and Docker version?
- Brian: using alpha instead of main?
- William will try to test and reproduce
- Brian: maybe this user could use 1.12?
- William: in last resort
- Sandra : “alternative: use vivo-docker2 ?”
- Brian : “Maybe vivo-docker2 should be archived after this release if we are including a docker build with VIVO now”
- Sandra: “checked the docker-compose of vivo but there is no vitro installation included i think”
- Brian : “There really is no vitro installation. vitro is just a dependency of vivo. ; `mvn clean package -s settings.xml` will build vivo and bring in vitro from a sibling directory or pull the version from maven central.”
- 1.12 release status
- Brian: all blockers are in review stage ; one issue (which one?) was removed from list of blockers
- VIVO-1978 should be easy to test ; data sample included.
- VIVO-1976 fixed, but we need to check how and where else this code is used ; Benjamin will try to have a look.
- VIVO-1973 Fixed, although it would need a deeper fix in the future ; should be easy to test.
- VIVO-1969 Should be ready to merge
- VIVO-1967
- VIVO-1966 Ready to merge, but PR is pointing at wrong branch ; Brian will ask Ralph to look at this ; although might be simpler (though messier) to have Georgy to open new PR
- VIVO-1910 Merged
- VIVO-1820 Fixed, but wording / position of controls is confusing ; there might be a need to broader reflexion on forms in the future
- VIVO-1615 Fixed, but should be updated with a change to runtime.properties
- Open pull requests:
- Blocker issues
- Future search indexing improvements: foolproof custom URI finders?
- VIVO-1975 - UriFinders may fail to find all URIs that need updating after content is deleted
- Brian: Batch removal of URI is the problem.
- Georgy: has tried it with custom URI finder ; found a fix, but not reliable, and not efficient performance wise
- William Welling in Scholar, using a list of related identifiers to an individual to update them ; in absence of messaging system, they’re reindexing everything on a regular basis
- Defining a "VIVO in a Box" project
- https://wiki.lyrasis.org/display/VIVO/2021-04-06+-+VIVO+Development+IG?preview=/208340000/208340003/VIVOInABoxProjectOutline1.pptx
- Brian : last meeting mostly devoted to VIVO in a box ; the concept in gaining interest in the leadership group
- Bruce presented his vision at this point ; showed potential architecture
- V in a box would be easier, less costly to install and run. Would increase adoption, and then paying members
- Developing a simplified profile? Core data harvested from known data sources ; limited customization.
- Components: how does VIVO fit in the plan: VIVO would provide the triplestore, and VIVO Scholars Discovery would provide the API?
- Discussions about developing time, Solr architecture, interaction with Solr API. Previous plans to use VIVO's indexing features to build an index structured for Scholars-discovery expects still make sense in the light of proposed VIAB architecture diagram
...