...
- Mike Conlon investigated wikidata un countries
- Less countries then he thinks it should have - 162
- This was entities instance of country – so that’s odd
- Eg Albania wasn’t on the list, sounds inconsistent for country definition
- So how do we work with Wikidata to determine why the list is so short and how is it maintained
- Main question – how do we follow up
- Don +1
- Mikes goal is not to update wikidata data
- Andrew noted that in Sem w3 list a wikidata question was monitored and answered by wikidata folks
- Mike C. — scholia seems very biased, very focused, working on large scale dumps. So if you want all papers from university of x, you might get nowhere
- Don – wikidata should be augmentation - non-authoritative.
- Ralph - wikidata should augment - also to deal with lag
- Don – wants to use wikidata concepts and use VIVO to map concepts between VIVO and wikidata - perhaps use openvivo for this. So try to store sameAs relationships between VIVO and wikidata. #
- Use the VIVO triple store and VIVO editorial interface to maintain these relationships
- Mike - UFL has the same need - Research Intelligence
...
- How to address workflows that bring things in from multiple data stores and store in VIVO
- On the flip side, have exports from VIVO or a canonical data store that pushes data to VIVO.
- Different VIVO front ends - so a read only view
Edit - can edit be separated from the standard view - Complexity added with seperate VIVO and Vitro. # What are the pros/cons of collapsing the two. So who cares about Vitro that doesn’t care about VIVO.
- Steve McCauley - more interested in Vitro than VIVO. He works more with Vitro.
- Mike - Metabolomics (sp?) project also using Vitro with some VIVO ontology
- Steve - will use some Vivo ontology but not all since they departed from the VIVO display.
- Andrew - Steve - are there natural architectural patterns that you would have like?
- Steve - separating the display layer from the rest of the system. Arch is fine since they don’t use it for display. Entirely as a backend.Some things could be changed. Things like externalizing search which would make things more modular. Or database not being tied to SDB/TDB so have a different triple store. Would like ability to swap things in and out. We replicate the VIVO SOLR for back end purposes.
- Mike - a deployment pattern could be that there is no front end. So could have a non vivo front end like Brown. So facts on demand and you put them where you want them. Not all sites want a front end. Just facts.
- Andrew/Mike - research intelligence system
- Don - are we discussing graph, LOD, and semantics
- Mike - semantics allow swapping out entities
Actions
- Mike Conlon to find contacts at wikidata to answer technical questions. We need to know how to interact with the wikidata community when it comes to understanding and validating, or eventually updating their data.
- Don Elsborg to move forward with a firsttime/everytime config model discussion
Previous Actions
- Brian Lowe confirm LDF server issue with TDB content stores
- Don Elsborg to update vagrant for 1.10
- Don Elsborg - add jira tickets for abox/tbox use cases - one ticket for each use case
- Brian Lowe - check with ontology group on handles
- Alex Viggio will bring news of Elasticsearch instead of Solr up with Product Evolution.
...