...

The eagle-i platform comprises software components deployed at a participating institution (an _eagle-i node) _and a central search application. Figure 1 provides a high-level overview of the eagle-i software components at one institutional deploymentof a node:

Figure 1. Overview of the eagle-i software stack

...

The SWEET (for Semantic Web Entry and Editing Tool) is a web application for manual data entry and curation developed using the GWT (Google Web Toolkit). Its core component is a dynamic forms generation module that translates ontology constructs axioms into UI data entry widgets. The SWEET generates a form per ontology class and thusly allows users to create instances of an ontology class. Navigational elements of the SWEET include workflow controls and instance listing and filtering.

...

A data management toolkit provides command line tools for performing bulk modifications on instances in a repository, and in particular for migrating existing instance data to conform to a newly released ontology. The data migration scripts are currently part of the nexus repository; we are currently putting together documentation about how to use these scripts effectively. A data management front-end to be used by data curators is under active development.

...

In March 2012, the eagle-i ontology was officially released. For more in-depth information about it, see the google code project site.

...

The eagle-i network

In an operational systemthe eagle-i network, institutional servers are independent of each other. A central search application provides a unified view across the institutional servers.

...

We are currently using an alternate deployment whereby the search application builds central indices by harvesting data from the institutional repositoryrepositories.

Figure 3 shows an eagle-i deployment using SPIN.

...