Date

17 Aug 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. William Welling
4. Huda Khan
5. Alexander (Sacha) Jerabek 
6. Dragan Ivanovic 
7. Sandra Mierz 

Agenda

1. Further investigation of the mailing list issue
   1. schema.org missing authors? https://groups.google.com/g/vivo-tech/c/MAoUdgZYOwo/m/uPswpzD_AgAJ?utm_medium=email&utm_source=footer
2. The issue reported via Slack by Naveen Sadhu: "Hello..We use pypubmed harvester process to retrieve additional information for publications like subject areas, keywords. Recently we had issues : duplicate subject areas in our VIVO application. We are using pypubmed python script to check vivo(our app) data against pubmed central repository and add subjectareas if not available.  I did check python script that we are using and no issues there. Anyone faced similar issues before? Any help would be greatly appreciated."
3. Small(er) development items for 1.13 (https://docs.google.com/spreadsheets/d/103P9P4v6yUBSb5BnVaK40NoGx1fIYyL8uaHKUubZWbE/edit?usp=sharing) vs decoupling UI (frontend) from backend 
4. JIRA vs GitHub issues
   1. "Andrew: have meeting with Tim Donahue of DSpace project. DSpace has already done a similar transition.  Will ask for feedback/advice." 2020-12-08 - VIVO Development IG
5. Merging developers and committers calls? 
6. 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. JSON entities in/out
      
      1. Apache Marmotta LDPath syntax https://marmotta.apache.org/ldpath/language.html
      2. JSON-LD framing: https://www.w3.org/TR/json-ld11-framing/
         1. Is round-tripping a potential benefit?
      3. Defining exercises for evaluation
   3. Ontology model for defining form behavior
7. 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 

Needing reviews

1. 1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   2. https://github.com/vivo-project/Vitro/pull/242
   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.
   5. Unable to locate Jira server for this macro. It may be due to Application Link configuration.

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

Task List

• Benjamin Gross to respond to schema.org issue email on listserv