Our subversion repository can be browsed here:
The two relevant directories are:
- apps: the code for the different software components and the artifacts to compile them.
- datamodel: the ontology files (owl) and artifacts for packaging them into a jar. Note that the pure ontology portion is mirrored at http://code.google.com/p/eagle-i/
- trunk - contains the active development of the different software components.
- branches - contains the releases of the software.
Miscellaneous Java services and utilities used by search and data tools applications. Includes: Solr index, auto-suggest, authentication and connection, logging, Jira connector for feedback,... |
Front-end GWT code shared by search and data tools applications (SWEET and data management);
Shared back-end code for read/write operations on an eagle-i repository;
Resources for developers, such as eclipse configuration files.
Documentation, including online user help (note: does not yet contain admin and developers guides found in this website).
Sample code and configuration files.
Abstraction for interacting with an eagle-i annotated ontology, optimized for access from client code (API and Jena-based implementation).
Experiments with LingPipe for extracting eagle-i top-level resources from PubMed abstracts.
Code that is no longer active in the main codebase but is helpful as reference.
Repository code and administrative tools. This directory is pretty much self-contained (except for its dependency on common/ui/static-resources).
Search application back-end.
User-facing web applications and web services except for repository. The modules in this directory produce .war files.
- trunk - contains the active development of the ontology.
- releases - contains the releases of the ontology.
The owl files that conform the eagle-i resource ontology, including imports. This directory also contains the main application ontology (eagle-i-app.owl)
The maven files to build the ontology jar and miscellaneous application-level administrative ontologies.