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
- Andrew Woods
- Mike Conlon
- Kristina Heinricy
- Don Elsborg
- Huda Khan
- María Amalia Flórez Huertas
- Ralph O'Flinn
- Brian Lowe
Agenda
- Community updates
- i18n efforts (lang-tag on triples, SKOS vs RDFS)
- 1.11.0 release updates - targeting this week!
- Externalized solr
- Still need setup documentation
Still need "custom field" documentation
- Acceptance Tests Results
- Externalized solr
- Sprint updates (Oct 14-25)
- Special topics for future dev calls: TDB vs SDB
- Date?
- Background reading materials?
- What decision are we trying to make?
- In-review tickets
Tickets
Status of In-Review tickets
Notes
- I18n updates. UQAM working on i18n. Suggestion that VIVO Scholars use the language files that VIVO currently uses. All the data should have language tags.
- Release 1.11 is ready to come out
- Acceptance tests run for 1.10 and 1.11. From run to run different results are obtained. Selenium results may be about timing. Tests are not ready to be relied on. Need work.
- Andrew will work on documentation for standing up Solr.
- Benjamin may work on custom fields documentation for 1.11. He has worked through the details.
- Sprint has started. See https://wiki.duraspace.org/display/VIVO/2019-10+Sprint for objectives.
- Scholar needs some kind of neutral look
- Scholar should be able to customize scholar without complex development
- Support for external triple stores
- Support for externalizing triple pattern fragments
- Messaging service to be added to Vitro
- NEMO -- Responsive freemarker templates
- ORCiD
- Sheila Raybun, a LYRASIS person, ORCiD US Consortium representative, has interest in VIVO/ORCiD integration.
- Kristina -- interested in saving the access token acquired through the integration. This would allow the update of the ORCiD record with data from VIVO, and pull down data from ORCiD. Access tokens have scopes. Authentication, update personal details, updating work. Kristina has code that requests the work update access token.
- Maria Amalia -- Anna, ORCiD Mexico, is interested in helping. ORCiD interested in integration of additional fields -- professional background, educational background.
- Mike -- does the planned integration require an institutional member key? Yes, it does.
- What could be done in this sprint? Store the keys.
- The public API key is a subset of the member key. May or may not be sufficient for applications.
- OpenVIVO pulls publications from ORCiD using the open API.
- TDB/SDB
- Brian, Graham, William, Andy Seaborne from Jena required.
- Create a pros and cons
- Some likely outcomes for each option
- Perhaps Brown’s editing work as a special topic for developers
Actions
- Organize a TDB/SDB special topics conversation
- Organize a session on Brown's work on editing