Versions Compared

Version Old Version 7 New Version 8
Changes made by

Kyle Hutson (Unlicensed)

Kyle Hutson (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Release Date: October 24, 2018

Contributors
showCounttrue
showLastTimetrue

Research Master ID Site New Features and Bug Fixes (v1.2.5)

1. (RMID/eIRB API) Update Configuration

 The RMID configuration has been updated to coincide with the recently updated eIRB server settings.

.(RMID) Change API Data Refresh Schedule

Background: eIRB imaging site creates the snapshot data every 15 minutes from 10, 25, 40, 55 of every hour.In in this production, the RMID eIRB refresh schedule  has been changed to every hour (7:05, 8:05, etc) in order to shorten the time in-between the RMID data refresh and the eIRB one, so that the updates made in eIRB system is reflected more timingly, we should change the RMID eIRB refresh schedule to every hour (7:05, 8:05, etc) insteadeIRB data refreshes. This change in refresh schedule will result in more timely updates.

(RMID) eIRB API Update: Add eIRB Fields

Background: Now that the 3 In this production, the three eIRB dates (Initial eIRB Approval Date, Current eIRB Approval Date, eIRB Expiration Date) are now being pulled into RMID backend , we need to expose these attributes and exposed via the RMID API so that they can be used in . These fields were pulled in to be shared with SPARCRequest. In addition, the eIRB Pro# should be exposed.

(RMID API) Expose CoeUs Project ID

Now that the COEUS Project ID has been added to the back-end, we need to expose it via the Research Masters API

has been exposed on the front-end.

(RMID) Research_masters. department Migration to Users Table

For the

The pi_department information that's currently stored in the research_masters table, could we integrate that into the users table as well, or reference out to the existing departments table?

Department (affiliation) logically is tied with the user.

Note that this is also part of preparation for us to unify the department fields for each user to get ready for using a single source in the future (from PRISM or else).

(RMID) Protocol PI Update for Complete eIRB Studies

When a PI moves to a different institution, their eIRB netID column gets updated to the new institution, which caused problem for RMID logic when trying to update the PI accordingly.

Please add the logic In this production, logic has been added to the eIRB/RMID API, so that PI-related protocol fields (First Name, Last Name, net_id) do not get updated for eIRB protocols under "Completed" state. There was a previous logic update issue that occurred when a PI moved to a different institution, which resulted in their eIRB netID column to be updated to the new institution, causing issues when trying to update the PI accordingly. This has since been fixed.

.(RMID) Add and Expose COEUS Project ID

As a prep work for a SPARCRequest new feature, the COEUS project ID (SRC_ORSP_AWARD_DETAILS.ACCOUNT NUMBER)  has been brought into the protocols table. This field will be used for the RMID/SPARC API and exposed on the front-end.

 (RMID) API Cronjob Improvements

The following Improvements have been made to the RMID cronjob to update that updates data every 4 hours from SPARC, eIRB and coEUS some times stops working without any signs, please:

  1. Better better exception handling . So that failures are captured and to capture failures and also provide an e-mailed mail to the development emails and sparcrequest@musc.eduOptimization: team

  2. better optimization for better efficiency of the updating logic, instead of reseting all the values and start-over every time. Note that based on 9/26 record, the eIRB refresh alone took more than 30 minutes.Start/completion notifications.update logic

  3. Start and completion notifications added

(RMID)

 Add

Visual Indicators Added for Associated Protocols from Different Systems

1). On

In this production, visual indicators have been added on:

  1. the "Associated Protocols" popup modal
, please add the "(
  1. (i.e. "RMID: 1")
" to display the RMID number.
2). Add
  1. color legends
on the RMID record
  1. to indicate whether there are protocols associated
, and use
  1. ; different colors
to
  1. represent different systems
.

(RMID) Adding COEUS Project ID

As a prep work for a SPARCRequest new feature: we need to bring in COEUS project ID (SRC_ORSP_AWARD_DETAILS
  1. .
ACCOUNT NUMBER) into the protocols table, as one of the fields usable for RMID/SPARC API.

(RMID) Missing net_id in primary_pis

There were previous Null values for the primary_pis.net_id and email columns.This data issue bug has since been resolved.

(RMID)   Different Different Users with Same NetID Bug

There are 30 couples of was a previous bug that allowed some users in RMID currently to have the same NetID (see attached), which shouldn't be possible.
Query used:
select *
from users users1
join users users2
on users1.`net_id` = users2.`net_id`
and users1.`id` != users2.`id`

NetID should be unique for each user.

Please look into the cause of the issue for a fix. This bug has since been fixed and all NetID's are truly unique again.

 (RMID) Repetitive Auditing Issue

It seems that The RMID audit trail is was previously recording hundreds of the same entry (updating back and forth) entries for the same data row. Please look into this and optimize In this production, the update and save audit time .For example, when looking into the audit records of RMID 2074 on production, there were 2728 versions of this row of data, and they were updating the same field with the same contents back and forth.

(RMID)

(RMID)has been updated.

Copyright © 2017-2018 MUSC Foundation for Research Development