...

Figure 2. Details of the eagle-i stack

Repository

Wiki MarkupThe eagle-i repository provides a REST API for storage and retrieval of eagle-i resource descriptions. It internally uses the Sesame RDF store. The repository functionality includes role-based access control, transactional CRUD operations on eagle-i instances \ [1\], a  a data staging mechanism in the form of a curation workflow, a harvesting mechanism for incrementally communicating updates aimed at building search indices and a general purpose SPARQL query endpoint.  

Data tools

The eagle-i platform utilizes a variety of tools for repository data ingest, broadly referred to as data tools. The different tools share a common layer for interacting with the eagle-i repository.

...

Figure 3. Sample eagle-i deployment

Terminology

Wiki Markup*\[1\] eagle eagle-i resource instance *\- a collection of RDF statements about the same subject or about an _embedded instance_ \[2\] subject, plus the display labels of all predicates and objects used in these statements.resource instance - a collection of RDF statements about the same subject or about an embedded instance [2] subject, plus the display labels of all predicates and objects used in these statements.

[2] embedded instance - an instance that can only exist in the context of a parent instance and that cannot be linked to from other instances. Embedded instances do not have provenance Wiki Markup*\[2\] embedded instance* \- an instance that can only exist in the context of a parent instance and that cannot be linked to from other instances. Embedded instances do not have provenance metadata

How are we doing?

Is there anything that could be clearer in our documentation? We welcome your questions and feedback.