Date

15 Jun 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 Kampe 
3. Georgy Litvinov 
4. Michel Héon 
5. William Welling 
6. Benjamin Gross 
7. Ralph O'Flinn
8. Don Elsborg 

Agenda

1. Announcements
   1. Welcome Georgy Litvinov to VIVO committers team!
2. Mailing list / Slack discussion
   1. ORCID authentication
3. 1.12.0 RC1 issues to test/merge:

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

5. VIVO WCAG 2 A/AA  accessibility audit results from Deque
6. Speeding up / simplifying our processes: how do we turn out releases more quickly?
7. Moving Scholars closer to the core : continuing discussion from last committers' meeting
   1. "win/win" opportunity: Scholars and VIVO both eliminate some complexity
   2. converting Scholars SPARQL queries to VIVO DocumentModifiers
   3. replacing URIFinders with fast, reliable Solr lookups 
8. Prioritizing future development items: https://docs.google.com/spreadsheets/d/103P9P4v6yUBSb5BnVaK40NoGx1fIYyL8uaHKUubZWbE/edit?usp=sharing
9.  
10. VIVO in a Box current document for feedback:

Future topics

1. Prioritizing and planning post-1.12 development
2. Forward-looking topics:
   
   1. frameworks: Spring / Spring Boot / alternatives
   2. Horizontal scalability
   3. Deployment
   4. Configuration : files / environment variables / GUI settings
   5. Editing / form handling
   6. Adding custom theming without customizing build
3. Post-release priorities
   
   1. Ingest / Kafka
   2. Advanced Role Management
   3. Moving Scholars closer to core - next steps
4. Vitro JMS messaging approaches - redux
   1. Which architectural pattern should we take?
   2. What should the body of the messages be
5. 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

• Georgy is new VIVO Committer.

1. Orcid authentification. Brian adapted working open orcid authentication to make it work with current VIVO.  Making Orcid authentication work. When it gets callback from Orcid, if it finds Orcid profiles if there are any publications do not exist in VIVO profiles, then it redirect to page to claim publications. If it doesn’t find any new publication it redirects to current profile. If no profile found then it should notify that profile wasn’t found. It was 1.2 
2. Release ahead. We can remove many of items from list fairly quickly.
1. VIVO-1999 CI Hooks when you make PR doesn’t know how to get VIVO-languages and Vitro-languages. Proper order of publishing new versions for VIVO-languages Vitro-languages, then Vitro, then VIVO. Automated tests don’t know about that order, so we should ignore warning on PRs. Ralph is going to test VIVO-1999.
2. VIVO-1996 Georgy have tested and will merge that.
3. VIVO-1987 Not reproduced. Shouldn’t be a blocker
4. VIVO-1985 Should consistently pick the same value, if hash corresponds to valid value in triple store it should work. Now if one use a pencil icon, change language in an opened form, new values will be created. Interface will allow creating multiple items in that case. That is not easy to address or we would need some sophisticated logic to work with it. Let that issue for next releases. Georgy will merge fixes for this issue.
5. VIVO-1983 Benjamin Gross will try to rebuild and test PRs to fix it today.
6. VIVO-1534 The only thing left to do is to add this to 1.11 documentation. 1.12 documentation is already updated. Benjamin Gross wil fix that too.

Should we clean comments in i18n classes? Not right before the release. Maybe we will prepare the release on friday. We will have Monday to fix anything.

Should we include in the release tar file VIVO-languages and Vitro-languages?

Ralph will add all four of them to the release download list.

1. VIVO WCAG 2 A/AA  accessibility audit results from Deque. ~300 issues. Most issues are color contrast issues. Ralph was trying browser plugin to figure out what to change to fix that issues. Theme looks the same mostly, just little tweaks all over the freemarker templates.

Draft notes on Google Drive