Date
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
- Self-register at: http://bit.ly/vivo-slack
Attendees
Indicating note-taker
Agenda
- Open discussion
- Scholars: GraphQL and REST API
- 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
- Ralph: GraphQL actually talking to REST API
- Don: Historical reasons: REST API part of TAMU's work with Angular.
- Don: TDB loading is slow
- 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
- May be related to how threads are managed
- 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
- 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
- Scholars: GraphQL and REST API
- In-review tickets
Tickets
Status of In-Review tickets
Notes
Actions
- Organize a session on Brown's work on editing