Deprecated. This material represents early efforts and may be of interest to historians. It doe not describe current VIVO efforts.
Page History
...
| Note |
|---|
Windows: For those installing on a Windows operating system, include the windows drive, but use the forward slash "/" and not the back slash "\" in the directory locations, e.g. |
| Property name | Default value | Example value |
|---|---|---|
| NONE | |
The directory where Vitro code is located. In most deployments, this is set to ./vitro-core (It is not uncommon for this setting to point elsewhere in development environments). | ||
| Property name | Default value | Example value |
|---|---|---|
| NONE | |
| The directory where tomcat is installed. | ||
| Property name | Default value | Example value |
|---|---|---|
| NONE | |
| The name of your VIVO application. This is not a name that will be displayed to the user. This name appears in the URL used to access VIVO, and in the path to the VIVO directory within Tomcat. | ||
| Property name | Default value | Example value |
|---|---|---|
| NONE | |
| The directory where VIVO will store the data that it creates. This includes uploaded files (usually images) and the Solr search index. Be sure this directory exists and is writable by the Tomcat service. | ||
| Property name |
|
|---|---|
| Description | The directory where Vitro code is located. In most deployments, this is set to ./vitro-core (It is not uncommon for this setting to point elsewhere in development environments). |
| Default value | NONE |
| Example value | ./vitro-core |
...
These properties define some fundamental aspects of your VIVO installation. Most sites will need to modify each of these values.
| Property nameProperty name | Default valueDefault valueExample value | Example value |
|---|---|---|
Vitro.defaultNamespace | NONE | http://vivo.mydomain.edu/individual/ |
The default RDF namespace for this installation. VIVO installations make their RDF resources available for harvest using linked data. Requests for RDF resource URIs redirect to HTML or RDF representations as specified by the client. To make this possible, VIVO's default namespace must have a certain structure and begin with the public web address of the VIVO installation. For example, if the web address of a VIVO installation is "http://vivo.example.edu/" the default namespace must be set to "http://vivo.example.edu/individual/" in order to support linked data. Similarly, if VIVO is installed at "http://www.example.edu/vivo" the default namespace must be set to "http://www.example.edu/vivo/individual/" * The namespace must end with "individual/" (including the trailing slash). | ||
...
Overview
Content Tools