+
This document provides a short description of the steps involved in upgrading your installation of VIVO from Release 1, Version 1.1 to Version 1.2. This and other documentation can be found on the support page @@ -67,8 +68,8 @@
While server memory capacity has increased significantly in recent
- years, VIVO's reliance on in-memory caching of RDF data had put limits
- on the ultimate scalability of VIVO instances and potentially increased
+ years, VIVO's reliance on in-memory caching of RDF data had put limits
+ on the ultimate scalability of VIVO instances and potentially increased
the cost of servers required to support VIVO.
VIVO 1.2 includes a new ontology module representing research - resources including biological specimens, human studies, instruments, - organisms, protocols, reagents, and research opportunities. This module - is aligned with the top-level ontology classes and properties from the + resources including biological specimens, human studies, instruments, + organisms, protocols, reagents, and research opportunities. This module + is aligned with the top-level ontology classes and properties from the NIH-funded eagle-i Project.
[new_source_directory]/themes/[theme_dir]/templates/googleAnalytics.ftlA sample
googleAnalytics.ftl
is included in the built-in
- theme. This file serves only as an example, and you must replace the
- tracking code shown with your institution's own tracking code. For
- additional information about the GATC for the NIH-funded VIVO
- implementation sites and a copy your institution's tracking code, see
+ theme. This file serves only as an example, and you must replace the
+ tracking code shown with your institution's own tracking code. For
+ additional information about the GATC for the NIH-funded VIVO
+ implementation sites and a copy your institution's tracking code, see
the VIVO
Google
Analytics
@@ -587,9 +592,9 @@
- Each uploaded file exists as an individual entity in VIVO. When the - browser requests an upload file from VIVO, the data model is queried to + Each uploaded file exists as an individual entity in VIVO. When the + browser requests an upload file from VIVO, the data model is queried to find out where the file is actually stored, so it can be downloaded to the browser.
In VIVO release 1.2 this storage location, - known as the "Alias URL" for the uploaded file, + known as the "Alias URL" for the uploaded file, is stored in the file entity. That way, pages that contain many files can be displayed much more quickly.
@@ -828,7 +833,7 @@