Date

22 Jan 2019

Call-in Information

Time: 11:00 am, Eastern Time (New York, GMT-05:00)

To join the online meeting:

• Go to: https://duraspace.zoom.us/j/823948749
• Or iPhone one-tap :
  • US: +14086380968,,823948749#  or +16468769923,,823948749#
• Or Telephone:
  • Dial(for higher quality, dial a number based on your current location):
  • US: +1 408 638 0968  or +1 646 876 9923  or +1 669 900 6833
  • Meeting ID: 823 948 749
• International numbers available: https://duraspace.zoom.us/zoomconference?m=Qy8de-kt6W4fMMDQCAV_3qfH1W-lxAo5

Slack

• https://vivo-project.slack.com
  • Self-register at:   https://goo.gl/forms/JxQFkut4TYj4Ehww1 
    

Attendees

 Indicating note-taker

1.  Don Elsborg
2. Ralph O'Flinn 
3. Andrew Woods
   
4. Huda Khan 
5. Jim Blake
6. Brian Lowe
7. Benjamin Gross

Agenda

1. Comments? Architectural fly-in updates

2. Mailing list messages

   1. jquery.scrollTo error - Do we need to upgrade `jquery_plugins`?
   2. No Subject - "How can I add more associated profiles for that particular  editor."
   3. Freemarker Template Error
      
   4. [vivo-tech] help regarding the custamization
      
   5. [vivo-tech] Inferencing engine not adding triples needed
      
   6. CODE4LIB list: rdf and doi's - thanks Marijane White
      

3. Received

   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.

   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  

      1. Benjamin Gross : Pending response to code review

   2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  

      1. (re-)Raises interest in reconsidering first-time, every-time, tdbconfig design

   3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  
      1. Should be low-hanging

   4. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  

      1. Where does this stand? What is needed to add more person identifiers to VIVO?

   5. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  
      1. Mike Conlon : thoughts on where this stands?

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

   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  

      1. Kitio Fofack ? Benjamin Gross ? Orcid and i18n

   2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  

      1. Only touches one file

   3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  

      1. Low-hanging - need one more reviewer

   4. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  
      1. Is this feature of broader interest?
   5. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  
      1. Andrew Woods to look into
   6. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  
      1. Mostly trivial, with conversation around Tomcat version support
   7. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  
      1. Relatively straight-forward bug fix
   8. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  
      1. An important step for i18n... resolves many other open issues
   9. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  
      1. Low-hanging, documentation
   10. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  
       1. Kitio Fofack to review?
   11. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  
       1. Low-hanging... need one more review

5. Bugs (1.11)

   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

1. Comments? Architectural fly-in updates

1. Aligning ingest and interface concerns with the current work

2. Be helpful to revisit Brian’s diagram at beginning of this fly-in prep meeting

3. Combine: Stanford’s work into RIALTO

4. Having indexing/reasoning etc. be separate components that can be configured/set up as desired

1. Currently indexing is done in a background thread triggered on edit events

1. Not to say those threads are lower priority

2. Since on the same processor, may slow things down

3. 2/3rds of the way there as far as being able to trigger reindexing based on events separately

4. Bottleneck is still triplestore since index building depends on Sparql queries and does not depend on search index being externalized

1. Weill Cornell was using Virtuoso but perhaps they are no longer using that

5. Original push for having a plug and play triplestore so people could try out different back-ends to see what works for them since performance issues

1. Seems to have been deprioritized with SDB performance improvements

6. Triplestore replacements will require extensive testing/evaluation

7. Performance upgrades in one context may yield differing results in other areas

8. Triplestore canonical data: the current architecture’s assumes this to be the case.  Do we carry that forward?

1. If not triple-centric, then what does that mean? Practical implications? New code-base?

2. Linked data at input/output but spectrum of possibilities for internal architecture

3. Decoupling vs radical departure?

4. If swapping out triplestores, need testing.  Technical challenge of writing the code is dwarfed by assessing whether this does what we want it to do?

1. If stepping away from triples, task got a lot bigger

9. Inclination to tease things apart - be able to integrate smoothly in ecosystem where triplestore is not necessarily canonical data

10. Inclined to hear about architectures where triplestores not “central”: what is the role of triples in this ecosystem

11. https://sul-dlss.github.io/rialto/architecture for reference

2. Inferencing is a blocking call

5. UI separation

6. Don is asked for general reflections:

1. For VIVO core group, incremental changes.  Product evolution group: GraphQL, PostgreSQL etc…

2. Performance issues not terrible for the profiling system in his experience

3. Shortcomings of SDB to not handle "optionals" so have to do unions and constructs

4. Would like to see VIVO do linked open data. So close

5. With something like Blazegraph and/or performant triplestore, would want to do get all the data (not just public) - should be easy to export data and import it into another triplestore and query like a data warehouse

6. Since using Symplectic, not invested in features for bringing in external publications, etc. but can see that as useful and perhaps that needs to be a separate module

2. Mailing list messages

1. Freemarker template errors: that old nugget

2. Not all inferencing happening

3. Messages from agenda:

1. jquery.scrollTo error - Do we need to upgrade `jquery_plugins`?

2. No Subject - "How can I add more associated profiles for that particular  editor."

3. Freemarker Template Error

4. [vivo-tech] help regarding the custamization

5. [vivo-tech] Inferencing engine not adding triples needed

6. CODE4LIB list: rdf and doi's - thanks Marijane White

Actions

Previous Actions

• Brian Lowe  confirm LDF server issue with TDB content stores
• 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.