Release Date: November 29th, 2018
Research Master ID New Features and Bug Fixes (version 1.2.5)
1. (RMID/eIRB API) Updated eIRB Connection Configuration and Refresh Schedule
The RMID/eIRB API configurations on both the production and staging sites have been updated to coincide with the recently updated eIRB server settings.
With the upgraded eIRB database, it is now possible to get fresh data more frequently without slowing down systems. In this release, the RMID/eIRB API refreshing schedule has been updated to be every hour (7:05, 8:05, etc), in order to shorten the reaction time. This change in refresh schedule will result in more timely updates reflecting eIRB changes.
2. (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.
3. (RMID) Improved API Performance and Status Notification Mechanism
To better observe the API status between RMID and other connected systems, the following Improvements have been made to the hourly refresh job from RMID to SPARC, eIRB and coEUS systems:
1). Exception handling to capture failures and real-time notification to the development team;
2). Optimization for better efficiency of the protocol association and PI update logic;
3). Start and completion notifications added (on the development Slack channel for development team).
4. (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).
5. (RMID) Protocol PIs Will Not Update for Completed 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.
6. (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.
7. (RMID) Visual Indicators Added for Associated Protocols from Different Systems
In this production, visual indicators have been added on:
The "Associated Protocols" popup modal will now include the RMID number associated to the protocol. (i.e. "RMID: 1")
Color legends to indicate whether there are protocols associated have been added, and the different colors represent different systems that the protocol has been associated to.
8. (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.
9. (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.
10. (RMID) Repetitive Auditing Entries Bug Fix
The RMID audit trail was previously recording hundreds of the same entries for the same data row because of the flawed logic. In this production, bug has been fixed.
Add Comment