VIVO Documentation
Page History
...
It is tempting to think of the models of the Servlet Context as equivalent to the unfiltered models of the Request. And in fact, they may represent the very same data. However, the unfiltered models in the Request go out of scope when the Request has been satisfied. As such, it is much easier to manage the resources required by these models. By contrast, the models of the Servlet Context never go out of scope until VIVO is shut down. Any resources such as database connections or processor memory are not easily reclaimed from these models.
The ModelAccess class
| Note |
|---|
Show how it represents all of these distinctions. Describe the scope searching and masking, wrt set and get. |
Initializing the Models
When VIVO starts up, OntModel objects are created to represent the various data models. The configuration models are created from the datasource connection, usually to a MySQL database. The content models are created using the new RDFService layer. By default this also uses the datasource connection, but it can be configured to use any SPARQL endpoint for its data.
...
Source: a combination of union ABox and union TBox
The ModelAccess class
...
Transition from previous methods
...
Overview
Content Tools