Bug fixes
General
- Redirects no longer cause error (i.e. http redirecting to https)
- Feedback form is now fully visible without needing to scroll
- Resources of the type "Clinical Organization" are now showing in search results as well as in the SWEET workbench.
SWEET application
- Now able to save records when using Internet Explorer
Search application (Institution and Central)
- Use of the html tags for super & subscripts are now correctly displayed.
Search application (Central Only)
- Removed dependency on a local-node.xml file (previously named whoami.xml)
Tools
- Datamanagement now accepts "http://localhost" as a valid target repository parameter (used in data migration scripts)
Improvements/New Features
General
- improvement Data with non-utf8 characters are now correctly displayed (i.e. MS Word smart quotes)
- improvement The feedback form now uses email. It is no longer dependent on the JIRA API.
SWEET application
- improvement Entering data as a user with the role of "admin" no longer inserts spurious triples into the data. NOTE: We very strongly recommend that users with the role of "admin" should not be entering data. If required, a second user account should be created instead.
Search application (Institution and Central)
- new feature "Cite This Resource" button for ease of citing a resource.
- improvement The contact button has been moved for better visibility and the text display is now conditional on the resource type being displayed.
- improvement The decision tree for who to contact for a resource has been improved:
- Contact the person specified for this resource as the contact person. If this is not specified or no valid email is provided, then
- Contact the general email for the lab that the resource belongs to. If this is not specified or no valid email is provided, then
- Contact the person specified as the contact person for the lab that the resource belongs to. If this is not specified or no valid email is provided, then
- Contact the PI for the lab that the resource belongs to. If this is not specified or no valid email is provided, then
- Contact the Co-PI for the lab that the resource belongs to. If this is not specified or no valid email is provided, then
- Contact the Director for the lab that the resource belongs to. If this is not specified or no valid email is provided, then
- Contact any person that is a member of the lab that the resource belongs to. If this is not specified or no valid email is provided, then
- Contact the eagle-i-postmaster
Search application (Central Only)
- improvement Easier to administer the network:
- Node registry application has been folded into the central application to improve robustness.
- Now able to add a node to a specific group via the network admin page.
- improvement Instance pages should load faster now.
- improvement Easier to administer the network:
Known Issues
The following are known issues that are in the queue.
Search application (Institution and Central)
- Entering text with square brackets, [ & ], in the search box will execute a blank search, rather than searching for the text.
Non-compatible Changes
The following changes need to be done to upgrade to this version. These changes are not compatible with prior versions of the software.
- Entering text with square brackets, [ & ], in the search box will execute a blank search, rather than searching for the text.
General configuration file(s) for all applications
- eagle-i-apps.properties - new required properties
- eaglei.feedback.email.host
- eaglei.feedback.email.from
- eaglei.feedback.email.to
- eagle-i-apps.properties - new required properties
Node configuration file(s) (for SWEET & Institution Search applications)
- whoami.xml
- File needs to be renamed "local-node.xml"
- Within this file, change
with
<node url="https://some.institution.edu">
Please note that this is case sensitive.<node URL="https://some.institution.edu">
- whoami.xml
Deprecated Properties
The following properties have been deprecated and can be removed from the properties file to avoid confusion.
eagle-i-apps.properties
- eaglei.datatools.repository.url
- eaglei.ui.ontologyBrowser.url
- eaglei.noderegistry.url
- eaglei.identity.url
configuration.properties
- eaglei.repository.index.url
Overview
Content Tools