Date

29 Oct 2019

Call-in Information

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

To join the online meeting:

• Go to: https://lyrasis.zoom.us/my/vivo1

• One tap mobile:

  • US: +16699006833,,9358074182# or +19292056099,,9358074182#

• Or Telephone:

  • US: +1 669 900 6833 or +1 929 205 6099 or 877 853 5257

  • Meeting ID: 935 807 4182

• International numbers available: https://zoom.us/u/aeANHanzED

Slack

• https://vivo-project.slack.com
  • Self-register at: http://bit.ly/vivo-slack
    

Attendees

 Indicating note-taker

1. Andrew Woods
2. Mike Conlon
3. Huda Khan 
4. Kristina Heinricy 
5. María Amalia Flórez Huertas
6. Ralph O'Flinn
7. Brian Lowe
8. Sacha Jerabek
9. Steven McCauley
10. Benjamin Gross
11. William Welling
12. Sheila Rabun

Agenda

1. Community updates
   1. Next release manager?
2. Orcid community integration patterns - Sheila Rabun
3. Sprint updates (Oct 14-25)
   1. Status of tickets
   2. Reviews needed
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - functionality review via Vagrant 
      2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - test steps well-defined
      3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - documentation review
4. Special topics for future dev calls
   1. 2019-12-06 - Special Topic - TDB vs SDB
5.  In-review tickets 
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - need 2 reviewers
   2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - need 1 reviewer
   3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - need 2 reviewers
   4. 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.

6. Short-term development activity
   1. Extract ontology from core codebase
   2. Extract languages from core codebase
   3. Move from 'develop' to 'master' branch

Tickets

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

Notes 

Draft notes in Google-Doc

Sacha interested in VIVO Scholar and Orcid Integration

VIVO Scholar - Mike wants this to be a standing item 

1. Ralph O’Flinn is willing to continue being the release manager.
   1. Noting that it is healthy for the project to have multiple people who are comfortable with the process
2. ORCID.  
   1. Workflow: https://members.orcid.org/api/workflow/RIM-systems
   2. Tutorials (how to read/write, etc.): https://members.orcid.org/api/tutorial
1. Sheila Rabun is a LYRASIS person and supports the US ORCiD consortium members.  ORCiD support outside the US is supported by others -- JISC in the UK, for example. 
2. Public API is limited to fetching public data and using ORCID as an authenticator.
   1. To update data in ORCID, the member API is required.
3. Current development: When one signs on to ORCiD through VIVO, VIVO gets the ORCiD access token.  This can be stored for future use.
4. Webhooks are only available through the Premium API.
5. To pull data down from ORCID, the access token could be used upon login to pull down DOIs and PubMed IDs and pipe them into the functionality already in VIVO.
6. ORCiD Documentation:
3. Sprint updates
1. VIVO Scholar can use either an Angular or React front-end.  Choices of “stack” -- the Freemarker stack, the VIVO Scholar stack with choices of front-end. 
2. Mike: like BMW -- choose a car vendor, choose a model based on technology/lifestyle.  For a car, choose a sports car, a hybrid, an SUV. For VIVO choose a stack. Then choose finishes -- for a car, colors and trim.  For VIVO, theming/local branding.
3. Vitro messaging: A design document for messaging can be done -- perhaps one page, two paragraphs, with a figure would suffice.
4. Need reviewers for the TPF items.
4. Sometime in November -- the Brown presentation on editing

Actions

• Organize a session on Brown's work on editing