VIVO Documentation
Page History
...
In release 1.5, VIVO added the RDFService interface, which has increased the flexibility of data sources, and promises to allow a more unified view of the knowledge base. However, the transition to RDFService is not complete, and so this adds another layer of complexity to the data issues.
Beyond the models
| Note |
|---|
TBD - Give a little capsule of what each of these structures is, and how it is used. |
The RDF Service
The DAO Layer
...
Model makers and Model sources
The ModelAccess class
...
| Note |
|---|
TBD - Show how it represents all of these distinctions. Describe the scope searching and masking, wrt set and get. Include the OntModelSelectors and WADFs. |
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
Transition from previous methods
| Note |
|---|
TBD - What are we transitioning from? Check out VIVO-82. |
...
Overview
Content Tools