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
- Brian Lowe
- Ralph O'Flinn
- Benjamin Gross
- Don Elsborg
- Pierre Roberge
- Alexander (Sacha) Jerabek
- Steven McCauley
- Maxime Bélanger
- Amin Keshavarz
- Rachid Belkouch
- Nicolas Dickner
- Michel Héon
- Martin Simoneau
Agenda
- Community updates
- VIVO Scholars
- UQAM i18n demo
- Special topics for future dev calls
- Brown's read/write decoupled UI - Scheduled for next week: Nov 19th
- 2019-12-06 - Special Topic - TDB vs SDB
- In-review tickets
- - need 1 reviewer
- - need 2 reviewers
- - need 1 more reviewer
- Short-term development activity
- Extract ontology from core codebase
- Extract languages from core codebase
- Move from 'develop' to 'master' branch
- Review of vivo-project repos for appropriateness of being supported by Committers
Tickets
Status of In-Review tickets
Notes
Attendees
- Pierre Roberge
- Maxime Bélanger
- Amin Keshavarz
- Rachid Belkouch
- Brian Lowe
- Andrew Woods
- Sacha Jerabek
- Nicolas Dickner
- Benjamin Gross
- Don Elsborg
- Ralph O’Flinn
- Michel Héon
- Steve McCauley
Brief updates on Vivo Scholar
- Ralph is working on some visualizations, making some progress in general; tweaked some dates.
- Monday there will be a Vivo Scholar demo.
- One other item from VIVO Scholar was that we talked about the use of the VIVO/Vitro language files instead of creating a new set.
Internationalization
Recording: http://bit.ly/vivo-2019-11-i18n
Slides: http://bit.ly/vivo-2019-11-i18n-slides
Presentation by Michel Héon:
- Created sample ontology for fr_CA addons
- Includes additional fr_CA labels for entities in the ontology / knowledge base, e.g. “Rhétorique”@fr_CA in addition to “Rhetoric”@en_US .
- Experiences with existing VIVO release:
- Encountered issues with items displayed on the home page lists; mixture of French and English, regardless of language selected by user.
- Editing interface was not aware of language setting; did not record expected language tags.
- Improvements
- Label editor will now add a language tag based on the current language setting of the application. (For example, click the American flag and enter the label for a concept in English. Then, click the Canadian flag and edit the same label but change it to the French version. Both values will be saved with the appropriate language tags.)
- This modification should work for the other custom forms, such as the publication entry form with title and abstract fields, but systematic tests need to be performed to confirm this.
- Capability map now shows values with the appropriate language in the lists, autocomplete and network graph.
- Someone suggested that it might be useful for the capability map to drop concepts that do not have a label in the currently-selected language (strict behavior vs. lax behavior)
- Integration in VIVO 1.10
- Currently built with Maven using an overlay of the internationalization artifacts
- Integration in VIVO 1.11
- Started integration with VIVO 1.11; need to check whether there are changes that need to be merged in.
- Future works
- Unit tests
- Documentation and Github availability
- Andrew: Changes as overlay vs. direct changes to Vitro codebase?
- Michel: When the code is stable, we can integrate it in the main core of Vitro.
- Interim step
- Pierre: proposal is to create a separate project and let the community take from it if desired.
- Ralph: When might we see a pull request? Might not be as complex or controversial a change as it seems.
- Michel: Prefer to use pull requests when teams are working closely together. For now, it would be complicated to work that way.
- Andrew: Desirable actions: (1) Push code to Github, (2) Share slides.
Actions
- Organize a session on Brown's work on editing