Date

19 Nov 2019

Call-in Information

Time: 11:00 am, Eastern Daylight 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. Andrew Woods
2. Ralph O'Flinn 
3. Benjamin Gross
4. Alexander (Sacha) Jerabek
5. Steven McCauley
6. Mike Conlon
7. Brock Balducci
8. Hector Correa
9. María Amalia Flórez Huertas
10. Huda Khan

Agenda

1. Community updates
   1. VIVO Scholars
2. Brown demo - read/write UI on VIVO
3. Special topics for future dev calls
   1. 2019-12-06 - Special Topic - TDB vs SDB
4.  In-review tickets 
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - need 1 more reviewer
   2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - need 1 more reviewer
   3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - need 1 more reviewer
   4. 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.

5. Short-term development activity
   1. Extract ontology from core codebase
   2. Extract languages from core codebase
   3. Move from 'develop' to 'master' branch
6. Review of vivo-project repos for appropriateness of being supported by Committers

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

Recording

• http://bit.ly/2019-11-vivo-read-write-ui

1. Slides: https://figshare.com/articles/A_new_editing_frontend_for_VIVO/9792176/1
2. Brown began with a separate front-end (based on Rails) that speaks to the Solr index generated based on the VIVO Solr index.  They also created an editing front-end (since the original VIVO editing front-end was considered too cumbersome) which relies on a Django/flask application that communicates directly with the VIVO triple store.  
3. The current motivation is to combine the display and editing front-ends into a single interface, where display and editing would still be funneled through different application areas but the end-user would not know the difference.
4. Challenges and opportunities
   1. ORM (Object Relational Mapper): Mapping graph structure to object/dictionary/hashmap (based on your particular programming flavor) appears to be straightforward (although weed-level may be complicated)
   2. Stateless state of graphs eliminates some of the complexities with other ORM work (don’t need to consider integrity checks/form key validation as deletes in a graph are pretty straightforward) 
   3. Documentation based on Flask SQLAlchemy
   4. Using Describe query to get all RDF with the app that sits on top of it filtering the appropriate information 
   5. Steve says the end is in sight.  Who wants to get Steve and Hector doughnuts when the end is in fact here? (Not THE end, but the end of this work)
1. Multiple points of interaction with the triplestore with multiple systems adding RDF where the RDF content is inconsistent with respect to shapes/content.  Aiming for all RDF production and ingest to be brought together at a single point using the Flask app. 
2. High level API for graph data generation would be desirable.  
5. Andrew: Given the probable reliance on well-defined JSON shapes/expectations, would be good to compare this work with the VIVO Scholars work

Actions

• Organize a session on Brown's work on editing