Page History

...

This pulls in the “VIVO-ISF ontology” files that are needed to build the eagle-i ontology files. An SVN update done from the root of the eagle-i trunk checkout should pull in any ISF changes unless the external is pinned to a specific ISF commit. Currently the external is following the latest ISF commits.

src/isf/tools 

 This is an SVN external that follows the “eagle-i” Git branch from the following location: https://github.com/vivo-isf/tools/tree/eaglei/tools/owlcl

...

Static application ontology files 

 These files are located under the the src/eagle-i/application directory  directory when an SVN checkout is done. They have “app” in their name, are committed to SVN, and they have OWL imports that import the “non-app” ontology files that are generated in the the src/eagle-i/public folder  folder when the generation scripts or build tools are used.

These files are application files, meaning that their content is specific to the eagle-i application, and they should not contain any reusable “ontology” content. Any “ontology” content will be coming from the generated files.

...

These files, are generated with the tools based on the definition/configuration in each of their modules. They can be generated as needed with the provided tools. 

 The eagle-i SVN trunk tracks the ISF trunk in GitHub. Whenever an SVN update is done in the eagle-i trunk folder, the update may bring in new changes from the ISF external even if there are no eagle-i SVN changes. When there are new ISF changes and one of the module configurations is affected by this change (for example, a new technique term is added in ISF and a module configuration uses the technique hierarchy), either all of the module files or just the affected ones have to be regenerated by using the module scripts to see the changes in the generated ontology files. 

 The Bamboo build server is setup to track all three sources that affect the generated OWL files. It watches for changes in the eagle-i SVN, ISF GitHub repository, and the tools GitHub repository, and rebuilds the modules whenever there is a change. The Bamboo built modules -- along with the static files -- are packaged and uploaded to Nexus as a JAR file. The JAR file contains additional content beyond the generated OWL files.

...