Date

04 Aug 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. Benjamin Gross
2. Huda Khan 
3. Don Elsborg 
4. Rachid Belkouch
5. William Welling 
6. Andrew Woods
7. Alexander (Sacha) Jerabek 
8. Brian Lowe 
9. Ralph O'Flinn
10. Michel Héon

Agenda

1. Announcements
   1. Andrew Woods on holiday next week
2. VIVO Roadmapping
   1. Product Direction for 2020
   2. Driving priorities
      1. Lowering barriers to adoption and contribution
      2. Modernizing architecture and administration
      3. Improving front-end user experience
   3. Focal areas
      1. i18n
      2. Ingest
      3. Improved frontend
      4. APIs (JSON data)
      5. Messaging
      6. Installation
      7. Upgrades
      8. Documentation
      9. Modularity
      10. Publication claiming
      11. Advanced role management
3. Next i18n sprint - Aug 24 - 28
   1. Necessary pre-sprint work?
4. Data ingest task force
   1. Slack: #dataingest
   2. Wiki landing page?
5. VIVO Scholars - next steps
   1. Indexing into core Solr index... with Scholar entities
   2. Tying into existing core indexing pattern
   3. Will allow for layering Scholar's REST-API, GraphQL endpoint, and UI over core Solr index

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 

Actions