Date

09 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. Benjamin Gross 
3. Nicolas Dickner 
4. Georgy Litvinov 
5. Benjamin Kampe
6. Michel Héon 
7. Huda Khan 
8. Alexander (Sacha) Jerabek
9. Ralph O'Flinn  

Agenda

1. Alpha release
   1. Configuration: context.xml and runtime properties
      
      1. Simplifying the changes
      2. app-name : is it necessary?
      3. Maven lifecycle semantics : install versus package
   2. Upgrades from monolingual to multilingual VIVO with ingested data
      1. Behavior with language-less literals
      2. Are we satisfied with providing documentation vs. tooling?
   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. Documentation for multilingual editing
         1. Existing document: How an End-User Can Use the i18n Features
            1. Should it be moved closer to profile editing documentation?
            2. Expand with text about class/property/faux property label/definition editing?
   4. Other questions
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration. License text: should other changes be considered?
      2. Mailing list: Page management entries and /vis request routing.
         1. Any issues that should be addressed immediately?
         2. 404 versus invalid parameter errors.
         3. Future improvements for adding link-only (no content) menu entries.
      3. Browser plugins that are able to double-submit editing forms? Cause for concern?
      4. Unable to locate Jira server for this macro. It may be due to Application Link configuration. How far did we get with this?
   5. Blockers
      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. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
2. New developments
   
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration. Configurable SPARQL queries for comprehensive individual deletion operations
      
      1. 1. Pull request for testing:
            1. https://github.com/vivo-project/Vitro/pull/213
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.

Draft notes on Google Drive