Date

19 Mar 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. Benjamin Gross 
6. Jim Blake

Agenda

1. Sprint update

2. Two In-Review tickets that need a push forward:

   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Benjamin Gross ?
      1. Cineca's BlazeGraph integration depends on this
   2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      
      1. Latest and greatest from TIB translations
3. Acceptance tests moved to vivo-community, thanks Jim Blake
   1. https://github.com/vivo-community/vivo-acceptance-tests
   2. How to run it?

4. Search index: approaches for configuration and processes 

5. Mailing list messages

   1. Some triples not getting deleted in VIVO?
      
   2. How can I backup the custom Pages that have been created?
   3. ORCiD Integration - Sync - Muhammad Javed suggesting Jim Blake has clues
   4. input data Vivo last version
6. Next Week: When Androids Dream (codename: androdies) - Huda Khan (PPT version)  ( Relegated to next week but feel free to review/give feedback on slides)

7. 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. Soft balls

      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
         1. Low-hanging, documentation - Mike Conlon, can you give this one a review?
   2. Regular balls
      

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

         1. New

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

         1. Kitio Fofack ? Orcid and i18n

      3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
         1. Is this feature of broader interest?
      4. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
         1. Andrew Woods to look into
      5. 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
      6. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
         1. Relatively straight-forward bug fix
      7. 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
      8. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
         1. Kitio Fofack to review?

8. Received

   Click here to expand...

   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. (re-)Raises interest in reconsidering first-time, every-time, tdbconfig design

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

   3. 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?

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

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

• Sprint update

• Among those present, Benjamin and Jim are limited participants.

• Ralph is starting work with search tasks

• Andrew starting work with Docker tasks

• Mike: Thoughts on documentation for new installation process?

• Ralph: The new process is much more straightforward. Mike: A button would be good. Ralph: Not quite.

• This is for 1.11 correct? Yes.

• Thoughts on when 1.11 may be released? By conference?

• Andrew: Rumblings in community that we may have enough content to make a release now. 1.10.1 or 1.11 up for discussion. The dockerization and search updates would definitely be for 1.11.

• Mike: If integration testing could be done for the next version, that’s a huge step forward

• Ralph: Could use just a little time for the community to play with it more, test it. Especially with big changes like Docker.

• Mike: Maybe a release candidate for conference? Or soon, so it’s ready/released for conference? Would like to have the tools to run tests.

• Andrew: If we achieve goals of merging search branch and complete dockerization (VIVO, Solr, MariaDB containers) we should have a release candidate.

• Don: Looking at doing Maven build via Docker, begin with normal 2 stage (VIVO + Vitro) build.

• What are expectations for skills needed to build and deploy for sysadmin vs dev ops? Don: Most people seem to be a combo, should be fine with using Docker and git.

• Andrew: You can point Docker toward your modified runtime.properties which gets us toward a single command spin up

• Andrew: Ralph, you need any support? Ralph: Nope!

• Tickets that need addressed: https://wiki.duraspace.org/display/VIVO/Design+-+External+Search

• Two In-Review tickets that need a push forward:

• VIVO-1641 - Replace afn:localname / afn:namespace with cross-platform equivalent IN REVIEW  - Benjamin Gross ?

• Cineca's BlazeGraph integration depends on this

• Benjamin and Ralph to review https://github.com/vivo-project/VIVO/pull/96

• VIVO-1661 - Merging VIVO-DE community translations into code base IN REVIEW
  
  

• Latest and greatest from TIB translations

• Andrew: this is a classic at this point. Pushes us way forward on i18n support. Kitio left his position for another position at a company :*(

• Benjamin: Any tips on how to test this?

• Observation: the only files touched that affect anything but the german language is the pom.xml files.

• Benjamin: Will check for missing all.properties strings that have been added in english since the time of this pull request

• https://github.com/vivo-project/VIVO-languages/pull/18

• https://github.com/vivo-project/Vitro-languages/pull/7

• 
  

• Acceptance tests moved to vivo-community, thanks Jim Blake

• https://github.com/vivo-community/vivo-acceptance-tests

• How to run it?

• Jim: Doing some additional work to make it more useful for the next person that gives it a shot

• Jim: I’ve made considerable progress

• Search index: approaches for configuration and processes

• Huda added this…? Calling out Jim. Jim: Can we use existing code to populate multiple search indexes? Internal + external. Brian Lowe called it hacky, but at least Jim could finish it. Huda said it was silly that application setup code is sitting in the display graph (search indexer configuration). Jim to talk to Huda more about it.

• Mailing list messages

• Some triples not getting deleted in VIVO?

• How can I backup the custom Pages that have been created?

• ORCiD Integration - Sync - Muhammad Javed suggesting Jim Blake has clues

• input data Vivo last version

• - Is this a very old version of VIVO? Hard to help until we know.

• Next Week: When Androids Dream (codename: androdies) - Huda Khan (PPT version)  ( Relegated to next week but feel free to review/give feedback on slides)

• Status of In-Review tickets

Benjamin: to answer the question posed for VIVO-1656, yes it is of broader interest because it is a prereq for https://jira.duraspace.org/browse/VIVO-1415

Actions

•   Unable to locate Jira server for this macro. It may be due to Application Link configuration. - Brian Loweis reviewing
• Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Mike Conlon, can you give this one a review?
• Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Benjamin Gross to review
• Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Benjamin Gross to re-review

Previous Actions