Date

14 Apr 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. Don Elsborg
   
2. Andrew Woods
3. Huda Khan 
4. Benjamin Gross 
5. Ralph O'Flinn
6. Brian Lowe
7. Michel Héon 
8. Alexander (Sacha) Jerabek
9. William Welling
10. Mike Conlon
11. Steven McCauley
12. Nicolas Dickner

Agenda

1. Sprint updates - i18n
   1. Reviewing the plan for integration with 'master' branches 
   2. Sprint JIRA board
   3. Outstanding tasks
      1. Update/Test German language files
      2. Documentation
      3. Testing update functionality
      4. Potential architectural refactoring
      5. Selenium testing
   4. Meetings
      1. Sprint check-in tomorrow at 10am ET
      2. Sprint retrospective Friday at 10am ET
2. vivo-tech emails
   1. How to remove people from Vivo - two solutions are being suggested... could someone create JIRA tickets?
      1. > a nice feature in the UI would be a deletion option that allows you to delete the primary object, plus whatever else is created via the UI when you create a new object. It could re-use the logic in the form controller 
      2. > Another possibility would be an automatic deletion of orphan objects: vcards without individuals, publications without authors, and for us membership without members. This could take place synchronously or asynchronously, through a script
3. Vitro JMS messaging approaches - redux
4. Moving tickets forward
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - back on your plate, Mike Conlon
5. Who is working on what? - Are there active tickets in-progress?
   1. 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.

6. 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