Date: Thu, 28 Mar 2024 14:42:51 -0400 (EDT)
Message-ID: <116923762.790.1711651371274@prodopencatalystconfluence.catalyst>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_789_3923001.1711651371270"
------=_Part_789_3923001.1711651371270
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
Introduction
A new version of the eagle-i applications is now available for download. The release notes do=
cumented on this page apply specifically to version 2.0 MS 3.07.
How to use this document
Notes for this release are broken out into five categories: #Bug fixes, #Improvements/New Features, #Known Issues, #Prerequisites for Upgr=
ading & =
#Deprecated Properties. Within each category, notes are further divided=
into the application that is affected. If you are unsure what applications=
are applicable for your installation, please refer to this page.
Most institutions will be interested primarily with the General=
(affects across multiple applications) and SWEET sections within =
each category.
Institutions that have installed the optional Institutional Search will =
be interested as well with the Search Application (Institution and Cent=
ral) section within each category.
For those who have chosen to administer their own network, the sections =
of interest are General, Search Application (Institution and C=
entral), and Network Administration (Central Search Only).
How to upgrade
To upgrade an existing installation to this new version, please do the fol=
lowing in the specified order:
- Update configuration files (#Prerequisites for Upgrading)
- Upgrade repository (Repository Installation, Upgrade and Administra=
tion Guide#Upgrade)
- Upgrade applications (SWEET and Institutional Search Installati=
on and Upgrade Guide#Upgrade)
Bug fixes
General
- Redirects no longer cause error (e.g. 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<=
/h4>
- 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=
.
Network Administration (Central Search Only)
- Removed dependency on a local-node.xml file (previously named whoami.xm=
l)
-
Datamanagement
now accepts "http://localhost" as a valid t=
arget repository parameter (used in data migration scripts)
Improvements/N=
ew Features
General
- improvement Data with non-UTF-8 cha=
racters are now correctly displayed (e.g. MS Word smart quotes)
- improvement The feedback form now u=
ses email. It is no longer dependent on the JIRA API.
SWEET applicatio=
n
- 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" shoul=
d not be entering data. If required, a second user account should be create=
d instead.
Search application (Institution and Central)
- new feature "Cite This Resource" b=
utton added for ease of finding the resource ID.
- 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 fo=
r who to contact for a resource has been improved:=20
- Contact the person specified for this resource as the contact person. I=
f this is not specified or no valid email is provided, then
- Contact the general email for the lab that the resource belongs to. If =
this is not specified or no valid email is provided, then
- 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 provide=
d, then
- Contact the PI for the lab that the resource belongs to. If this is not=
specified or no valid email is provided, then
- Contact the Co-PI for the lab that the resource belongs to. If this is =
not specified or no valid email is provided, then
- Contact the Director for the lab that the resource belongs to. If this =
is not specified or no valid email is provided, then
- Contact any person that is a member of the lab that the resource belong=
s to. If this is not specified or no valid email is provided, then
- Contact the eagle-i-postmaster
Search A=
pplication (Central)
- improvement Instance pages should l=
oad faster now.
Network Administration (Central Search Only)
- improvement Easier to administer th=
e network:=20
- 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 (i=
ncludes case sensitivity and possible leading/trailing whitespaces). A new =
group will be created for the node if the group name does not already exist=
.
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. (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. (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 (Institution and Central)
- Entering text with square brackets, [ & ], in the search box will e=
xecute a blank search, rather than searching for the text. (No workarou=
nd)
- "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 Administration (Central Only)
- There is no direct way to remove a node (institution) from a group. Workaround:
- Edit the node
- Take the node out of service
- Save
- Edit the node again
- Put the node back into service
- Save
- There is no direct way to change the group a node belongs to. Worka=
round:
- Edit the node
- Take the node out of service
- Save
- Edit the node again
- Enter a new name for the group
- Put the node back into service
- Save
Prerequisites=
for Upgrading
General configuration file(s) for all applications
- eagle-i-apps.properties - new required properties=20
- eaglei.feedback.email.host
- eaglei.feedback.email.from
- eaglei.feedback.email.to
Node configuration file(s) (for SWEET=
& Institution Search applications)
- whoami.xml=20
- File needs to be renamed "local-node.xml"
- Within this file, change=20
<nod=
e url=3D"https://some.institution.edu">
with=20
<nod=
e URL=3D"https://some.institution.edu">
Please note that this is case sensitive.
Deprecated Propert=
ies
eagle-i-app=
s.properties
- eaglei.datatools.repository.url
- eaglei.ui.ontologyBrowser.url
- eaglei.noderegistry.url
- eaglei.identity.url
configurat=
ion.properties
- eaglei.repository.index.url
------=_Part_789_3923001.1711651371270--