Date

15 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. Mike Conlon
5. Huda Khan
6. Jim Blake

Agenda

1. Architectural fly-in

   1. Straw-chitectures at two levels:
      1. VIVO components
      2. VIVO ecosystem
   2. Deployment models

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

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.  - Benjamin Gross : Does Stefan Wolff 's recommendation resolve the issue?

   2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - (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.  - should be low-hanging

   4. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - 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.  - 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.  - Kitio Fofack ? Benjamin Gross ? Orcid and i18n

   2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Only touches one file

   3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - low-hanging - need one more reviewer

   4. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Is this feature of broader interest?
   5. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Mike Conlon : Correct to assume this is on the ontology team's radar?
   6. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Andrew Woods to look into
   7. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Mostly trivial, with conversation around Tomcat version support
   8. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - relatively straight-forward bug fix
   9. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - An important step for i18n... resolves many other open issues
   10. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - low-hanging, documentation
   11. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Kitio Fofack to review?
   12. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - low-hanging... need one more review
   13. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Mike Conlon: Ontology group?

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. How do we merge the views of future VIVO?
   1. Dealing with the data?
   2.  Where is Core VIVO?
      1. Headless? With UI? New UI?
   3. Tech needed?
2. Reviewing the diagrams
   1. Effort?
   2. VIVO Architecture Future v3 Discussion
3. What is VIVO used for? Reporting? Reviewing Data?
4. Analytics? Real linked Open Data? (Huda’s Work)
5. Don - Wants Real Linked Open Data
6. Consume Data on Demand - Leave the data there
7. Operations vs Open Data (Live Data)
8. Modular VIVO
9. In some of the diagrams why was VIVO there?
   1. VIVO has these items internally
10. APIs? Just SPARQL? JSON?

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.