Date

08 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. Ralph O'Flinn 
2. Brian Lowe 
3. Michel Heon
4. Julia Trimmer 
5. Andrew Woods
6. Robert Nelson 
7. Benjamin Gross 
8. Kristina Heinricy
9. Don Elsborg
10. Steven McCauley

Agenda

1. Community updates
2. 1.11.0 release updates - targeting this week!

   1. Release Testing - 1.11.0

      1. Data distribution API documentation has been updated
      2. Proxy Editor documentation ticket created
      3. Externalized solr
         1. Still need setup documentation
         2. Still need "custom field" documentation
   2. 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.

   3. Sprint planning (Oct 14-25)
      1. Topics
         1. Provide an orientation to VIVO Scholar for community developers, setting up the environment, and introducing existing documentation
         2. Updating Scholars Discovery defaults for specific institutions such as TAMU including branding, look and feel etc.
         3. Orcid integration: pulling and pushing publications
         4. Decoupling TPF server
            1. or starting with decoupling the triplestore?
         5. Bringing NEMO Freemarker templates into core
         6. Vitro Messaging ?
   4. Special topics for future dev calls?
      1. TDB vs SDB - date?
   5.  In-review tickets
      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.

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

Actions

Previous Actions