Date

20 Oct 2020

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

• 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. William Welling 
2. Andrew Woods
3. Alexander (Sacha) Jerabek  
4. Benjamin Gross 
5. Huda Khan 
6. Ralph O'Flinn
7. Brian Lowe
8. Nicolas Dickner
9. Michel Héon

Agenda

1. I18n sprint next week
2. WCM approach (Sarbajit, Paul)
   1. Deployment
      1. WCM's repo
      2. SDB vs. TDB
      3. Kubernetes (https://github.com/wcmc-its/vivo-docker.git)
   2. Ingest
      1. ReCiter Connect
3. Drop-in war
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      1. Third-tier builds?
4. Solr configuration
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      1. Two tasks: process for auto-configuration and determining the correct configuration
5. Moving Scholars closer to core - next steps
   1. SelectQueryDocumentModifier
   2. Entities: Collection, Concept, Document, Organization, Person, Process, and Relationship
   3. Configuring Solr
6. Moving Data Ingest Task Force forward

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. Renaming of 'master' branch? (ZDNet, BBC)
   1. Guidance from GitHub 
   2. DSpace has done it
   3. Fedora has done it
   4. Samvera is doing it
3. 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
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.

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 

Draft notes in Google-Doc 

Weill Cornell updates

1. AWS deployment
2. Challenges
   • Scalability issues with TDB
   • Can only support one VIVO connecting to one TDB
   • Ingest: direct to TDB is fast... but using SDB direct for initial
     • Reingest is ~3hours with SDB
3. Load balancer over VIVO
4. CloudFront cache
5. 4 CPU 16 GB RAM (t3xlarge)
6. ReCiter as backend datasource for publications
7. Cost: ~$300/month
   • On-prem was ~$40k/year
   • 1000 iops

Actions