vivo #11

Supports: precise

Add to new model

Description

VIVO enables the discovery of researchers across institutions.
Participants in the network include institutions with local installations
of VIVO or those with research discovery and profiling applications that
can provide semantic web-compliant data.


This charm is intended to provide an easy deployment of the VIVO web application

The basic steps to deploying a VIVO with the default options are:

1) Deploy a mysql server. VIVO uses JENA ontop of mysql to provide
the RDF database for the website. juju deploy mysql

2) Deploy vivo
juju deploy vivo

3) Link mysql to vivo
juju add-relation mysql vivo

4) Expose your new vivo website
juju expose vivo

5) Browse and use the site by going to the public address of your vivo
application server http://INSTANCEIP:8080/vivo

Issue the 'juju status' command, and look for the public address listed 
IE, the following is accessible on ec2-184-73-116-125.compute-1.amazonaws.com:8080/vivo
vivo/0:
    agent-state: started
    machine: 1
    public-address: ec2-184-73-116-125.compute-1.amazonaws.com

Additionally, the relevant build options for VIVO are exposed. You will want
to set at least a few of them, see the config.yaml file for all options.

juju set Vitro.defaultNamespace = "YOURNAMESPACE"
juju set email.replyTo = "YOUREMAIL"
juju set email.smtpHost = "YOURHOST"
juju set rootUser.emailAddress = "YOUREMAILADDRESS"
juju set selfEditing.idMatchingProperty = "YOURIDPROPERTY"

You can set the build options at any time using the 'juju set option=value'
command. However, it's important to note that setting options after the website
is deployed, causes the website to rebuild and redeploy. This is because all of
the options exposed are changed during compilation. Until recompiled and
redeployed the site will be down. Additionally, only one mysql instance relation
should be added at a time. If scaling is needed, an additional unit can be
added to the mysql charm using the juju add-unit mysql command.

About VIVO:
VIVO enables the discovery of researchers across institutions.
Participants in the network include institutions with local installations
of VIVO or those with research discovery and profiling applications that can
provide semantic web-compliant data. The information accessible through VIVO's
search and browse capability will reside and be controlled locally,
within institutional VIVOs or other semantic web-compliant applications.


Configuration

Vitro.defaultNamespace
(string) Default namespace, VIVO installations make their RDF resources available for harvest using linked data.
http://vivo.mydomain.edu/individual/
email.replyTo
(string) Specify an email address which will appear as the sender in e-mail notifications to users
vivoAdmin@mydomain.edu
email.smtpHost
(string) Specify an SMTP host that the application will use for sending e-mail
smtp.mydomain.edu
externalAuth.buttonText
(string) If an external authentication system like Shibboleth or CUWebAuth is to be used, this property specifies how the login button should be labeled. Leave blank if not using.
externalAuth.netIdHeaderName
(string) If an external authentication system like Shibboleth or CUWebAuth is to be used, this specifies which HTTP header will contain the user ID from the authentication system. Leave blank if not using.
rootUser.emailAddress
(string) Specify the email address of the root user account for the VIVO application. This user will have an initial temporary password of 'rootPassword'. You will be prompted to create a new password on first login.
vitro@localhost
selfEditing.idMatchingProperty
(string) The URI of a property that can be used to associate an Individual with a user account
http://vivo.mydomain.edu/ns#networkId
visualization.temporal
(string) The temporal graph visualization is used to compare different organizations/people within an organization on parameters like number of publications or grants.
enabled