New Release: SPARCRequest Version 3.0.0b & SPARCFulfillment Version 2.6.5

Dear SPARC OS Community,

We have tagged the latest releases of SPARCRequest(v3.0.0b) and SPARCFulfillment(v2.6.5) on GitHub. Please feel free to reach out to us if you have any questions.

Check out the link below for the new features and bug fixes included with the new release!

171024-SPARCRequest v3.0.0b +SPARCFulfillment v2.6.5

List of rake tasks and configuration changes with this release:

(SPARCRequest)

  1. use_cas: false
  2. use_cas_only: false
  3. lazy_load_ldap: true
  4. .env needs: org_logo=/assets/sctr_header_sized.jpg
  5. .env needs: institution_logo=/assets/musc_header.jpg
  6. .env needs: institution=….
  7. .env needs: SPARC_VERSION=v3.0.0
  8. bundle exec rake import_permissible_values
  9. bundle exec rake data:restore_service_requester_id (optional, for recovering service requester data that were missing caused by a bug, see #8 on the release note)

(SPARCFulfillment)

  1. ENVIRONMENT=testing
  2. TESTING_EMAIL=…@…

 

For more information, please contact:

Email: sparcrequest@gmail.com

-The SPARC Team

2017.10.31.

New Release: SPARCRequest Version 3.0.0a & SPARCFulfillment Version 2.6.0

Dear SPARC OS Community,

We have tagged the latest releases of SPARCRequest(v3.0.0a) and SPARCFulfillment(v2.6.0) on GitHub. Please feel free to reach out to us if you have any questions.

Check out the link below for the new features and bug fixes included with the new release!

170829-SPARCRequest v3.0.0a +SPARCFulfillment v2.6.0

There are no rake tasks or configuration changes with this release.
For more information, please contact:

Email: sparcrequest@gmail.com

-The SPARC Team

2017.09.13.

Invoice Report Data Dictionary -SPARCFulfillment (Version 2.5.5)

Dear SPARC OS Community,

As an effort to facilitate better understanding of the definition of the system-generated canned reports and continuously improving them, we have been working on the data dictionary of each report. The data dictionary documents include the definition of each column/data field as well as its source record and backend information.

As the second of the series of documents, please click here for the Data Dictionary of the Invoice Report based on the current version of SPARCFulfillment (version 2.5.5), which can be generated on SPARCFulfillment “All Reports” tab.

Screen Shot 2017-07-24 at 11.30.09 AM.png

Below is an example of the SPARCFulfillment Invoice Report for your information:

Screen Shot 2017-07-24 at 11.34.24 AM.png

 

Please contact us if you have any feedback about the report or the data dictionary document.

Have a great day!

Email: sparcrequest@gmail.com

-The SPARC Team

2017.07.24.

Milestone: 2017 SPARCRequest Open Source Governance Retreat

Dear SPARC OS Community,

We are proud to announce that MUSC hosted the 1st annual SPARCRequest Open Source Governance Retreat on June 19th to 21st, 2017, with 4 CTSA Hubs (Iowa, Utah, Children’s National, MUSC) and 1 IDeA State CTR Hub (LA CaTS) participated, which represent 20 institutions.

The national SPARCRequest Open Source Governance is comprised of Steering Subcommittee, Technical Subcommittee, Operational Logistics Subcommittee, as well as an Evaluation Team. MUSC, Iowa and Utah were awarded a CTSA Grant Administrative Supplement Award to support the development of this governance structure that will support sustainability, co-development and institutional adoption of SPARCRequest. The Administrative Supplement is a 2 year award from NCATS with a total award of $853,998. This is an exciting opportunity for us to expand SPARC to other CTSA Hubs and the IDeA State CTR Hubs and to explore options to support the national CTSA Trial Innovation Network.

The highlights of this 2017 retreat includes:

  1. Agreement on branding and promotion of SPARCRequest. The OS governance group defined  SPARCRequest as a “Research Transaction Management System” for clarifying its functionality and branding;
  2. Experience and lessons learnt through the SPARC implementation process were shared among institutions;
  3. Each institution demonstrated their site-specified customization during the retreat;
  4. Prioritization of the SPARC OS project task list was discussed;
  5. Technical team members worked collaboratively during the Code-A-Thon to initiate the clean code base and convert the configuration and constants settings in the application into database (and eventually through user interface) to make the adoption/deployments easier.

b55fa455-a6e2-48ec-a39c-9406f81e7c9d.jpg

We are looking forward to the future collaborations with our OS partners for further improvement to SPARCRequest!

-The SPARC Team

2017.7.

 

New Release: SPARCRequest Version 2.1.0 & SPARCFulfillment Version 2.5.5

Dear SPARC OS Community,

We have tagged the new releases of SPARCRequest(v2.1.0) and SPARCFulfillment(v2.5.5) on GitHub. Please feel free to reach out to us if you have any questions.

Check out the link below for the new features and bug fixes included with the new release! The feature highlights in the new versions include Freezing Header Rows on Visit Calendars on SPARCRequest and SPARCDashboard (see SPARCRequest #10), Coverage Analysis Report on SPARCDashboard (see SR #27), and Participant List and Participant Tracker tabs merge with SPARCFulfillment (see SPARCFulfillment #4), etc.

170712-SPARCRequest v2.1.0 +SPARCFulfillment v2.5.5

Below is a list of the rake tasks and configuration changes that needs to be done with this release:

(SPARCRequest)

1). bundle exec rake study_type_question_3_fix  

2). bundle exec rake merge_srs 

3). bundle exec rake fix_ssr_ids

(SPARCFulfillment)

1). USE_INDIRECT_COST=false (needs added to .env)
For more information, please contact:

Email: sparcrequest@gmail.com

-The SPARC Team

2017.07.12.

SPARCFulfillment (Version 2.5.0) Visit Report Data Dictionary

Dear SPARC Open Source Community,

As an effort to facilitate better understanding of the definition of the system-generated canned reports and continuously improving them, we have been working on the data dictionary of each report. The data dictionary documents include the definition of each column/data field as well as its source record and backend information.

As the first of the series of documents, please click here for the Data Dictionary of the Visit Report based on the current version of SPARCFulfillment (version 2.5.0), which can be generated on SPARCFulfillment “All Reports” tab.

Screen Shot 2017-06-08 at 9.39.46 AM

And this is an example of the generated visit report for your information:

Screen Shot 2017-06-08 at 9.47.32 AM

The data dictionary for the other reports will be published shortly afterwards. Please contact us if you have any feedback about this report or data dictionary document.

Have a great day!

Email: sparcrequest@gmail.com

-The SPARC Team

2017.06.08.

New Release: SPARCRequest Version 2.0.5 & SPARCFulfillment Version 2.5.0

Dear SPARC OS Community,

We have tagged the new releases of SPARCRequest(v2.0.5) and SPARCFulfillment(v2.5.0) on the MUSC branch on GitHub, as well as the OS branch. Please feel free to reach out to us if you have any questions.

Check out the link below for the new features and bug fixes included with the new release!

170509-SPARCRequest v2.0.5+SPARCFulfillment v2.5.0

Below is a list of the rake tasks and configuration changes that needs to be done with this release:

(SPARCRequest)

1). Bundle exec rake data:update_protocol_filters

2). Add sparc-rails_backup database entry to database.yml

3). Bundle exec rake data:fix_notes_with_wrong_dates (for fixing the wrong note dates from a past migration on 6/20/2016, using notes data from a backup version)

4).Application.yml change:
set up site_admins
and update users for epic_queue_access

5). Application.yml change:
set up redcap_token for the SPARC/RedCap API

(SPARCFulfillment)

6). Bundle exec rake data:replace_arm_name_special_characters

 

For more information, please contact:

Email: sparcrequest@gmail.com

-The SPARC Team

2017.05.18.

SPARC Open Source Operations/Logistics Subcommittee

Hi Open Source Community,

The University of Iowa has accepted the lead institution role in running the Operations/Logistics subcommittee for SPARC Open Source Governance. In this role, Iowa is in charge of ensuring the flow of communication between each subcommittee and participating institutions. In an effort to reach the sites currently using SPARC, and continue to add members to our Operations Committee (one call each month), we ask that those institutions using SPARC join our committee to help shape the way it is used in the future.

The overarching goal is to first transition SPARC to an open source application that offers each institution an opportunity to provide input toward improving functionality and even voicing new ideas. Each institution may understandably utilize SPARC in different ways, so the operations committee will work to identify key areas for improvement. The perceived success of implemented changes to SPARC will be based on feedback from each institution, which is the reason we hope to collaborate with everyone interested in participating on the monthly call. This will help to provide better direction for achieving desirable milestones.

As you may recall, in late 2016 there was a transition from MUSC hosting a monthly update call, to now having an Open Source Governance Committee platform. The committee is compiled of three subcommittees that include a Steering, Operations/Logistics, and Technical subcommittee. There is currently representation (pertaining to future development and sustainability) from MUSC, Iowa, Utah, LA CaTS, and VCU on all three of the subcommittees. The immediate goal is to better understand how each institution uses SPARC, to provide infrastructure and resources for SPARC,  as well as to weigh/discuss pros and cons experienced at each site to enhance future functionalities.

Thanks,

-SPARCRequest OS Committee

Blog at WordPress.com.

Up ↑