Date

02 Mar 2021

Call-in Information

Time: 11:00 am, Eastern Time (New York, GMT-04:00)

To join the online meeting:

• Go to: https://lyrasis.zoom.us/my/vivo1?pwd=a2Q3RUVKVkN2dkNHV3FUaFRtLzhGdz09
  • Passcode: 351860

• One tap mobile:

  • US: +16699006833,,9358074182# or +19292056099,,9358074182#

• Or Telephone:

  • US: +1 669 900 6833 or +1 929 205 6099 or 877 853 5257

  • Meeting ID: 935 807 4182

• International numbers available: https://zoom.us/u/aeANHanzED

Slack

• https://vivo-project.slack.com
  • Self-register at: http://bit.ly/vivo-slack
    

Attendees

 Indicating note-taker

1. Brian Lowe
2. Benjamin Gross 
3. Nicolas Dickner 
4. Georgy Litvinov
5. Benjamin Kampe 
6. Michel Héon 
7. Huda Khan 
8. Alexander (Sacha) Jerabek
9. Ralph O'Flinn  

Agenda

1. Alpha release
   
   1. Blockers
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      4. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   2. Deployment and developer workflow
      1. Not requiring home directory tar file Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      2. Offer ability to copy war to Tomcat during installation?
         1. 1. https://github.com/vivo-project/VIVO/pull/224
      3. Maven lifecycle semantics : install versus package?
   3. Unable to locate Jira server for this macro. It may be due to Application Link configuration. License text: should other changes be considered?
   4. Upgrades from monolingual to multilingual VIVO with ingested data
      1. Are we satisfied with providing documentation vs. tooling?
   5. Nonblockers and documentation tasks
      
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
2. New developments
   
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration. Configurable SPARQL queries for comprehensive individual deletion operations
      
      1. Pull request for testing:
         1. https://github.com/vivo-project/Vitro/pull/213
   2. Deploy VIVO with Solr in one "docker-compose up"
   3. Browser plugins that are able to double-submit editing forms
3. Post-i18n priorities
   1. VIVO-in-a-box
   2. Ingest / Kafka
   3. Advanced Role Management
   4. Moving Scholars closer to core - next steps

Future topics

1. Vitro JMS messaging approaches - redux
   1. Which architectural pattern should we take?
   2. What should the body of the messages be?
2. Incremental development initiatives
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   3. Integration test opportunities with the switch to TDB - requires startup/shutdown of external Solr ..via Maven

Tickets

1. Status of In-Review tickets

   Click here to expand...

   type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Notes 

1. 1.12 Alpha release blockers
1. VIVO-1956 needs some reviews. Review please. Should be fairly easy thing to check. Try some queries. Ralph and Don Elsborg are ready to test. 
2. VIVO-1966 Subject of the statement is not being reindexed. If you create a Faculty member and add sameAs property to second Faculty member. First one won’t be reindexed. sameAs doesn’t have inverse property. Default behaviour should be to reindex both object and subject. Georgy will prepare a pull request for this issue. 
3. VIVO-1967 Errors in logs appeared while opening the Person page. Binding method wasn’t implemented. Brian implemented it to make it work properly.
4.  VIVO-1969 - Removing RDF with uploadRDFForm does not lead to reindex dependent uris that should be found by IndexingUriFinder. The problem is that by the time indexFinders start working, triples they are looking for are already gone. After removing some data it could still exist in search indexes. Can lead some embarrassing situations but only relates to search indexes. It is a pre-existed problem. Maybe add some warning in documentation. For now this problem could create a delay to release 1.12. So maybe fix it later. Needs some more investigation.
2. Deployment
1. Michel tested VIVO-1968. We need to save layers of customizations. Simplest way to retain custom installation is to allow changes to core VIVO war-based installers. Good solution could be to have some switch to skip new install process (changing home directory) entirely. Could be a piece of the puzzle. William also reviewed it. 
2. Still have an issue to solve for UQUAM. UQUAM smoketests are showing problems with new context.xml In addition to packing tarball there have been some changes to context.xml It put one property in context.xml to bootstrap home directory. New example of context.xml https://github.com/vivo-project/VIVO/blob/main/installer/webapp/src/main/webResources/META-INF/context.xml . The name of home directory property has changed. Property vivo-home renamed to vitro-home. New installation doesn’t know about old properties. Possible resolution - take old context.xml and test with it. Michel is going to test it with updated context.xml. Error messages strangely has links to Tomcat9. Should new release documentation require Tomcat 9 or still 8.5 enough? Using Tomcat 9 is just a recommendation. No hard requirements for Tomcat 9 for now.
3. VIVO-1962 Georgy added some fixes to his initial pull request.

Draft notes on Google Drive