You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Introduction

This document contains the release notes for eagle-i Resource Ontology (ERO) version 2.0.3, released in conjunction with eagle-i application version 4.0.0.


General

  • Refactoring

    • ISF refactoring: includes getting existing eagle-i MIREOTs integrated into ISF and regenerated into the eagle-i ontology. This refactoring, while largely invisible to end users, will support efficient maintenance and better integration with current community ontologies, and thereby data integration capabilities.
    • Disease ontology: the MeSH disease hierarchy has been replaced by the Disease Ontology (DO) hierarchy. Migration files with mappings to update legacy data are included with the 4.0.0 software release.
    • Update software ontology:
      • definitions and metadata for objectives, data types hierarchies (hundreds of classes)
      • analysis of integration issues with SWO 
      • merging eagle-i modeling into SWO 
      • re-mireoting content back into ISF

Known Issues

 

Note: this is a major ontology release and is not fully backwards compatible. For this reason, it is highly recommended that institutions indexed in eagle-i Central Search that are using an older version of the ontology upgrade as soon as possible.

  • The old MeSH terms will display in instance pages for institutions that don’t update, but clicking on the disease name pulls up a loading error message that the repo where that term resides is currently unavailable.
  • Searching for MeSH term names will not bring up results for those terms unless the term appears in a field other than related disease, i.e. searching for “Adenoma” will pull up resources with the term in the description, but not the ones that list it as a related disease:
  • MeSH terms will not show up in autosuggestions unless the exact same name also exists in the new disease ontology. But again, even if the names are the same, instances with the old terms will not show up in search results unless that term exists free text somewhere else in the record.
  • In the SWEET, as observed with prior backwards compatibility issues, disease terms will show up the SWEET dropdowns of institutions that haven’t upgraded. Although the terms will not resolve properly in the SWEET once selected, they will resolve correctly in search.
  • Filtering by diseases in iPS Cell Search will not pull up any cell lines from sites that are using the old disease ontology.
  • No labels