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.3.0. Please see the Upgrade Checklist for information on how to perform an upgrade.

How to use this document

Notes for this release are broken up into four categories: New Features, Improvements and/or Bug-fixes, Known Issues, Prerequisites for Upgrading & Deprecated Properties.  Within each category, notes are further divided into the application that is affected. Known issues will be cumulative of known issues that have not yet been resolved. If you are unsure what applications are applicable for your installation, please refer to this page.

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

Institutions that have installed the optional SPARQLer application will be interested in the SPARQLer section within each category.

Institutions that have installed the optional Institutional Search will be interested as well in items that have been tagged INSTITUTION in the Search Application section within each category.

For those who have chosen to administer their own network of nodes, the sections of interest are General, items that have been tagged CENTRAL in Search Application  and Network Administration (Central Search Only) sections within each category.

 

New Features, Improvements and/or Bug-fixes

General

  • NEW FEATURE Public sparql endpoint (version 2.0-MS3.07 or later) is now a required component.
    • We are moving toward features that require the use of the public sparql endpoint.  The specific features will be noted as they are released.
  • IMPROVEMENT Updated and refactored in preparation for solr upgrade.
    • Should no longer see "obsolete" warnings from solr in the logs.

Search application

Applies to both central and institutional search, unless otherwise specified.

  • BUG Sorting by resource type after executing a search is working again.

Network Administration

Available in Central Search only.

  • NEW FEATURE Now checks to see if an institution has a working public SPARQL endpoint

    • Schema for node-registry.xml has changed to include an additional attribute for the SPARQLer status.

      was:

      <node URL="https://hawaii.eagle-i.net" status="Node is running normally">

      now:

      <node URL="https://hawaii.eagle-i.net" status="Node is running normally" sparqlerStatus="Sparqler is running normally">

Known Issues

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

Current Release

Network Administration

  • node-registry.xml files are not backwards compatible.
    • The new attribute in the <node></node> field makes node-registry.xml files that have been updated by central search versions (3.3.0 and newer) un-compatible with older versions (3.2.0 and older).  Workaround:
      1. Stop tomcat
      2. Open the node-registry.xml file
      3. Manually remove the attribute and value for sparqlerStatus
      4. Save the node-registry.xml file
      5. Start tomcat

Prior Releases

3.0.4 Release

General

  • Incomplete records may be displayed in central search if no upgrade is done. Extensive work has gone into our ontology for this release to bring eagle-i to ISF compliance, in addition to enhancing the modeling 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.

Network Administration

Available in central search only.

  • We have seen an issue with how strictly different versions of tomcat parses local-node.xml file.  One version insisted on case sensitivity for the tag, and one version was fine. For example, tomcat version 7.0.42 does not have same parsing as version 7.0.41.  In other words, using <node url="https://some.institution.edu"> in the local-node.xml file was acceptable in one version, while the same exact line caused a parsing error (note the lower case 'url' instead of the documented 'URL').

2.0 MS 3.07 Release

General
  • When using drop down boxes in Chrome, it is not possible to jump to an entry by typing the first few letters. (No workaround)
SWEET
  • It is possible to save records with unnamed embedded instances. Doing so results in losing any information entered for the embedded instances. (No workaround)
  • 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. (No workaround)
Search application

Applies to both central and institutional search, unless otherwise specified.

  • Entering text with square brackets, [ & ], in the search box will execute a blank search, rather than searching for the text. (No workaround)
  • "Cite This Resource" - The keyboard shortcut for copying does not work in Firefox or Chrome. Workaround:
    1. Use the Copy from the browser's menu bar or from the popup while right clicking.
Network Administration

Available in central search only.

  • In the network administration UI (at <myNode>/central/admin), there is no direct way to remove a node (institution) from a group. Workaround:
    1. Use central/admin to edit the node:
    2. Take the node out of service (a check-box near the bottom of the form)
    3. Save
    4. Edit the node again, removing the value from the field "Belongs to group"
    5. Put the node back into service (the same check-box)
    6. Save
  • In the network administration UI (at <myNode>/central/admin), there is no direct way to change the group a node belongs to. Workaround:
    1. Use central/admin to edit the node:
    2. Take the node out of service (a check-box near the bottom of the form)
    3. Save
    4. Edit the node again
    5. Enter a new name in the field "Belongs to group"
    6. Put the node back into service (the same checkbox)
    7. Save

Prerequisites for Upgrading

SPARQLer

Also known as the public SPARQL endpoint.

Please install the public SPARQL endpoint, instructions for installation can be found here: Public SPARQL Endpoint.

Deprecated Properties

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

No deprecated properties for this release.

  • No labels