Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Implications of export page and sparqler

...

  • Status
    colourGreen
    titlenew feature
     
    Status
    colourYellow
    titlecentral
     
    iPSC (induced pluripotent stem cell) search now available. This feature issues a federated SPARQL query to all institutions in the network that have iPSCs. Users are able to download results as a csv file. No additional configuration is required to set up this feature.
    • Status
      titlePublic SPARQL endpoint
       This feature accesses the public SPARQL endpoint at each institution to determine availability of iPSCs and to execute a SPARQL query.  Institutions who would like to have their iPSC lines searchable through this feature must install the public SPARQL endpoint.

Website

Website refers to http://www.eagle-i.net

  • Status
    colourBlue
    titleimprovement
     Website now checks to make sure institutions have a public SPARQLer before listing them on the export page.
    • Status
      titlePublic SPARQL endpoint
       If an institution does not have a public SPARQLer version 2.0MS3.07 or later, they will not be represented on the export page.

Anchor
known
known
Known Issues

...

Expand
titleClick here to view known issues for prior releases...

3.3.0 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

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

Anchor
prereq
prereq
Prerequisites for Upgrading

SPARQLer

Also known as the public SPARQL endpoint.

In order to have representation on the export page, institutions must be running a public SPARQLer application that is version 2.0MS3.07 or later.

Property values changed

The location of the navigation snippets has changed. Please update the following properties to the value specified in the eagle-i-apps.properties files:

...