Date

03 Jul 2018

Call-in Information

Time: 11:00 am, Eastern Time (New York, GMT-04: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 
    

Development Process

• See https://github.com/vivo-project/VIVO/wiki/Development-Processes

Attendees

 Indicating note-taker

1. Ralph O'Flinn
2. Tim Worrall  
3. Don Elsborg 
4. Andrew Woods 
5. Huda Khan
6. Kitio Fofack  
7. Benjamin Gross
8. Christian Hauschke 

Agenda

1. 1.10 Release updates
2. Mailing list activity
   1. CHANGING THE VIVO FRONT-END (product-evolution?)
   2. Error on root login - updates?
   3. Does Vivo sparql update API support delete/insert operation
   4. internationalization
      
3. New tickets
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  (documentation)
   2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  (Vitro pull-request)
   3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  (jenatools pull-request)
4. Javadocs – Suggested discussion from Don
5. Working towards a unified VIVO technical vision
   
   1. Salient use cases
      • Standard, full-app with focus on profiles
      • Headless component of research intelligence ecosystem
      • Minimal store in support of modern, custom UIs
   2. Multi-source ingest: OpenHarvester, Combine, Reciter, etc
6. Suggested updates from Michael J. Giarlo
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Notes

Draft notes in Google-Doc

Update on 1.10 release

1. The release is officially in process. The testing process revealed some issues, but no blockers and no issues that weren’t there already.
2. Andrew, Ralph, and Kitio developed documentation for the release process, which will be used for future releases
3. Maven/Github process for Jena tools is 50 % finished. 
   1. https://docs.google.com/spreadsheets/d/1TuaZ7s0FjtmKQnDzT9M9U8Vr3yyMTOXrPONbckdW0Aw/edit#gid=1769378986
4. VIVO Ontology (https://github.com/openrif/vivo-isf-ontology / https://github.com/vivo-ontology-lab) is right now not included in the VIVO release. It should be discussed if it has to be handled in a similar way.
5. Different approaches of including the ontology file(s) in the release have to be discussed. Maybe VIVO-ISF could be an artefact/dependency for a specific version of the ontology. Discussion has to be led in the ontology calls (now on Thursdays, was already discussed in https://wiki.duraspace.org/display/VIVO/2018-06-28+Ontology+Improvement+Call).
6. Release is to be expected this or next week.
7. Don raises the question which heavily customized VIVOs will upgrade to 1.10 soon. Ralph will most likely will do it in the next weeks.

Mailing list activity

1. CHANGING THE VIVO FRONT-END
   1. Is there a technical solution to solve the performance issues?
   2. More information need to answer question (which API etc.)
   3. Using the Solr index could be a possibility.
   4. Issue for product-evolution? 
2. Error on root login - updates?
   1. Don: How can we make things easier to work on data in VIVO. Right now too much knowledge is necessary (what is in firsttime/everytime etc.) to work on the data.
   2. Huda: It’s better designed to do changes through the interface. There is work to do with respect to where something is stored and how it is used. We need more coherence and consistency.
   3. Don will document his use case of changing a label and respond to the mail thread.
3. Does Vivo sparql update API support delete/insert operation
   1. VIVO should support delete/insert operations.
4. Internationalization
   1. The #I18n channel has agreed on having a I18N call on 17th July 2018 just before the developer’s call (1pm UTC, 9am EST and 3 PM Hannover).
   2. I18N issues will be strategies to maintain language versions, release processes, multiple language support for the interface. The latter will be (maybe) mainly a usability challenge. MLS in OJS could serve as a model.
   3. Kitio will announce the call on the mailing list and provide some information.

New tickets

1. Update Vitro documentation. We need a space to document Vitro.

Previous Actions

• Don Elsborg to document "firsttime" resolution in CU BOulder wiki, circulate this doc to email list and discuss as a team how to integrate this in VIVO documentation

Actions

• ...