Versions Compared

Old Version 3

changes.mady.by.user Paul Albert

Saved on

compared with

New Version Current

changes.mady.by.user Andrew Woods

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. William Welling 
  2. Andrew Woods
  3. Alexander (Sacha) Jerabek  
  4. Benjamin Gross 
  5. Huda Khan 
  6. Ralph O'Flinn (star)
  7. Brian Lowe
  8. Nicolas Dickner
  9. Michel Héon
  10. Sarbajit Dutta
  11. Paul Albert
  12. Don Elsborg

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. Jira
      serverLYRASIS JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyVIVO-1443
      1. Third-tier builds?
  4. Solr configuration
    1. Jira
      serverLYRASIS JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyVIVO-1752
      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 forwardWCM approach (Sarbajit, Paul)DeploymentWCM's repo
  7. SDB vs. TDB
  8. Kubernetes
  9. Ingest
    1. ReCiter Connect

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. Jira
      serverDuraSpace JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyVIVO-1688
    2. Jira
      serverDuraSpace JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyVIVO-1751
    3. Integration test opportunities with the switch to TDB - requires startup/shutdown of external Solr ..via Maven
      1. Jira
        serverDuraSpace JIRA
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyVIVO-1752

...

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

  •