Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.



Hi there,

You are invited to a scheduled Zoom meeting.

Topic:  VIVO i18n task force Meeting
Time: Aug 14, 2018 10:00 AM EST (US and Canada)
    Every 2 weeks on Tue, until Nov 05, 2019, 33 occurrence(s)
    Sep 11, 2018 10:00 AM
    Please download and import the following iCalendar (.ics) files to your calendar system.

Join from PC, Mac, Linux, iOS or Android:

Or iPhone one-tap :
    Canada: +16475580588,,673342989#
Or Telephone:
    Dial(for higher quality, dial a number based on your current location):
        Canada: +1 647 558 0588
    Meeting ID: 673 342 989
    International numbers available:

Or an H.323/SIP room system:
    H.323: (US West) (US East) (China) (India) (EMEA) (Australia) (Hong Kong) (Brazil) (Canada)
    Meeting ID: 673 342 989


Meeting notes document :


  1. Kitio Fofack Kitio Fofack

  2. Andrew Woods Andrew Woods

  3. Manuel Schwarz

  4. Ralph O'Flinn 

  5. Leticia Palos


  1. Identifying non-translated text in Vitro/VIVO

  2. A demo installation with up-to-date German files was provides: results can be found at
  3. If you would like to have an account, please ask someone from the TIB VIVO team (Tatiana, Graham, Asim, Christian ...)

  4. Tasks are being created in JIRA (


  5. Scope of i18n during next Ongoing Sprint

    1. Home page :

    2. Capability Map:

    3. Header section of Profile:

  6. Community engagement on i18n related developments

  7. i18n issues (


Non-translated text in Vitro/VIVO

  1. Suggestion: Have a top-level page or ticket for the more granular tasks

    1. This is being done by associated tasks with “JIRA Epics”

  2. Transitioning the issues documented in Google-Doc into JIRA tickets

Scope of i18n during next Sprint


  1. Complete Capability Map i18n


  2. Home page i18n


  3. Header section of Profile



  1. Need to document the approach (“recipe”) for working through each section of the application

    1. Once an item needing i18n in the UI is identified, recipe is approach for updating the various files

Outreach for Sprint engagement

  1. ACTION: Kitio Fofack to send out message to the list

i18n Requirements


  2. Fallback

  3. Are users interested in potentially disabling fallback?

  4. ...therefore, showing nothing if a translation is not available