Page History
Info |
---|
Pages here should be assumed to pertain to the latest release (currently 23.07). |
This documentation is a work in progress. We are grateful to the many people who have contributed to improving it. Please keep your comments coming.
Release Notes
- 2.0 MS 3.07 Release Notes Latest release
System Overview
- System Overview: This document provides a high-level overview of the system. It describes the ontology-centric architecture, an institutional deployment and the eagle-i software stack including the repository, data tools, search and ontology/data model.
Developers
Web Services
- Web Services Provided by eagle-i Nodes: Describes public web services for retrieving eagle-i data.
- Web services Provided Centrally: Describes public web services for obtaining ontology information.
Ontology
Repository
- Repository Design Specification and API*: This document is intended to be a thorough description of the data repository design; concentrating on its external interfaces. The intended audience is repository coders as well as implementers of other components that depend on the repository. It also serves as an API reference manual.
- Repository Workflow Design Notes: Contains requirements, use cases, ontology design principles, access control and API for eagle-i workflow.
- Repository Embedded Instances Design Notes: This page describes how embedded instances are to be managed by the repository.
Applications
- Sweet Developers Guide: This is a developers' guide to the eagle-i data tools. It's focus is primarily on the SWEET (Semantic Web Entry and Editing Tool).
- Search Application Developers Guide: This is a developers' guide to the eagle-i search application. It covers the search backend and Solr.
Javadocs
- Current release : http://search.eagle-i.net/javadoc => javadocs are currently not deploying correctly
- Nightly build : http://search.qa.eagle-i.net/javadoc
Experimental Work
...
Panel |
---|
Installation and Administration Data Ingest and Data Management Integration with Profiles RNS: this page describes the eagle-i API for displaying resource information in the Profiles RNS application |
How are we doing?
Is there anything that could be clearer in our documentation? We welcome your questions and feedback.
Overview
Content Tools