Date

16 Oct 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. Benjamin Gross 

3. Jim Blake  

4. Andrew Woods 

5. Steven McCauley

Agenda

1. Advanced Role Management 3-day fiesta!

   1. Oct 24th - 26th, come join the fun
   2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.

2. Technical questions

   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - "Removing the ${blankSentinel} value on line 117 of personHasAdvisorRelationship.ftl fixes the problem... but I'm not sure what blankSentinel is supposed to be doing."

3. Done?

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

4. In-Review

   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.

5. 1.10 

   1. bugs (1.10.1?)

      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.

   2. Plans for a 1.10.1 patch release

6. In Limbo
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
7. Recent mailing list topics:
   1. display dataGetters, weird behaviour with vivo:Award
   2. Update from Ontology group? - Add Handle Support in VIVO?

Notes 

Draft notes in Google-Doc

Advanced Role Management 3-day fiesta

1. If you are interested in this feature, please join: Oct 24th - 26th... #develop channel on VIVO Slack
2. So far: Mike Conlon, Jim Blake, Andrew Woods, Ralph O'Flinn(?)
3. Suggestion: review the pull-requests prior to Oct 24th
   1. https://github.com/vivo-project/VIVO/pull/85
      
   2. https://github.com/vivo-project/Vitro/pull/80

Technical questions

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

   1. Two existing forms are used for adding Advisors and Advisees
      1. One form uses ${blankSentinel} the other does not
   2. Tim Worrall and Huda Khan may have more insight into the backstory

RDF documentation

1. Brian Lowe recently added: Application RDF Files
   1. It is great! Is it done?

In-Review tickets

1. Externalized Solr
   1. Andrew Woods to make SmokeTest updates for  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   2. Andrew Woods and Ralph O'Flinn to subsequently move the following tickets forward
      
      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.
   3. A broader developer discussion is needed for moving the pattern of externalized search into {develop}
2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   
   1. Ralph O'Flinn and Andrew Woods to review/test

1.10 bugs

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

   1. Historically, there was a manual build-text file populated during release

   2. Historically, there contained revision detail for each: Vitro, VIVO, third-tier

      1. This seems ideal... but at a minimum, we need the revision details for VIVO
2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   
   1. We should document the required files for new Themes
      1. Benjamin Gross to create ticket
   2. In the meantime, probably sufficient to remove the `<#include flash.html>` from page.ftl
3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   
   1. Stefan Wolff has implemented suggestion from JIRA
   2. Mike Conlon / Brian Lowe to review

Actions

• Benjamin Gross to create new Jira issue for additional errors thrown startup.
  
• Benjamin Gross to create new Jira issue for documenting required Theme files (inspired by:  Unable to locate Jira server for this macro. It may be due to Application Link configuration. )
• Mike Conlon and Brian Lowe to review:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Previous Actions

• 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.  Might there be consequences for the September sprint.