Date

20 Apr 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. Michel Héon 
4. Nicolas Dickner 
5. William Welling 
6. Huda Khan 
7. Benjamin Gross 

Agenda

1. 1. Blocker issues
      

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

2. Defining a "VIVO in a Box" project
   1. Compiling feedback for Leadership
   2. Draft set of problems/features to consider in planning VIAB: https://docs.google.com/document/d/1lfTzXSXrtpRVT3CVWAj55XOou94kIg7QJ2NrHPQewUM/edit?usp=sharing
   3. Reference slides: 
3. Other topics?

Future topics

1. 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
2. Post-release priorities
   
   1. Ingest / Kafka
   2. Advanced Role Management
   3. Moving Scholars closer to core - next steps
3. Vitro JMS messaging approaches - redux
   1. Which architectural pattern should we take?
   2. What should the body of the messages be
4. 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

1. Blocker issues

Two issues need committer to push the button: 

https://github.com/vivo-project/VIVO/pull/235

https://github.com/vivo-project/Vitro/pull/215

Issue added today as a blocker is VIVO-1343. 

Christian submitted 4 years ago. Language attribute is hardcoded to “en”. A lot of templates should be changed. Bad for web crawlers as wrong lang value could problems for web crawlers. Brian is going to look into this issue.

Before release we need to check documentation is correct.

We hope to release RC1 next week.

1. William prepared a google document with a set of problems and features to consider in planning VIAB.

Link to google document is in agenda (b).

Try to give feedback to the leadership group about issues we see so they could define what VIAB should be.

How can we propose to leadership group things that could be advantageous for VIVO? It would be good to prepare document for next leadership group meeting.

What is the advantage of having data in RDF?

First issue in the document is Data Ingestion.

We need a simple way for data ingestion. For now there are several options for data ingest: 

• reCiter the only open source way for data ingest. Currently dependent on pubMed. To make it source agnostic there a lot of development needed.
• WoS or Scopus (already do disambiguation work) could be used as a paid source for people profiles, ingest them as a vCards with manual disambiguation.
• Get ORCIDS and get data from ORCID IDs, match publications to people, keep others as vCards. Manual disambiguation in VIVO. Manual claiming.

With RDF it is easier to find errors. All dirty data becomes visible in VIVO.

Pure (VIVO competitor) have disambiguation plugin, that already working but stores data in a relational database. It also ingest external information about faculty members, extending information added manually. VIVO users anticipate similar behaviour.

William: For Universities, to get VIVO components and simplify work with VIVO. Librarians as target administrators for VIVO instances. VIAB should add more simple approach to get and work with data. Lower barrier for Universities because Universities have lack of staff.

Michel: It will be useful to have user stories of VIVO usage, where we can use VIAB, who will be using VIAB.

We should also list components that require development, like editing.

For now it is evidently that components are not ready for packaging into VIAB.

Let's improve the document about VIVO problems and features and provide it for Leadership group.

Draft notes on Google Drive