Skip to end of metadata
Go to start of metadata


The primary objective of the i18n sprints are to bring the language-aware editing capabilities into the core VIVO application.

This objective will include the following goals:

  1. Creation of Integration and Regression tests to ensure the existing functionality does not break during the course of the i18n editing development activities (and beyond)
  2. Transfer of UQAM software updates into one or more GitHub repositories
  3. Review, testing and integration of the initial UQAM software updates into core VIVO
    1. Given the size of these initial software updates, we will need to slice the updates into smaller units of functionality and pull-requests
  4. Establishment of a pattern for making additional languages available to all VIVO installations
  5. Review and test incremental i18n editing updates
  6. Update documentation of installation and configuration guides


Four Three sprints are planned:

  • April 6 - 17
  • May 19 - 25 (Tuesday through following Monday)
  • June 22 - July 3 (sprints 3 and 4 combined)

Who (and roles)

Roles: developer, documenter, tester, translator, other?

  1. Michel Héon(UQAM) Developer
  2. Joachim Dornbusch  (EHESS)
  3. Christian Hauschke (TIB; check German version pages, documentation)
  4. Benjamin Gross (limited availability, testing and code review)
  5. Ralph O'Flinn  (limited availability, testing and code review)
  6. Alexander (Sacha) Jerabek(UQAM - review documentation, check French version pages, test installation of Vivo)
  7. Matthias Lühr(HS Mittweida; testing, documentation)
  8. Andrew Woods Developer / Tester
  9. Nicolas Dickner(UQAM - review documentation, check French version pages, test installation of Vivo)
  10. Rachid Belkouch (UQAM - review documentation, check French version pages, help coordinate if necessary)

Sprint Summary

The (current) i18n sprint officially ended on Friday, April 17th.

The team consisted of ten participants from 6 different organizations.

The top-level objective of the effort is to establish a clearly documented capability within VIVO to add new and enable existing languages such that both the static text as well as the site-specific data is exposed in a language-aware context. Additionally, the effort is focused on adding the ability to create language-aware content in the native VIVO user interface.

In addition to establishing a cohesive and productive team, the primary outcomes of the sprint include:

  1. Initial (pre-beta) implementation of i18n edit capabilities, found on the "sprint-i18n" branches of the VIVO, Vitro, VIVO-languages and Vitro-languages projects
  2. Comprehensive testing of the i18n implementation across (almost) all UI pages, and associated JIRA ticket creation
    1. 63 JIRA bug tickets created (14 resolved)
    2. 6 JIRA improvement tickets created (4 resolved)
    3. 4 JIRA test tickets created
    4. 4 JIRA documentation tickets created
  3. Selenium testing framework created with a focus on i18n
  4. Git / GitHub process documentation created to help onboard team members to the VIVO development processes

Remaining tasks include:

  1. Finish testing of remaining few UI pages
  2. Resolving and verifying fixes of identified bugs
  3. Documentation of how to use the updated functionality, how to enable languages, and how to add a new language
  4. Expanding Selenium tests
  5. Code refactoring

In order to complete the outstanding tasks, we will be holding one-week-long sprints during the months of May, June and July. Mark you calendars! These sprints will be happening on the third full week of the month:

  1. May 18-22
  2. June 15-19
  3. July 20-24


1) Project wiki

VIVO-i18n - Canadian French Initiative

2) UQAM's GitHub - although development will happen on the 'sprint-i18n' branches of VIVO/Vitro/VIVO-languages/Vitro-languages
3) Test data

  • Would be good to have a German version of this as well

4) i18n Reference Demo

Demo VIVO server consisting of UQAM's implementation of the i18n editor design

  1. User:
  2. Pass: VivoI18nRoot.

5) Vivo Translation Ecosystem

Ecosystem useful for the development of VIVO

  • Java and ftl code editing
  • Editing ontologies
  • Local execution of VIVO
  • Access to source code in GIT

6) VTE First run wiki

Documentation in under construction

Sprint goals

  1. Updates will go into the core

  2. Sprint will demonstrate editing with French, German and English

  3. Regression testing with Selenium

  4. Updated documentation

Sprint prerequisites

  1. (tick) Code in GitHub
  2. (tick) GitHub diff/pr
  3. Remove whitespace from VIVO and Vitro working branches
  4. (error) How can the code be subdivided? - no, the plan is to refine the sprint branches, then submit uber-PR
  5. (tick) Test data
  6. (tick) Set up a reporting and monitoring tool for identified problems (potentially Jira) able to manage screenshots - JIRA scrum board

Future goals

  1. English to be extracted, like any other language
  2. All VIVO languages will be consolidated into central language repositories
  3. Move translation files to ontology files

Working GitHub branches

  1. VIVO : (until we have whitespace removed)
  2. Vitro : (until we have whitespace removed) 
  3. VIVO-languages :
  4. Vitro-languages :

  • No labels