...
Indicating note-taker
- Andrew Woods
- Brian Lowe
- Ralph O'Flinn
- Benjamin Gross
- Don Elsborg
- Pierre Roberge
- Alexander (Sacha) Jerabek
- Steven McCauley
- Maxime Bélanger
- Amin Keshavarz
- Rachid Belkouch
- Nicolas Dickner
- Mike Conlon
- Brock Balducci
- Hector Correa
- María Amalia Flórez Huertas
- Huda Khan Michel Héon
Agenda
- Community updates
- VIVO Scholars
- Brown demo - read/write UI on VIVO
- Special topics for future dev calls
- In-review tickets
- need 1 more reviewerJira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1726
- need 1 more reviewerJira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1729
- need 1 more reviewerJira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1733 Expand Jira server DuraSpace JIRA jqlQuery filter=14416 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
- Short-term development activity
- Extract ontology from core codebase
- Extract languages from core codebase
- Move from 'develop' to 'master' branch
- Review of vivo-project repos for appropriateness of being supported by Committers
...
Recording
- Slides: https://figshare.com/articles/A_new_editing_frontend_for_VIVO/9792176/1
- 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.
- 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.
- Challenges and opportunities
- 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)
- 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)
- Documentation based on Flask SQLAlchemy
- Using Describe query to get all RDF with the app that sits on top of it filtering the appropriate information
- 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)
- 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.
- High level API for graph data generation would be desirable.
- 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
...