Versions Compared

Key

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

Table of Contents

Site Administration

Once you are logged into VIVO, you will notice in the upper right hand portion of the page links to "Index" and "Site Admin", alongside a drop-down menu with your name on it, and containing links to "My account" and "Log out".

...

FIGURE 3 - VIVO Site Administration screen

Data Input

There are two ways to manually input data into VIVO. On the Site Administration Menu, a new individual of any type may be added directly through the Data Input menu. Once an individual has been created object and data properties may be added for that individual on the page displaying the individual’s profile. The object and data properties presented for editing will vary by the type of the individual, in accordance with the ontology.

Ontology Editor

In VIVO, information is identified by references to Unique Resource Identifiers (URIs). URIs can be used by other web pages and applications to locate and retrieve specific chunks of data. The detailed level to which VIVO captures information enables complex relationships among data to be represented.

...

Ontology List - VIVO supports keeping an internal list of ontology namespaces and corresponding prefixes to facilitate using external ontologies as well as to help differentiate local ontology additions from VIVO core.

Class Management

Individuals in VIVO are typed as members of one or more classes organized and displayed as a hierarchy.

...

Class groups - Class groups are a VIVO-specific extension to support using VIVO as a public website as well as an ontology and content editor. Class groups are a means to organize the classes in VIVO into groups. They represent the facets seen when VIVO is searched (people, activities, events, organizations, etc).

Property Management

If classes define what each individual in VIVO is, properties define how that individual relates to other individuals and allow an individual to have attributes of its own. VIVO has two property editors, one for object properties and another for data properties.

...

Property groups - Like class groups, property groups are a VIVO-specific extension to support using VIVO as a public website as well as an ontology and content editor.

Site Configuration

...

The site configuration aspects of VIVO enables administrators to add or adjust to their institution’s site specific details, as well as to manage menus, tabs, and user accounts. Please refer to the Site Configuration section below for detailed instructions.

Advanced Tools

The Advanced tools are VIVO’s built-in features for data management and export. Please refer to the Advanced Tools section below for detailed instructions.

In addition, many VIVO adopters may require additional information regarding the importing and exporting of RDF data and creating SPARQL queries.

There are several avenues available to acquire guidance with these advanced tools. Information sources such as the VIVO Data Ingest Guide, the W3C’s Resource Description Framework model, and the W3C’s SPARQL Query Language for RDF, to name a few. Please refer to Appendix A for links and additional resources.

Refreshing Content

V1.3 Specific: Site Administrators can rebuild their search, class group cache, visualizations, and inferencing in the Site Admin interface. It is important to build the visualization code after ingesting publication data or it will take a long time to display the visualization to the user.

Image Removed

...

...

This

...

Site Configuration

This section discusses the site configuration aspects of VIVO. It enables administrators to add or adjust to their institution’s site specific details, as well as to manage menus, tabs, and user accounts.

Site Information

...

– The Site information link provides administrators with the capabilities of editing and adding site specific details for that institution’s instance of VIVO.

...

Copyright URL — The URL you want the copyright to go to in the footer. It could be your institution’s copyright information or the actual institution.

Advanced Tools

The Advanced tools are VIVO’s built-in features for data management and export. Please refer to the Advanced Tools section below for detailed instructions.

In addition, many Many VIVO adopters may require additional information regarding the management importing and exporting of RDF data and use of SPARQL (SPARQL Protocol and RDF Query Language)creating SPARQL queries.

There are several avenues available to acquire guidance with these advanced tools. Information sources such as the VIVO Data Ingest Guide, the W3C’s Resource Description Framework model, and the W3C’s SPARQL Query Language for RDF, to name a few. Please refer to Appendix A for links and additional resources.

Advanced Data Tool Short Description

Ingest tools – A suite of data management tools. See below for a detail of each tool.

...

SPARQL query builder – A query generating interface with pre-populated drop down lists.

Ingest Menu Short Description

Connect DB – (warning) Removed in v1.7+. This tool allows for the VIVO application to interact with a variety of Jena RDB or SDB databases through a JDBC connection. Database connection types include: MySQL, D2B, H2, JavaDB, Oracle, and more. 

...

Change Namespace of Resources — This tool will change all resources in the supplied “old namespace” to be in the “new namespace.” Additionally, the local names will be updated to follow the established “n” + random integer naming convention.

Refreshing Content

V1.3 Specific: Site Administrators can rebuild their search, class group cache, visualizations, and inferencing in the Site Admin interface. It is important to build the visualization code after ingesting publication data or it will take a long time to display the visualization to the user.

Image Added

Rebuild visualization cache

Panel

Why
Large-scale visualizations like the Temporal Graph or the Map of Science involve calculating total counts of publications or of grants for some entity. Since this means checking also through all of its sub-entities, the underlying queries can be both memory-intensive and time-consuming. For a faster user experience, we wish to save the results of these queries for later re-use.
What
To this end we have devised a caching solution which will retain information about the hierarchy of organizations-namely, which publications are attributed to which organizations-by storing the RDF model. We're currently caching these models in memory. The cache is built (only once) on the first user request after a server restart. Because of this, the same model will be served until the next restart. This means that the data in these models may become stale depending upon when it was last created. To avoid restarting the server in order to refresh the cache, administrators can use the Rebuild visualization cache link.
This works well enough for now. In future releases we will improve this solution so that models are stored on disk and periodically updated.