Introduction
A new version of the eagle-i applications is now available for download. The release notes documented on this page apply specifically to version 3.0.4.

Please note that we have moved to a more conventional approach for our version numbering scheme.  We are now using the format of: [major].[minor].[patch].  Also note that this is a major release and we are not guaranteeing backwards compatibility with previous versions.

How to use this document
Notes for this release are broken out into five categories: Bug fixes, Improvements/New Features, Known Issues, Prerequisites for Upgrading & Deprecated Properties. Within each category, notes are further divided into the application that is affected. If you are unsure what applications are applicable for your installation, please refer to this page.

Most institutions will be interested primarily with the General (affects across multiple applications) and SWEET sections within each category.

Institutions that have installed the optional Institutional Search will be interested as well with the Search Application (Institution and Central) section within each category.

For those who have chosen to administer their own network, the sections of interest are General, Search Application (Institution and Central), and Network Administration (Central Search Only).

How to upgrade
To upgrade an existing installation to this new version, please do the following in the specified order:

  1. Update configuration files (Prerequisites for Upgrading)
  2. Upgrade repository (Repository Installation, Upgrade and Administration Guide)
  3. Upgrade applications (SWEET and Institutional Search Installation and Upgrade Guide)

Bug fixes

Improvements/New Features

Known Issues

The following are known issues that may be addressed in future releases. If there is a suitable workaround for a given issue, it will be listed.

Current Release:

Extensive work has gone into our ontology for this release to bring eagle-i to ISF compliance, in addition to enhancing the modelling for induced pluripotent stem cell types.  If existing data is not migrated to the new ontology, the central search application may not be able to interpret/recognize obsolete ontological properties and will not display them

2.0 MS 3.07 Release:

Prerequisites for Upgrading

The following changes need to be done to upgrade to this version. These changes are not compatible with prior versions of the software.

There are several types of email that can be sent by the various applications.  Previously, each of these email types had separate properties for configuring how the emails should be sent, in addition to the email address that should be used.  In an attempt to simplify our configuration files, we have consolidated these properties.  There is now one set of properties to configure how an email should be sent.  Each email type will still be able to specify its own email address.

Deprecated Properties

The following properties have been deprecated and can be removed from the properties file to avoid confusion.

Properties with new default value

The following properties now have a default value and can be removed from your properties files if the default value is suitable.