Page Comparison

Release Date: March 25, 2019

Research Master ID New Features and Bug Fixes (version 1.3.0)

1. (RMID) Updated Email Contact on Homepage and RMID Emails

In this release, the email address shown on the RMID homepage and in the RMID system-generated emails has been updated to rmid@musc.edu, which is a shared inbox managed by the Research Integrated Network of Systems (RINS) group.

Image Modified

2. (RMID) Replace LDAP Source with ADS 

In this release, the identity information feed from Lightweight Directory Access Protocol (LDAP) has been replaced with Active Directory System (ADS);

With this new feed, we are using a more reliable key (pvid) now and resolved issues with pulling and displaying middle names to help identifying the user.

Note: Affiliated NetID users can still log into RMID system after this reconfiguration.

Image Modified

3. (RMID) Add Dependabot to RMID Repository

For maintenance of the system, all gems have been updated in RMID has been updated to latest in this release;  We have also added Dependabot (automated dependency updates tool) to the RMID repository as well.

4. (RMID) Primary Investigator on an RMID Are Now Able to Edit/Delete

A previous bug prevented Primary Investigator (PI)'s the rights to edit or delete a RMID record that he/she has been listed on. In this release, this bug has been fixed and the PI now has the same rights to an RMID record as the creator:

1). Ability to Delete the RMID record
2). Ability to Edit the record when it's not validated yet

Image Modified

5. (RMID) Email Notifications Bug Fix and Improved Job Automation

A previous bug prevented RMID email notifications from being sent when the corresponding job fails. This bug has since been fixed and emails are working correctly.

Image RemovedImage Added

Now our development team has an hourly monitoring and fail-safe mechanism for better automation (The job watcher will restart if necessary every hour, and also display the result on Slack channel).

Image RemovedImage Added

 6. (RMID) Ability to Edit Funding Source and Research Type Fields after eIRB Validation

Previously, all RMID fields were tied to the eIRB validation flag, so that the "Edit" button was disabled once the associated eIRB record was beyond approval. However, RMID users needed a way to update the two fields that were entered into RMID and exist in RMID only. In this release, users (RMID creator, PI, and RMID admins) now have the ability to edit and update the two fields ("Funding Source" and "Research Type") even after the eIRB validation is flagged on a record.

Image RemovedImage Added

7. (RMID) Research_masters. department Migration to Users Table: Part 2

The department data from PRISM has been restructured in RMID to linking to the users.department instead. The following changes have been made:

1). The "Department" showing on a RMID record is now reading from the users.department for the associated PI on the RMID record;
2). research_masters.department column has been removed;
3). When a new  Primary PI Information and Department Reconfiguration

In this release, we have restructured the backend data for primary PI information (such as first name, last name, email, department etc) that's associated with protocols coming from eIRB and SPARCRequest, to increase the efficiency of the system, and also to link the data feed to ADS (for identity information) and PRISM (for department affiliation if exists in PRISM). Once a user is pulled into the users table , his/her department is subsequently pulled from the PRISM API.

Image Removed

8. (RMID) Research_masters.department Migration to Users Table: Part 3

When creating a new RMID record, after filling in the PI, their department will now pull from the user's table if the PI exists there. If the PI is a prism user, the field will be disabled.

10in RMID, and a protocol from eIRB or SPARCRequest has that user as a PI, the pre-saved information (Department) will be loaded for that PI. This change doesn't affect frontend functionalities, but improves the efficiency of the system and data storage.

8. (RMID) PI Affiliation Lock-down When down Fix When Editing RMID Record

Currently, PI Affiliation is auto-filled from PRISM, however when a user went Following the PRISM API we implemented in the previous release (see RMID v1.2.5 Item 7), in this release, when a user comes back to edit a RMID record and did not without reset/change the PI, the "Department" field became enabled again. This would occur even when showing the PRISM department, which enabled manual entry for the user. In this release, the department field is now disabled when showing information from the PRISM (API)now remains locked if it is pulling from PRISM source. The only scenario where department is editable in RMID is when that PI is not found in via the PRISM API.Image Removed

When Editing RMID with PI PRISM Interfaced	When Editing RMID with Manually Entered PI Affiliation (PI not in PRISM)
Image Added	Image Added