Date

16 23 Jun 2020

Call-in Information

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

...

• 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. Brian Lowe 
3. Ralph O'Flinn 
4. Andrew Woods
5. Nicolas DicknerJeff Tyzzer
6. Michel Héon
7. Huda Khan
8. Don Elsborg
9. Alexander (Sacha) Jerabek

Agenda

1. Updates from vivoconference.org
   1. Add your input: VIVO Development Priorities - 2020
2. Sprint updates - i18n - (scrum board)
   1. Criteria for merge to 'master'
   2. Selenium testing

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

         1. UQAM wiki documentation

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

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

3. Renaming of 'master' branch? (reference)
4. Bugs/Issues
   1. Mailing list (vivo-tech)
      1. Global Transaction Identifier Setting in MySQL
   2. Solr configuration needs updates: 

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

      1. Potentially related: 

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

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

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

       - Will potentially simplify i18n '.ftl' files
5. Tickets to be reviewed

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

       - one more reviewer needed

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

    - low-hanging and urgent... or else we will fall out of date again

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

   3. 
      

      Expand
      Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=14416 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

      
      

6. Who is working on what? - Are there active tickets in-progress?

   1. 
      

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

      
      

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

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

Tickets

1. Status of In-Review tickets

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

   
   

Notes 

Draft notes in Google-Doc 

1. Updates from vivoconference.org
   1. Would be helpful to have additional time between presentations (back to back 15min sessions are tight)
   2. Potentially include input/evaluation survey in email request for improvements
1. Add your input: VIVO Development Priorities - 2020
2. Sprint updates - i18n
   1. Feature summary for the committers
      1. find . -name '*.java'|xargs grep -H UQAM
   1. Michel to look into making the list
   2. Goal to get to master at the end of the sprint
   1. Committers and reviewers should start looking at the i18n branches now so by the end of the sprint it will only be a simple merge request
   2. Best to get the merge completed sooner rather than later to get other requested sync’d
1. Criteria for merge to 'master'
   1. Sprint testing has been thorough and comprehensive
   2. Regression tests will provide assurances

Actions