Date

31 Jul 2018

Call-in Information

Time: 10:00 am, Eastern Time (New York, GMT-04:00)

To join the online meeting:

Join from PC, Mac, Linux, iOS or Android: https://uqam.zoom.us/j/981823821

Or iPhone one-tap :
    Canada: +16475580588,,981823821#
Or Telephone:
    Dial(for higher quality, dial a number based on your current location):
        Canada: +1 647 558 0588
    Meeting ID: 981 823 821
    International numbers available: https://zoom.us/u/eAvn48bdc

Or an H.323/SIP room system:
    H.323:
        162.255.37.11 (US West)
        162.255.36.11 (US East)
        221.122.88.195 (China)
        115.114.131.7 (India)
        213.19.144.110 (EMEA)
        202.177.207.158 (Australia)
        209.9.211.110 (Hong Kong)
        64.211.144.160 (Brazil)
        69.174.57.160 (Canada)
    Meeting ID: 981 823 821

    SIP: 981823821@zoomcrc.com

Slack

• https://vivo-project.slack.com
  • Self-register at:  https://goo.gl/forms/JxQFkut4TYj4Ehww1 
    

Attendees

 Indicating note-taker

1. Kitio Fofack

2. Andrew Woods

3. Graham Triggs

4. Ralph O’Flinn

Agenda and Notes

1. Consensual Items

                  A.Complete multilingual interface (making English a language as others)

1. Graham agrees and argues that we need to address the string in the rdf. There may be issues in loading

2. We need a proof of concept taking all known issues related to the item to implement (taking out english)

3. Ralph : maybe it is better to just start the work and see as the work moves forward the issues and solve them

4. Areas of focus

1. language-tagged content

2. strings in freemarker and jsp templates

3. strings in the code, itself

4. strings in the ontology, labels etc

                  B.Documentation on the release policy of language related artifacts

1. Andrew: By default any VIVO release is dependant on languages project. So the languages supported on the listed

2. Ralph : Keeping the process simple to start. Release the language as we release VIVO

3. Graham : What happen when someone completes it’s translation  before or after a VIVO release ?

4. Kitio: We can have a simple release process that triggers community feedback to improve the translation by bootstrapping

5. Ralph : We can have a wording according to the level of support of a language

6. Ralph and Andrew: Separate the concern : extract the strings Then think how we simplify language support

                   C.Documentation on how to conduct language related work (adding a new language, updating a translation, ...)

                   D.Better usability for switching languages in standard themes (no flags)

1. Ralph: Use ISO flags for the languages

2. Kitio: This is maybe too political issue

3. Andrew: there has to be a very simple and efficient for a visitor to set the interface in his/her native language

2.What to implement for next VIVO release ?

1. Ralph and Kitio: Let’s target getting English out of the application for next release

3.i18n issues

1. UX design for multilingual content edition

2. Steps in implementing fallback mechanism