2.0 MS 3.1 Release Note

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 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 process for who to contact for a resource has been improved:
    1. Contact the person specified for this resource as the contact person. If this is not specified or no valid email is provided, then
    2. Contact the general email for the lab that the resource belongs to. If this is not specified or no valid email is provided, then
    3. 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
    4. Contact the PI for the lab that the resource belongs to. If this is not specified or no valid email is provided, then
    5. Contact the Co-PI for the lab that the resource belongs to. If this is not specified or no valid email is provided, then
    6. Contact the Director for the lab that the resource belongs to. If this is not specified or no valid email is provided, then
    7. 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
    8. 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. To add a node to an existing group, the group name needs to be identical (includes case sensitivity and possible leading/trailing whitespaces). A new group will be created for the node if the group name does not already exist.
  • improvement Instance pages should load faster now.

Known Issues

• General

  • When using drop down boxes in Chrome, it is not possible to jump to an entry by typing the first few letters.

• SWEET

  • It is possible to save records with an unnamed embedded instances. Doing so results in losing any information entered for the embedded instance.
  • If more than one organization record has the same exact name, only one of them will be displayed in the "Work With My Organizations" dropdown.

• 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.
  • "Cite This Resource" - The keyboard shortcut for copying does not work in Firefox or Chrome. The current work around is to use the Copy from the menu bar or right clicking.

• Search application (Central Only)

  • There is no direct way to remove a node (institution) from a group. The workaround is:
    1. Edit the node
    2. Take the node out of service
    3. Save
    4. Edit the node again
    5. Put the node back into service
    6. Save
  • There is no direct way to change the group a node belongs to. The workaround is:
    1. Edit the node
    2. Take the node out of service
    3. Save
    4. Edit the node again
    5. Enter a new name for the group
    6. Put the node back into service
    7. Save

       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.

• 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

• Node configuration file(s) (for SWEET & Institution Search applications)

  • whoami.xml
    • File needs to be renamed "local-node.xml"
    • Within this file, change

      <node url="https://some.institution.edu">

      with

      <node URL="https://some.institution.edu">

      Please note that this is case sensitive.

Deprecated Properties

• eagle-i-apps.properties

  • eaglei.datatools.repository.url
  • eaglei.ui.ontologyBrowser.url
  • eaglei.noderegistry.url
  • eaglei.identity.url

• configuration.properties

  • eaglei.repository.index.url