Date

16 Mar 2021

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?pwd=a2Q3RUVKVkN2dkNHV3FUaFRtLzhGdz09
  • Passcode: 351860

• 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. Brian Lowe
2. Georgy Litvinov 
3. Nicolas Dickner 
4. Michel Héon 
5. Huda Khan 
6. William Welling
7. Benjamin Gross 

Agenda

1. Moving towards RC1
   1. Reverting deployment changes for 1.12
      
      1. https://github.com/vivo-project/VIVO/pull/228
      2. https://github.com/vivo-project/Vitro/pull/217
   2. New issues:
      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. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      4. Permissions problems with page management? Others?
   3. Documentation
      
      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. Using VIVO's Internationalization (i18n) Features
      4. Simplifying end-user/installation instructions while retaining details for developers
      5. Making it easy for people to help with testing : Release Testing - 1.12.0
   4. Other questions
      
      1. Browser plugins that are able to double-submit editing forms? Cause for concern?
      2. Unable to locate Jira server for this macro. It may be due to Application Link configuration. How far did we get with this?
      3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
2. Embracing standard approaches : how do we better align VIVO with other software and make it easier to adopt / install / develop for without having to learn the "VIVO way"?
   1. Possible topics:
      1. Deployment
      2. Configuration : files / environment variables / GUI settings
      3. Frameworks / Spring
      4. Editing / form handling
      5. Adding custom theming without customizing build
3. Post-i18n priorities
   1. VIVO-in-a-box
   2. Ingest / Kafka
   3. Advanced Role Management
   4. Moving Scholars closer to core - next steps

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

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

1. PRs ready to revert deploy strategy.
1. Testing continued… -Georgy and Nicolas
2. To be reviewed and merged for RC1 -Michel and Brian
3. Close to RC1. - Brian
4. https://github.com/vivo-project/VIVO/pulls
5. https://github.com/vivo-project/Vitro/pulls
6. Some PRs requiring second reviews
2. Some new issues.
   1. Not used anymore. Remove entirely. -Brian
   2. What is the meaning of isomorphic in VIVO? - Michel
   3. Jena checks to determine if it is isomorphic… use of blank nodes… -Brian
   4. Check between new and old not returning expected results -Brian
   1. Not new behavior. -Nicolas
   2. Shouldn’t be a blocker and will look into effort for fix. -Georgy
   3. Is there a known issues page for release? -Michel
   1. Regex not supporting UTC
   2. Manual parsing not considering timezone
   1. Can create and delete but can’t edit by a non root user. -Benjamin
   2. Creating an issue and looking into. -Brian
1. Regression with Remove Portal and Tab resources
2. Should VIVO-1971 be blocker for release? -Brian
3. Date timezone issue not able to format with ‘Z’ as UTC.
4. Page management permissions issues?
3. Documentation
4. Other questions
1. EndNote browser plugin causes VIVO docker deployment to make duplicate requests for form submission
2. VIVO-1910 blocker for release and will take a look at -Brian
3. What version in Jira should we use? -Benjamin
4. Precise queries make everything go faster...

Draft notes on Google Drive