Release Date: May 9, 2018
| Contributors | ||||
|---|---|---|---|---|
|
Research Master ID Site New Features and Bug Fixes (v1.2.0)
1. (RMID/SPARC API
/RMID) Upgrade to Ruby on Rails 5.1.5
In
our latest productionthis release, the RMID/SPARC API framework has been updated to
Ruby onuse 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
SPARC the SPARCRequest production site to improve accuracy.
3.
Testttttttttttttttt(RMID) Audit Trail Feature
An audit
trail table, with its related features, has been added to the RMID application
to enable. The audit trail feature enables tracking of creation, updates, and destroys of records, by both users and
API's.the Application Programming Interfaces (APIs).
4. (RMID) Improved Protocol Update Method
Logic Update (Wenjun??)
Previously there were scenarios where the PI name displayed for protocols
in RMID back-end was associated to a Research Master record were different from the current PI name shown in
SPARCSPARCRequest, 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
revampedsince improved to compare every protocol-level field and then determine whether an update to the protocol record is needed.
  |   |
|---|
5. (RMID)
RMIDResearch Master PI Update
from eIRB Validation Sending Emailand 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)
that has been validated in the eIRB record is now being used to update the PI-associated data within RMID. When a RMID record has been updated an email notification is sent to the RMID creator, the previous PI and the new PI, and logged-in admin user as a default sender The "Notification" button allows the admin user to type in the message to be emailed to the users.
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.
| Example Research Master PI Update Notification |
|---|
 |
6. (RMID) Admin Message
Minor RefactorThe following changes have been made to the Admin message sent out by clicking the envelop icon on RMID records:
1). User names included in the opening line
2). Language updated to include the RMID record number and Short Title to give users more information.
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.
(RMID) Notifications for Admin UsersA "Notification" button has been added on the RMID homepage for admin users. This button allows the admin user to send a notification email to both the Requester user and the PI user and defaults to the admin users as the sender.
8. (RMID) Associated Popup Bug Fix
PreviouslyPreviously, 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
RMID's, even those that do not have associated records.
The netID
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 |
|---|---|
|
|
11. (RMID) NetID Information Added to Users Table
In this release, the NetID column has been added to the users table.
(RMID) Protocol Update Method Logic Fine-Tune
(RMID) Investigate Missing net_id in primary_pis
(RMID) Investigate Missing pi_id in research_masters Record
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.
Copyright © 2017-2018 MUSC Foundation for Research Development