No description
Find a file
j2blake ebe1e1430e VIVO-552 Reduce “memory leak” messages at shutdown.
Tomcat also complains if the VALUE of a ThreadLocal is an instance of a class that is defined in the Webapp. So even though the key type was HttpServleetRequest, some of the values were VitroRequest objects. Refactor so the value is the hash code of the request.
2013-11-17 13:35:18 -05:00
doc VIVO-453 language filtering defaults to “false” 2013-11-17 13:20:18 -05:00
opensocial VIVO-448 Change the "example_gadgets" file to use gadgets that are currently active. 2013-11-05 17:35:22 -05:00
solr VIVO-377 Remove "classLocalName" from the search index. 2013-10-17 15:10:36 -04:00
utilities Line-end characters 2013-10-23 09:41:21 -04:00
webapp VIVO-552 Reduce “memory leak” messages at shutdown. 2013-11-17 13:35:18 -05:00
.gitattributes VIVO-4 remove the license substitution code from the license scanner 2013-08-26 14:56:54 -04:00
.gitignore VIVO-2 Modify the build so installers can create a container-neutral VIVO. 2013-01-16 14:54:33 -05:00
README.md Added the README file. 2012-10-29 20:41:47 -04:00

What is Vitro?

Vitro is a general-purpose web-based ontology and instance editor with customizable public browsing.

Vitro is an integrated ontology editor and semantic web application.

Vitro is a Java web application that runs in a Tomcat servlet container.

With Vitro, you can:

  • Create or load ontologies in OWL format
  • Edit instances and relationships
  • Build a public web site to display your data
  • Search your data with Apache Solr

Vitro was originally developed at Cornell University, and is used as the core of the popular research and scholarship portal, VIVO .

For more information, contact the VIVO community.