Versions Compared

Key

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

...

StepAction

1) Creating the GIT directory

Whether under Windows or on Unix it is necessary to create a space in which it is possible to work. As proposals we suggest creating a directory called under the Tomcat root directory. In the case of users and Unix we suggest to carry out the operations under the tomcat username. This precaution facilitates the management of credentials associated with development under Linux.


Code Block
languagebash
sudo -i -u tomcat # sudo in Linux - not on Windows
mkdir $TOMCAT_HOME/GIT # $TOMCAT_HOME is predefined at the installation of Tomcat
cd $TOMCAT_HOME/GIT


2) Retrieving VIVO the code

To VIVO internationalization, it is necessary to extract the four following GitHub repo:




Code Block
languagebash
git clone https://github.com/vivo-project/Vitro.git Vitro -b branch_name_to_be_coming
git clone https://github.com/vivo-project/VIVO.git VIVO -b branch_name_to_be_coming
git clone https://github.com/vivo-project/VIVO-languages VIVO-languages -b branch_name_to_be_coming
git clone https://github.com/vivo-project/Vitro-languages Vitro-languages -b branch_name_to_be_coming


3) Retrieving UQAM

Vivo

VIVO-

installer-i18n

installe

The installer makes it easy to manage the compilation and deployment of the VIVO i18n instance.


Code Block
languagebash
git clone https://github.com/UQAM-SB/Vivo-installer-i18n


Item C) Configuring the VIVO search accelerator (SOLR)

...

The addition of ontologies for managing menus and menus brings profound changes to the core content of VIVO data. For the success of this iteration, it is necessary to reinitialize the content of the VIVO triplestore. To do this it is necessary to delete the directories rdf, tdbContentModels, tdbModels contained in vivo/home:

StepAction
Stoping tomcat


Code Block
${CATALINA_HOME}/bin/cmd.sh stop


Removing directories


Code Block
cd $VIVO_HOME
rm -r rdf
rm -r tdbContentModels
rm -r tdbModels


Step 1) Compile and deploye a new/corrected instance of VIVO and start it

StepAction
Compiling VIVO


Code Block
languagebash
titleCommand
cd $GIT_HOME/Vivo-installer-i18n
mvn -s settings_i18n_linux.xml -DskipTests=true clean install 


Populating VIVO with Sample-Data and restart Tomcat


Code Block
cp $GIT_HOME/sample-data/i18n/sample-data* $VIVO_HOME/rdf/abox/filegraph/
${CATALINA_HOME}/bin/cmd.sh start


Step 2) Running VIVO for testing and/or finding an i18n problem

...