Date

23 Mar 2021

Call-in Information

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

...

• 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. Georgy Litvinov 
3. Nicolas Dickner 
4. Michel Héon 
5. Huda Khan 
6. William Welling
7. Benjamin Gross

Agenda

1. How can we make a push to get to RC1?
   
   1. Open pull requests:
      
      1. https://github.com/vivo-project/VIVO/pulls
      2. https://github.com/vivo-project/Vitro/pulls
   2. New issues
      1. Additional thoughts/results about precise subquery default for TDB or not?
   3.  Release Testing - 1.12.0
      1. How can we encourage community testing?
      2. Can we simplify documentation for new users?
   4. Documentation
      1. How an End-User Can Use the i18n Features
      2. Simplifying end-user/installation instructions while retaining details for developers
   5. Blocker issues
      

      1. Jira
         server LYRASIS JIRA jqlQuery project = VIVO AND priority = Blocker and status = Open serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

2. Embracing standard approaches : how do we better align VIVO with other software and make it easier to adopt / install / develop for without having to learn the "VIVO way"?
   1. Possible topics:
      1. Deployment
      2. Configuration : files / environment variables / GUI settings
      3. Frameworks / Spring
      4. Editing / form handling
      5. Adding custom theming without customizing build
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. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1688

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

   3. Integration test opportunities with the switch to TDB - requires startup/shutdown of external Solr ..via Maven

Tickets

1. Status of In-Review tickets

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

   
   

Notes

Draft notes on Google Drive

...