...

 Indicating note-taker

1. Brian Lowe
2. Ralph O'Flinn 
3. Georgy Litvinov 
4. Nicolas Dickner
5. Alexander (Sacha) JerabekSandra Mierz 
6. William Welling
7. Benjamin Gross Benjamin Kampe 
8. Huda Khan

Agenda

1. Slack questions
2. 1.12 release status
   
   1. Open pull requests:
      
      1. https://github.com/vivo-project/VIVO/pulls
      2. https://github.com/vivo-project/Vitro/pulls
   2. Blocker issues
      

      1. 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

3. Future search indexing improvements: foolproof custom URI finders?

   Jira
   server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1975

4. Defining a "VIVO in a Box" project
   1. Updates from leadership group

      View file
      name VIVOInABoxProjectOutline1.pptx height 250

   2. Discussion / questions / refining the idea
5. Other forward-looking topics:
   
   1. frameworks: Spring / Spring Boot / alternatives
   2. Horizontal scalability
   3. Deployment
   4. Configuration : files / environment variables / GUI settings
   5. Editing / form handling
   6. Adding custom theming without customizing build
6. Post-i18n priorities
   
   1. Ingest / Kafka
   2. Advanced Role Management
   3. Moving Scholars closer to core - next steps

...

1. Status of In-Review tickets

   Expand
   Jira server DuraSpace JIRA jqlQuery filter=14416 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

Notes

1. Slack questions
   1. William: compatibility issue between war file and Docker version?
   2. Brian: using alpha instead of main?
   3. William will try to test and reproduce
   4. Brian: maybe this user could use 1.12?
   5. William: in last resort
   6. Sandra : “alternative: use vivo-docker2 ?”
   7. Brian : “Maybe vivo-docker2 should be archived after this release if we are including a docker build with VIVO now”
   8. Sandra: “checked the docker-compose of vivo but there is no vitro installation included i think”
   9. 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. Brian : anyone an idea for https://vivo-project.slack.com/archives/C8RL9L98A/p1617519081037900?
2. https://vivo-project.slack.com/archives/C8RL9L98A/p1617710461045600

1. 1.12 release status
   1. https://github.com/vivo-project/VIVO/pulls
   2. https://github.com/vivo-project/Vitro/pulls
   1. Brian: all blockers are in review stage ; one issue (which one?) was removed from list of blockers
   2. VIVO-1978 should be easy to test ; data sample included.
   3. VIVO-1976 fixed, but we need to check how and where else this code is used ; Benjamin will try to have a look.
   4. VIVO-1973 Fixed, although it would need a deeper fix in the future ; should be easy to test.
   5. VIVO-1969 Should be ready to merge
   6. VIVO-1967 
   7. 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
   8. VIVO-1910 Merged
   9. VIVO-1820 Fixed, but wording / position of controls is confusing ; there might be a need to broader reflexion on forms in the future
   10. VIVO-1615 Fixed, but should be updated with a change to runtime.properties
1. Open pull requests:
2. Blocker issues
2. Future search indexing improvements: foolproof custom URI finders? 
1. VIVO-1975 - UriFinders may fail to find all URIs that need updating after content is deleted 
2. Brian: Batch removal of URI is the problem.
3. Georgy: has tried it with custom URI finder ; found a fix, but not reliable, and not efficient performance wise
4. 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
3. Defining a "VIVO in a Box" project
   1. https://wiki.lyrasis.org/display/VIVO/2021-04-06+-+VIVO+Development+IG?preview=/208340000/208340003/VIVOInABoxProjectOutline1.pptx
   2. Brian : last meeting mostly devoted to VIVO in a box ; the concept in gaining interest in the leadership group
   3. Bruce presented his vision at this point ; showed potential architecture
   4. V in a box would be easier, less costly to install and run. Would increase adoption, and then paying members
   5. Developing a simplified profile? Core data harvested from known data sources ; limited customization.
   6. Components: how does VIVO fit in the plan: VIVO would provide the triplestore, and VIVO Scholars Discovery would provide the API?
   7. 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
1. Updates from leadership groupPrésentation

Draft notes on Google Drive

...