Date

14 Jan 2020

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. Brian Lowe 
2. Huda Khan
3. Don Elsborg
4. Benjamin Gross
5. Ralph O'Flinn

Agenda

1. Open discussion
   1. Scholars: GraphQL and REST API
      1. Huda: Had considered a single API for VIVO with GraphQL or other implementations under the hood, so technologies or implementations could change without changing the API itself
      2. Ralph: GraphQL actually talking to REST API
      3. Don: Historical reasons: REST API part of TAMU's work with Angular. 
   2. Don: TDB loading is slow
      1. Brian: Haven't encountered a situation where TDB is as slow as SDB. Use SPARQL API.  Sometimes service available can remotely turn off inferencing/indexing.  Plain SPARQL update.  TDB usually better than SDB in this context
         1. May be related to how threads are managed
      2. Don: With RDF delta patch work - if listener is waiting for changes, if that portion could be put on another server, that may relieve resources for the main VIVO app
   3. Huda: Issue (also on email list) around how indexing plays into profile page load.  When information is updated, the first time the profile comes up it takes a long time
      1. Brian: Is she using multiple languages and if there are several? Noticed slow down recently that large publication lists in conjunction with large publication lists and on SDB, slow down possible because of filtering for desired language if operating against a much larger result set from SDB query
      2. Indexing process separate and not much related to the profile page, so it shouldn't be indexing that slows down the profile page
      3. Don: Custom faux properties that use OPTIONAL instead of UNION
      4. Ralph: Sometimes power settings on desktops can mess things up
      5. Huda: Will also suggest coming onto the development call and perhaps sharing screen/participating to help with debugging and/or troubleshooting
   4. Brian: Could be different ways of handling languages (as well as other areas) if were to architect from the ground up in the future
2. In-review tickets 
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   2. 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 

Actions

• Organize a session on Brown's work on editing