MUSC Research Master ID

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Release Date: October 24, 2018

Kim Spencer (Unlicensed) 1 (2234 days ago), Kyle Hutson (Unlicensed) 1 (2234 days ago), Wenjun He (Unlicensed) 1 (2234 days ago)

Research Master ID 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

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 and eIRB data refreshes. This change in refresh schedule will result in more timely updates.

(RMID) eIRB API Update: Add eIRB Fields

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 and exposed via the RMID API. These fields were pulled in to be shared with SPARCRequest. In addition, the eIRB Pro# has been exposed on the front-end.

(RMID) Research_masters. department Migration to Users Table

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

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 that updates data every 4 hours from SPARC, eIRB and coEUS:

  1. better exception handling to capture failures and also provide an e-mail to the development team

  2. better optimization for better efficiency update logic

  3. Start and completion notifications added

(RMID) Visual Indicators Added for Associated Protocols from Different Systems

In this production, visual indicators have been added on:

  1. the "Associated Protocols" popup modal (i.e. "RMID: 1")
  2. color legends to indicate whether there are protocols associated; different colors represent different systems.

(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 Users with Same NetID Bug

There was a previous bug that allowed some users in RMID to have the same NetID (see attached). This bug has since been fixed and all NetID's are truly unique again.

 (RMID) Repetitive Auditing Issue

The RMID audit trail was previously recording hundreds of the same entries for the same data row. In this production, the update and save audit time has been updated.

Copyright © 2017-2018 MUSC Foundation for Research Development

  • No labels