An eagle-i institutional server, or eagle-i node, is a server that runs an eagle-i institutional software stack and that is independently managed at a participating institution. If an eagle-i node is part of the eagle-i network, Its public resources are periodically indexed by the eagle-i central search application.

At a minimum, an eagle-i node comprises:

• An eagle-i repository for storing resource descriptions
  • Needs access to an outgoing mail server (SMTP) to provide the Contact Resource Owner feature
• A Sparqler application for exposing a public SPARQL endpoint (user interface and web service) that allows non-registered users to issue queries against the public data
• A SWEET application for entering an editing resource descriptions
  • Needs access to an outgoing mail server (SMTP) to provide the Feedback feature

Optionally, the following component may be installed:

• An Institutional search application for providing an institution-only search interface (useful for eagle-i nodes that are not part of the eagle-i network)

In addition to installing and maintaining the software, eagle-i node administrators will need to lay out and implement a strategy for allowing their resources to be indexed by search engines, and for monitoring access (Google analytics). To support this, we provide an example robots.txt file; once installed the SWEET provides a web service for generating sitemaps; and we provide a configurable  Google analytics ID property.