SPARCRequest v1.6.0 + SPARCFulfillment v2.0.1 New Features and Fixes_(for open source)

SPARCRequest Wiki

SPARCRequest v1.6.0 + SPARCFulfillment v2.0.1 New Features and Fixes_(for open source)

SPARCRequest Version 1.6.0 New Features

  1. (SPARCRequest) FAQ pop-up window configuration


The format of the "Help/FAQ" function (pop-up window) is now available for other institutions. It is now possible to turn it on and off in the configuration file (choose between pop-up window or link to another webpage).

  1. (SPARCRequest) Right panel buttons reconfiguration







The "Ask A Question" and "Dashboard" buttons have been removed from this panel. The "Feedback" button now opens up a new browser tab showing the RedCap survey. We have also added a "Contact US" button that will be opened as a popup window with which the user can contact the SPARCRequest Team directly through email.

  1. (SPARCRequest) Protocol information page bug fixed

The bug with the SPARCRequest protocol information page (Step 1) that was pointed out by LACaTS has been fixed. Now the checkboxes can be unchecked and saved.

 

  1. (SPARCRequest and SPARCAdmin) Visit calendar window +/- signs alignment


The + and - associated with the windows in the visit calendar on Step 2B in SPARCRequest and SPARCadmin are now centered and aligned with the corresponding days.

  1. (SPARCRequest) "Save As Draft" function reconfiguration

In SPARCRequest, when a user clicked on the "Save As Draft" button with the required fields not filled out on Step 2A and 2B, it was creating a "request in progress" in SPARCDashboard, along with other data integrity issues. We have fixed the bug and changed the logic of the "Save As Draft" button to the following:
If the request has not been submitted before, the user can click the "Save As Draft" button and save it as a draft even when the required fields are not filled out;


If the request has been submitted before, then there is no "Save As Draft" button on Step 2A and Step 2B pages (because saving an already-submitted request without the required information is problematic).

  1. (SPARCRequest) Added new configurable "Advanced User Search" function



We included the "Advanced User Search" function that was developed by the University of Iowa. This function is now configurable to be turned on/off for the open source community. When this function is turned on, the original "search" box only searches the local database, and not every LDAP search result is automatically added. Underneath the "User Search" box there is an "Advance User Search" link that opens a new page where any user can add/import another user from the institutional LDAP individually. This new page also allows super users to edit an existing SPARC user's first name, last name, and email address.

  1. (SPARCRequest) New/Existing Protocol Reconfiguration

In this version of SPARCRequest, when a service is being added, a pop-up window will show us asking "Is this a new research study or project?" If "yes" is chosen, then user is allowed to continue adding services following the common service request workflow. If "no" is chosen, then the user is redirected to SPARCDashboard where they will need to find the corresponding existing protocol to work with. This pop-up only occurs when the first service is added to the shopping cart for a study/project.






  1. (SPARCRequest/SPARCDashboard/SPARCAdmin) Epic Questions Reconfiguration


We have reconfigured the Epic questions by grouping the questions into the "Epic Information" box on the protocol information page, and adjusted the logic-driven questions. The Certificate of Confidentiality question is now combined into the Epic Information section. In SPARCRequest and SPARCDashboard, the Epic questions and answers are displayed and editable; In SPARCAdmin, the answers to the Epic questions will be displayed if previously filled out, and will be display and not editable if not previously answered.

  1. (SPARCRequest) New navigation bar feature


In the new version of SPARCRequest, a navigation bar has been added on the top of every page. Clicking on the navigation bar, the user will find a new browser tab opened leading to the corresponding SPARC modules if he/she has been authorized to access that module. Log-in and log-out buttons/functions are also included on the navigation bar.

  1. (SPARCDashboard) "Create New Project" button and function added


A "Create New Project" button was added on top of SPARCDashboard, to the right of the current "Create New Study" button, providing the user a way to create a project from the dashboard.

  1. (SPARCDashboard) Switch protocol type between study and project



From SPARCDashboard, users are now allowed to change type between study and project by clicking "Edit Study/Project Information" button. The previously filled out fields will transfer to the other type when the user chooses to switch between study and project; display to the project/study type is also updated in the user dashboard when the change is saved. (This function was previously only available in SPARCAdmin.)

  1. (SPARCDashboard) Switching tab bug fixed

In the Dashboard, users can now toggle back and forth between the "Message" tab and the "Show All Studies/Projects" tab.






  1. (SPARCDashboard) "Request In Progress" Fix


We have fixed the bug on SPARCDashboard for protocols showing as "Request in Progress", and not editable. It was caused by several different reasons, the most common one being when users quit editing a protocol by exiting out the browser without saving it. With this update, the users will not have that issue any more.

  1. (SPARCAdmin/SPARCDashboard) Switch the Primary PI role between users new feature

A new feature has been built to switch a primary PI on an existing protocol in SPARCAdmin and SPARCDashboard. When editing an authorized user listed or adding an authorized user, if "Primary PI" is chosen for the selected user while there is already an existing primary PI on the protocol, a "Change Primary PI" popup window will show up with a warning message showing which protocol and user names involved. If the user clicks "Yes", the primary PI will be switched to the chosen user and the current primary PI will be changed to a general access user; If the user clicks "No", then no change will be made.


Copyright © 2011-2026 MUSC Foundation for Research Development