Contributors | ||||||
---|---|---|---|---|---|---|
|
Release Date: March 30th, 2020
Status colour
Bluecolour |
---|
Green title
In processGreen |
title |
---|
Finished
Finished |
Research Master ID New Features and Bug Fixes (
v1version 1.4.0)
1. (RMID
) Authentication) Updated Single Sign-On (SSO) from Shibboleth to ADFS
The single-sign-on(SSO) integration that Research Master ID utilizes has switched from Shibboleth to ADFS.
2. (RMID/SPARC API)
SPARC Production and Staging Connection UpdatedSPARCUpdated SPARCRequest Data Connections
SPARCRequest database servers were recently updated
(December 2019)for both SPARC Staging and Production sites in December (2019).
In this release, the connection information has also been updated accordingly for RMID Staging and Production API's, so that new SPARC protocols are being brought on hourly basis.
3. (RMID)
AddingCAYUSE API
- Data Access & UI DisplayAdded
In this release, Cayuse SP has been added as the fourth data source feed into RMID. Associated
protocols willCayuse projects are displayed with show Project
_number, Research_team (PI's name)Number, PI Name, and Project_title. The grants/award system
CoeUsCOEUS was previously replaced by Cayuse SP and both data source feeds will exist in RMID as the transition between systems is smoothed over.
Please contact your Cayuse admin to correct the RMID on Cayuse projects, if any wrong associations for Cayuse are identified.
4. (RMID/eIRB) API
is BrokenBug Fix
A previous bug occurred where the RMID
_/eIRB API was failing
resulting, which resulted in eIRB associations to not display in RMID. This bug has since been fixed
and all associations are updated from the previous bug.
5. (RMID) eIRB New primary PI and Update Issue
In this release, the eIRB/RMID API method has been improved to handle the following scenarios:
1).
ifIf the primary PI on eIRB protocol is a user who doesn’t exist yet in RMID users table, LDAP is now queried to fetch and create the RMID user for that eIRB PI.
2).
ifWhen the PI changes
inon an existing eIRB record, then they will be updated accordingly in the RMID
back-endbackend.
SCREENSHOTS??
6. (RMID/eIRB) Withdrawn eIRB and Active eIRB with the same RMID
Previously, when there were scenarios where multiple eIRB protocols were using the same RMID
. As a result, the RMID/eIRB API could not decide which eIRB record to associate the RMID with, as well as which to display in the user interface.
In this release, the RMID system will only associate the RMID record to the eIRB record that's not Withdrawn. The association will be updated to have the verified, but not Withdrawn eIRB record when this scenario occurs moving forward.
The screen shots below shows an example of this scenario:
Example RMID used ona withdrawn eIRB and an active eIRB records | Before this Release | After this Release |
---|---|---|