VIVO Documentation
...
This document presents the process required to develop a new language to be integrated into VIVO and Vitro. It is intended for any developer who wishes to develop a new integrated language. The development process requires a good knowledge of the VIVO internal structure and its internal working mechanisms. This document describes the development cycle of new languages as well as the components required for this development.
The project of adding a new language requires diverse and varied skills. Therefore, it requires the involvement of a multidisciplinary team composed of software developers, linguists and ontologists. It is therefore necessary to allow a few days or even a few weeks, depending on the computer skills of the team, to complete all the iterations presented in this guide. La maîtrise du cycle de développement présenté ci-dessous ainsi que des actions informatiques associées à chacun des étapes du cycle doivent être maîtrisé par l'ensemble des membres de l'équipe. Il sera donc nécessaire d'offrir un support informatique adéquat au personnel non informaticiens travaillant sur la traduction des textes contenus dans les divers fichiers. Pour simplifier ce travail nous recommandons fortement l'usage de UQAM-DEV R.3 : An Interoperable UQAM Development Environment for VIVO (UQAM-DEV)
...
Step | Action | |||||
---|---|---|---|---|---|---|
1) Start TOMCATAfter making the appropriate configurations move to the TOMCAT executables directory and launch the application. |
| |||||
2) Monitoring the executionafter running the "taill -f" command you can do ^C to stop the Monitoring |
| |||||
3) Observing the execution After logging in to VIVO and passing the smocktest you should see a presentation similar to this one. If you don't observe people in the faculties make sure that the example files are copied to the right place as indicated above or that Solr has been started . |
...