From d2b3df1674ef367bed34e0d7c2272356b169e3f6 Mon Sep 17 00:00:00 2001 From: ejc12 Date: Thu, 10 Feb 2011 18:37:48 +0000 Subject: [PATCH] Minor editorial changes applied to the docs. --- doc/install.html | 78 +++++++++++++++++++++++++++----------------- doc/upgrade-1.2.html | 6 ++-- 2 files changed, 51 insertions(+), 33 deletions(-) diff --git a/doc/install.html b/doc/install.html index e52d5653..45c579d8 100644 --- a/doc/install.html +++ b/doc/install.html @@ -33,7 +33,7 @@ display and navigation, plus improvements to address scalability. The release also features two new visualization options: temporal graphing for organizations, and personal visualizations extended to cover grants - as well as publications. The VIVO Harvester library has also been + as well as publications. The VIVO Harvester library has also been significantly improved and expanded in scope for its 1.0 release through the VIVO SourceForge project at http://sourceforge.net/projects/vivo.

@@ -77,16 +77,16 @@

Ontology

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.

Associated VIVO releases

VIVO Harvester

The Harvester development team is releasing version 1.0 of the VIVO - Harvester library, an extensible data ingest and updating framework + Harvester library, an extensible data ingest and updating framework with sample configurations for loading PubMed publication, grants, and human resources data. The Harvester is available at http://sourceforge.net/projects/vivo.

@@ -567,13 +567,19 @@ The temporal graph visualization can require extensive machine resources. This can have a particularly noticable impact on memory usage if - The VIVO developers are working to make this visualization more efficient. + The VIVO developers are working to make this visualization more efficient. In the meantime, VIVO release 1.2 guards against this impact by disabling - temporal graph visualization unless the "visualization.temporal" flag is + temporal graph visualization unless the "visualization.temporal" flag is set to "enabled". @@ -782,12 +788,13 @@

XII. Configure Pellet Reasoner

This optional configuration step is only applicable to VIVO installations - running in RDB mode (See section Choose Triple Store for details). - VIVO uses the Pellet engine to perform reasoning, which runs in the - background at startup and also when the knowledge base is edited. VIVO - continues serving pages while the reasoner continues working; when the - reasoner finishes, the new inferences appear. Inferred statements are - cached in a database graph so that they are available immediately when + running in RDB mode (See section Choose Triple Store + for details). + VIVO uses the Pellet engine to perform reasoning, which runs in the + background at startup and also when the knowledge base is edited. VIVO + continues serving pages while the reasoner continues working; when the + reasoner finishes, the new inferences appear. Inferred statements are + cached in a database graph so that they are available immediately when VIVO is restarted.

@@ -863,17 +870,21 @@

  • The name of the HTTP header that will hold the external user's network ID.
    - When a user completes the authentication process, the Apache server - will put the user's network ID into one of the headers of the HTTP - request. The instructions from your institution should tell you which - header is used for this purpose. +

    + When a user completes the authentication process, the Apache server + will put the user's network ID into one of the headers of the HTTP + request. The instructions from your institution should tell you which + header is used for this purpose. +

    You need to tell VIVO the name of that HTTP header. Insert a - line like this in the deploy.properties file: + line like this in the deploy.properties file: 

    externalAuth.netIdHeaderName = [the header name]
    -

    For example:

    - 
    externalAuth.netIdHeaderName = remote_userID
    +

    + For example: +

    + 
    externalAuth.netIdHeaderName = remote_userID
  • The text for the Login button.
    @@ -885,13 +896,17 @@ externalAuth.buttonText = [the text for your login button] For example: 

    externalAuth.buttonText = Log in using BearCat Shibboleth
    - The VIVO login form will display a button labelled "Log in using - BearCat Shibboleth". +

    + The VIVO login form will display a button labelled "Log in using + BearCat Shibboleth". +

  • -
    Associating a User with a profile page
    - If VIVO has an account for the user, the user will be given the - privileges assigned to that account. +
    Associating a User with a profile page.
    +

    + If VIVO has an account for the user, the user will be given the + privileges assigned to that account. +

    In addition, VIVO will try to associate the user with a profile page, so the user may edit his own profile data. VIVO will search the @@ -900,7 +915,10 @@ Insert a line like this in the deploy.properties file: 

    selfEditing.idMatchingProperty = [the URI of the property]
    - For example:
    selfEditing.idMatchingProperty = http://vivo.mydomain.edu/ns#networkId
    +

    + For example: +

    + 
    selfEditing.idMatchingProperty = http://vivo.mydomain.edu/ns#networkId

    • XIV. Was the installation successful?

    @@ -958,7 +976,7 @@ Enter the name "test individual" under the field "Individual Name," scroll to the bottom, and click "Create New Record." You will be taken to the "Individual Control Panel." Make note of the value of the - field "URI" it will be used in the next step. + field "URI" - it will be used in the next step.
  • Open a new web browser or browser tab to the page http://marbles.sourceforge.net/. diff --git a/doc/upgrade-1.2.html b/doc/upgrade-1.2.html index 6b16ce40..d7a27167 100644 --- a/doc/upgrade-1.2.html +++ b/doc/upgrade-1.2.html @@ -117,7 +117,7 @@ The Upgrade Process
  • - Ontology Upgrade + Ontology Changes
    1. Verify Ontology upgrade @@ -143,7 +143,7 @@
  • - Theme Modifications + Theme Changes
  • Set Up SDB Store in the Background (Optional) @@ -621,7 +621,7 @@ 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 + VIVO implementation sites and a copy of your institution's tracking code, see the VIVO Google Analytics wiki page.