Date

20 Jul 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
9. Huda Khan 
10. Dang Vu Nguyen Hai
11. Christoph Gopfert

Agenda

1. Announcements
   1. via David Wilcox: VIVO in a Box town hall

      1. This is just a reminder that the VIVO in a Box town hall meeting will take place on Monday, July 26, at 11am EDT / 5pm CEST. Please use this link to register for the meeting and generate a calendar invite in your timezone: https://lyrasis.zoom.us/meeting/register/tJwqceGvrzwpHdc1g3NSgvHOhRlLF3mCjY_r.

         You can read and comment on the proposal here: https://docs.google.com/document/d/1JOO2mUlGcc1eAXJG5k-7r86FyE2JKjKOqjFZ5vVp_zI.

2. Unit tests
   1. runOrder fix ready for 1.12.1 – just needs branch to merge into Unable to locate Jira server for this macro. It may be due to Application Link configuration.
3. List of desired development items:
   1. quick wins / items for a more rapid release
   2. collaborative items for future sprints
   3. (Add/edit at will) spreadsheet: https://docs.google.com/spreadsheets/d/103P9P4v6yUBSb5BnVaK40NoGx1fIYyL8uaHKUubZWbE/edit?usp=sharing
4. Defining shapes or subgraphs for use in APIs, edit forms, indexes etc.
   1. Diagrams:
      1. existing architecture: https://docs.google.com/presentation/d/1raO98mklGUQgAc6wMMbgDEsHVk1zoCA3bq4Fyy21GjI/edit?usp=sharing 
      2. Georgy: existing versus proposed
         1. 
   2. Results of initial experiments with SHACL
   3. Defining concrete next steps
      1. Ontology model for defining form behavior?
      2. N3-based templates?
         1. Deriving indexing / display queries?
   4. Mapping to simplified JSON objects for data ingest
      1. Inspiration? William Welling: Apache Marmotta LDPath syntax https://marmotta.apache.org/ldpath/language.html
5. Moving Scholars closer to the core
   1. Build messaging system first? versus
   2. Original option of typing into existing document modifiers:
      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 

References

1. 2019-01 Architectural Fly-in Summary#201901ArchitecturalFlyinSummary-Ingest
2. 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

Draft notes on Google Drive