Page History

...

depending on the particular model.

Where are the RDF files?

In the distribution, the RDF files appear in [vivo]/rdf and in [vitro]/webapp/rdf. These directories are merged during the build process in the usual way, with files in VIVO preferred over files in Vitro.

During the build process, the RDF files are copied to the VIVO home directory, and at runtime VIVO will read them from there.

The "first time"

For purposes of initialization, VIVO is considered to be starting for the "first time" RDF files are loaded if the Application metadata relevant data model contains no statements, or . Content models may also load "first time" files if the RDFService detects that its SDB-based datastore has not been initialized.

...

Source: the application Datasource (MySQL database) (memory-mapped)

If this is the first startup, read the files in /WEB-INF/init-data (without subdirectories)

• In Vitro, there are none
• In VIVO, initialSiteConfig.rdf

)

If Also if this is the first startup, read the files in in rdf/WEB-INF/ontologies/user/applicationMetadataapplicationMetadata/firsttime.

• In Vitro, there are none
• In VIVO, initialSiteConfig.rdf, classgroups.rdf and propertygroups.rdf

User Accounts

Contains login credentials and assigned roles for VIVO users.

...

If this model is empty, read the files in rdf/WEB-INF/ontologies/auth (without subdirectories). Ordinarily there are no such files. This feature is useful when running acceptance tests.auth/firsttime.

The Display model

This is the ABox for the display model, and contains the RDF statements that define managed pages, custom short views, and other items.

...

If this model is empty, read the files in /WEB-INF/ontologies/app/ (without subdirectories)in rdf/display/firsttime

• In Vitro, application.owl, menu.n3, profilePageType.n3
• VIVO contains its own copy of menu.n3, which overrides the one in Vitro
  

Every time, read the files in rdf/WEB-INF/ontologies/app/loadedAtStartupdisplay/everytime

• in Vitro, displayModelListViews.rdf
• In VIVO, homePageDataGetters.n3, localeSelectionGUI.n3, vivoDepartmentQueries.n3, vivoListViewConfig.rdf, vivoSearchProhibited.n3

...

Source: the application Datasource (MySQL database) (memory-mapped)

Every time, read /WEB-INF/ontologies/app/menuload/displayTBOX.n3 (note that existing statements are not cleared, except through the GUI)the files in rdf/displayTbox/everytime.

• In Vitro, displayTBOX.n3
• In VIVO, there are none
  

DisplayDisplay

Name: http://vitro.mannlib.cornell.edu/default/vitro-kb-displayMetadata-displayModel

Source: the application Datasource (MySQL database) (memory-mapped)

Every time, read /WEB-INF/ontologies/app/menuload/displayDisplay.n3 (note that existing statements are not cleared, except through the GUI)the files in rdf/displayDisplay/everytime

• In Vitro, displayDisplay.n3
• In VIVO, there are none.
  

Initializing Content models

...

If first setup, read the files in rdf/WEB-INF/ontologies/user/abox (without subdirectories)abox/firsttime

• In Vitro, there are none
• In VIVO, geopolitical.ver1.1-11-18-11.individual-labels.rdf, vocabularySource-labels.n3

Every time, read the files in rdf/WEB-INFabox/filegraph/abox, and create named models in the RDFService. Add them as sub-models to the base ABox. If these files are changed or deleted, update the RDFService accordingly.

...

If first setup, read the files in rdf/WEB-INF/ontologies/user/tbox tbox/firsttime (without subdirectories)

• In Vitro, there are none
• In VIVO, geopolitical-ver1.1-11-18-11-annotations.rdf, isDefinedBy-1.5-annotations.rdf, scires-1.5-annotations.rdf, vitro-0.7-annotations.rdf, vivo-core-1.5-annotations.rdf, vivo-core-1.5-labels_es_ES.n3

Every time, read the files in rdf/WEB-INFtbox/filegraph/tbox, and create named models in the RDFService. Add them as sub-models to the base TBox. If these files are changed or deleted, update the RDFService accordingly.

...