Release Date: October 24, 2018
| Contributors | ||||
|---|---|---|---|---|
|
Research Master ID Site New Features and Bug Fixes (v1.2.5)
1. (RMID/
SPARCeIRB API)
Upgrade to Ruby on Rails 5.1.5In this release, the RMID/SPARC API framework has been updated to use Rails 5.1.5, for maintenance and better performance.
2. (SPARC API) Remove Custom DB connection
The SPARC API previously had its own database, but now pulls data directly from the SPARCRequest production site to improve accuracy.
3. (RMID) Audit Trail Feature
An audit table, with its related features, has been added to the RMID application. The audit trail feature enables tracking of creation, updates, and destroys of records, by both users and the Application Programming Interfaces (APIs).
4. (RMID) Improved Protocol Update Method
Previously there were scenarios where the PI name displayed for protocols associated to a Research Master record were different from the current PI name shown in SPARCRequest, or eIRB. These scenarios were caused by the PI change in different systems not being updated in the RMID back-end. The protocol update method has been since improved to compare every protocol-level field and then determine whether an update to the protocol record is needed.
5. (RMID) Research Master PI Update and Notification According to Verified eIRB Record
When a RMID is used in the eIRB system and the corresponding eIRB record has been in an approved and beyond status, in addition to the titles of the Research Master record, the Primary PI-associated data (Name and netID) are now also updated accordingly.
In addition, the system is now sending automatic emails to the previous PI, creator, as well as the updated PI of the record, to notify users of the PI change when the PI on the research master record is updated according to the eIRB record.
6. (RMID) Admin Message Feature
In the event a RMID administrative user needs to contact the user(s) of a Research Master record, there is now a "Send Notification" button available on each record . With this new feature, admins can now send messages to the creator and PI of the RMID record to their MUSC email addresses directly if desired.
Notification Window for Admin Users
Example Notification Email
7. (RMID) Edit Button Bug Fix
In this release, a potential security issue has been fixed where an admin user could change the property of a disabled "Edit" button on a Research Master record from the browser console and make it editable. This bug has since been fixed, and even admin users are not able to edit a verified record.
8. (RMID) Associated Popup Bug Fix
Previously, when clicking on an existing RMID, a pop-up box did not appear for those that had no associated records. This bug has since been fixed and the pop-up box now appears for all Research Master records (see below for screenshots).
RMID with Associated Protocols
RMID without Associated Protocols
9. (RMID) CoeUs Record Association Display Bug Fix
Previously, when moving the association of a SPARC protocol from using one RMID (i.e RMID#1) to the another RMID (i.e. RMID#200), associated CoeUs record(s) (i.e. MIT Award Number 020045-001) were also removed inadvertently from the displayed association of the original RMID (i.e. RMID 1). The removal of the CoeUs association was not intended and should not have been dissociated from the RMID (i.e. RMID 1). This association bug has since been fixed.
Before Changing RMID in SPARCRequest
After Changing RMID in SPARCRequest
10. (RMID) Automatic Filter Added for Special Characters
To avoid the errors caused by special characters for systems that are not compatible with them (such as Epic) and improve the data consistency, automatic filters have been added for special characters and excessive blanks in the text fields of RMID.
Example Text Fields with Special Characters
After Automatic Filtering
In this release, the NetID column has been added to the users table. This column was added to establish ground work in the upcoming releases to condense the Primary PI information from different systems into linked users' records, which will improve the system efficiency. The primary PI on the Research Master record itself has been mapped and linked to the corresponding user, based upon this data structure change
Update Configuration
RMID configuration has been updated to coincide with the recently updated eIRB server settings.
. (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 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.
. (RMID) API Cronjob Improvements
The RMID cronjob to update data every 4 hours from SPARC, eIRB and coEUS some times stops working without any signs, please:
Better exception handling. So that failures are captured and e-mailed to the development emails and sparcrequest@musc.edu
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.