...
- William Welling
- Andrew Woods
- Alexander (Sacha) Jerabek
- Benjamin Gross
- Ralph O'Flinn
- Benjamin Gross
- Michel Héon
- Huda Khan
- Rachid Belkouch
- Don Elsborg
- Brian Lowe
Agenda
- i18n update
- need one more review, Benjamin Grosshas "approved"Jira server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1848 Jira server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1885
- the final lynchpinJira server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1918
- Simplifying installation
Jira server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1443 Jira server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1752 - Two tasks: process for auto-configuration and determining the correct configuration
- Moving Scholars closer to core - next steps
- SelectQueryDocumentModifier
- Entities: Collection, Concept, Document, Organization, Person, Process, and Relationship
- Configuring Solr
- Moving Data Ingest Task Force forward
- Renaming of 'master' branch?
...
- i18n update
- Andrew - I don’t think much has been done since our last call. True.
- VIVO-1848 - i18n: Improve Identification of files to filter IN REVIEW - need one more review,
- Benjamin Gross has "approved"
- Another review would be preferred
- Removes the available.langs file
- Changes structure of rdf directory - see https://github.com/vivo-project/Vitro/pull/169 for the new directory structure
- Retains the directory of the language agnostic files from before
- VIVO-1885 - i18n-regression-test documentation IN REVIEW
- Just here FYI
- Andrew: It’s challenging, but he’s gotten it to work from the documentation
- VIVO-1918 - i18n: Reload firsttime files on start-up if changed IN PROGRESS - the final lynchpin
- Leading to a more exciting discussion on RELEASING THE BETA (of the merged i18n work).
- Brain Lowe should have an opportunity to work on it in October
- Brian: Is there still a concern about page rendering speed with language filtering turned on?
- Andrew: Is caching a possibility?
- Brian wants to look at the filtering mechanism algorithm. The actual amount of data returned when languages are enabled is not significantly more, but we lose a lot of time in the filtering mechanism itself.
- Or can we order the result set from the queries so the language data is grouped together?
- Andrew: Is there a small example dataset to evaluate the difference between languages on and off?
- So remaining issues: Reload firsttime, performance, and a boatload of documentation (Andrew points to Sacha gently)
- Does it make sense to schedule another sprint?
- Ralph: Perhaps a two week sprint? Andrew: Perhaps first week, finish i18n work then second week prepare the release.
- Ok, so do we need a sprint? If so, what is the nature of the sprint? Sacha says he could focus on documentation for a week. Brian and Benjamin will not be able to devote an entire week to a sprint. Others may be able to participate (eg Dominik) and we will rely on the committers for reviews.
- Huda will provide ONE WEEK of moral support
- Andrew will attempt to schedule with Ralph and Sacha (plus Dominik and Mathias and UQAM folks).
- Distillation of priorities: https://docs.google.com/spreadsheets/d/17tfl5-q8DmRTI-Vc2MiONsscaQ4JBlAWy7SbvzXdL40/edit#gid=0
- Note #7 - simplifying installation
- Simplifying installation
- VIVO-1443 - Decouple VIVO build from installation IN PROGRESS
- Not actively in progress
- VIVO-1752 - Instantiate Solr core via API OPEN
- Two tasks: process for auto-configuration and determining the correct configuration
- See updates to https://jira.lyrasis.org/browse/VIVO-1752
- TAMU uses a Spring solr library to manage the schema. Still requires an initial config.
- It’s not clear if Solr is really intended to be built this way
- Andrew is concerned if Solr exists outside the VIVO server
- Brian reports that in the past people have requested having Solr on a separate server… but we don’t usually do that.
- Brian - even if we can’t create the config via API perhaps the Schema could be created?
- Spring API solr requires a collection to exists… could be default. Will read your annotated solr document files and update the schema for you.
- Some gotchas… e.g. can’t mutate certain types of fields
- Moving Data Ingest Task Force forward
- Haven’t heard from them in awhile
- Renaming of 'master' branch?
- Update: "GitHub to replace 'master' with 'main' starting next month"
- Might still be some work on the GitHub side for easy migration
Actions
- Benjamin Gross to merge VIVO-1848