Date

14 Jul 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. Nicolas Dickner 
3. Huda Khan 
4. Don Elsborg 
5. Rachid Belkouch
6. William Welling
7. Andrew Woods
8. Alexander (Sacha) Jerabek
9. Jeff Tyzzer
10. Brian Lowe
11. Ralph O'Flinn

Agenda

1. Mini-sprint focused on VIVO committer review/refactor: July 14-16th
   1. Next i18n sprint? - July 24th? Aug 24th?
   2. Scrum board
   3. Needing review / merge:
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   4. Concerns:
      1. Homogenize design for filtering languages between frontend and backend approaches
      2. Upgrading... reorganization of firsttime/everytime
      3. Resolution on split-out of language files:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
2. 2020-07-15 - Special Topic - VIVO Scholar Next Steps
   1. What is your opinion?
3. Renaming of 'master' branch? (ZDNet, BBC)
   1. DSpace has done it
   2. Fedora has done it
4. Moving priorities forward: Data ingest
   1. Task force!
      1. Deliverables?
      2. What are the use cases?
   2. Tools:
      1. RML-Mapper
      2. Ingest Tools - Who Is Using What
   3. Entities (scholars-discovery model) (fly-in discussion):
      1. Person, Grant, Publication, Authorship, ...

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