...

1. Andrew Woods
2. Mike Conlon
3. Huda Khan 
4. Kristina Heinricy 
5. Don Elsborg
6. María Amalia Flórez Huertas
7. Ralph O'Flinn
8. Brian Lowe
9. Sacha Jerabek
10. Steven McCauley
11. Jose
12. Benjamin Gross
13. William Welling
14. 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. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1718

          - functionality review via Vagrant 

      2. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1723

          - test steps well-defined

      3. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1728

          - documentation review
4. Special topics for future dev calls
   1. 2019-12-06 - Special Topic - TDB vs SDB
5.  In-review tickets 

   1. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1704

       - need 2 reviewers

   2. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1726

       - need 1 reviewer

   3. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1729

       - need 2 reviewers

   4. 
      

      Expand
      Jira server DuraSpace JIRA jqlQuery filter=14416 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

      
      

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

...

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

...