A new version of the eagle-i applications is now available for download. The release n=
otes documented on this page apply specifically to version 3.3.0. Plea=
se see the Upgrade Checkl=
ist for information on how to perform an upgrade.
How to use thi=
s document
Notes for this release are broken up into four categories: New Features, Improvements and/or Bug-fixes=
, Known Issues, <=
a href=3D"#id-3.3.0ReleaseNotes-prereq">Prerequisites for Upgrading&nbs=
p;& Deprecated Proper=
ties. Within each category, notes are further divided into the ap=
plication that is affected. Known issues will be cumulative of known issues=
that have not yet been resolved. If you are unsure what applications are a=
pplicable for your installation, please refer to this page.
Most institutions will be interested primarily in the General=
em> (affects across multiple applications) and SWEET&nbs=
p;sections within each category.
Institutions that have installed the optional SPARQLer application will =
be interested in the SPARQLer section within each catego=
ry.
Institutions that have installed the optional Institutional Search will =
be interested as well in items that have been tagged INSTITUTION in the&nb=
sp;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 Netwo=
rk Administration (Central Search Only) sections within each cate=
gory.
NEW FEATUR=
E Public sparql endpoint (version 2.0-MS3.07 or later) is =
now a required component.=20
We are moving toward features that require the use of the public sparql=
endpoint. The specific features will be noted as they are released.<=
/li>
IMPROVEMEN=
T Updated and refactored in preparation for solr upgrade.=20
Should no longer see "obsolete" warnings from solr in the logs.
Search application
Applies to both central and institutional search, unless otherwise s=
pecified.
BUG Sorting by resource type after executing a search is working again.<=
/p>
Network Administratio=
n
Available in Central Search only.
NEW FE=
ATURENow checks to see if an institution has a working pu=
blic SPARQL endpoint=20
Schema for node-registry.xml has changed to include an additional at=
tribute for the SPARQLer status.
was:
<node=
URL=3D"https://hawaii.eagle-i.net" status=3D"Node is running normally">=
now:
<node=
URL=3D"https://hawaii.eagle-i.net" status=3D"Node is running normally" spa=
rqlerStatus=3D"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 liste=
d.
Current Release
Network Administrat=
ion
node-registry.xml files are not<=
/em> backwards compatible.=20
The new attribute in the <node></node> field makes node-reg=
istry.xml files that have been updated by central search versions (3.3.0 an=
d newer) un-compatible with older versions (3.2.0 and older). Wor=
karound:
Stop tomcat
Open the node-registry.xml file
Manually remove the attribute and value for sparqlerStatus=
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 migrate=
d to the new ontology, the central search application may not be able to in=
terpret/recognize obsolete ontological properties and will not display them=
.
Network Administrat=
ion
Available in central search only.
We have seen an issue with how strictly different versions of tomcat pa=
rses local-node.xml file. One version insisted on case sensitivity fo=
r the tag, and one version was fine. For example, tomcat version 7.0.4=
2 does not have same parsing as version 7.0.41. In other words, using=
<node url=3D"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 c=
ase 'url' instead of the documented 'URL').
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 s=
o results in losing any information entered for the embedded instances.&nbs=
p;(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.&nbs=
p;(No workaround)
Search application
Applies to both central and institutional search, unless otherwise s=
pecified.
Entering text with square brackets, [ & ], in the search box will e=
xecute a blank search, rather than searching for the text. (No wor=
karound)
"Cite This Resource" - The keyboard shortcut for copying does not work =
in Firefox or Chrome. Workaround:
Use the Copy from the browser's menu bar or from the popup while right =
clicking.
Network Administrat=
ion
Available in central search only.
In the network administration UI (at <myNode>/central/admin), the=
re is no direct way to remove a node (institution) from a group. W=
orkaround:
Use central/admin to edit the node:
Take the node out of service (a check-box near the bottom of the form)<=
/li>
Save
Edit the node again, removing the value from the field "Belongs to grou=
p"
Put the node back into service (the same check-box)
Save
In the network administration UI (at <myNode>/central/admin), the=
re is no direct way to change the group a node belongs to. Workaro=
und:
Use central/admin to edit the node:
Take the node out of service (a check-box near the bottom of the form)<=
/li>
Save
Edit the node again
Enter a new name in the field "Belongs to group"
Put the node back into service (the same checkbox)
Save
Prere=
quisites 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.
D=
eprecated Properties
The following properties have been deprecated and should be removed from=
the properties file to avoid confusion.