Date

06 Jan 2021

Call-in Information

• https://lyrasis.zoom.us/my/vivo1

Attendees

 Indicating note-taker

1. Brian Lowe 
2. Benjamin Gross 
3. Don Elsborg
4. William Welling

Agenda

1. Review pending VIVO and Vitro pull requests
2. In-review
   

   1. 
      

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

      
      

Other topics

Notes

• Discussion surrounding

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

  • Don: Will the old process still be maintained?
    • Likely not
  •  William: What about maven deploy?
    • Could we use that to provide an option that copies over the .war? 
    • Or potentially execute the old Maven build process
  • Who will be affected by these changes?
    • In its current state, 3 tier build is only partially possible
    • Anybody who wants to edit files directly in their Tomcat directory, i.e. hotfixes without change control
    • People editing or adding files in their VIVO home directory
      • Edited files would have been overwritten via the old process anyway
  • Revisit moving themes to home directory? That way a .war could be distributed that would be common across all users.
  • Alternatives to copying the vivo-home tar upon every start
    • Could there be a configuration flag that determines whether the copy happens or not? Perhaps in runtime.properties, that makes the deployment of the home directory configurable? 'clobber setting'
    • Default config could be 'don't copy' with the exception that it will need to copy on 'firsttime' regardless of setting. 
    • What about the upgrade process, when additional files may have been added to home, or edited? 
  • From Brian, there is also the 'Do Not Build' option: We already create an existing .war file upon compilation (which is then exploded and inserted into Tomcat's webapps directory). What if the end users who want a war downloaded two things... war file and tar file for home? 
  • Path forward seems to require two things at a minimum
    • A method for building the application with both webapp and home directory overlays (fully functioning third tier)
    • A change so the home folder files are not copied on every startup. 

Actions

•  ...

Previous Actions

•  Brian Lowe to draft initial sketch of "VIVO2" in a Google Doc
•  Huda Khan to review: 

  Jira
  server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1694

•  Brian Lowe to review: 

  Jira
  server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1694

•   Ralph O'Flinn to review: 

  Jira
  server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1694