Discussion:

• No planned discussion items; see MUSC update section

Institutional Updates:

Louisiana Clinical & Translational Science Center: 

12/6/2023

• Met with Jeremy (Case) to demo MOU feature in SPARC. This may be revisited as a potential SPARC feature at the next OS Governance call.

1/17/2024

• not in attendance

MUSC:

12/6/2023

• Next major release SPARC v3.12.0 - finishing stories for deployment Dec 14th

• SPARCFulfillment - Late Winter 2024

1/17/2024

• Released SPARC v3.12.0 (Dec 14th) and v3.12.1 (Jan 10th). Both releases available to OS Community - see blog

• Working on SPARCFulfillment planned deployment March 21st.

• SPARC Ruby & Ruby Rails upgrades happening as Fulfillment work being done.

• OS Governance Dec 1th meeting reviewed MOU demo and is ok with including as a SPARC, customizable feature. Next step is a story describing the work.

Oregon Health & Science University:

12/6/2023

• Planning for SPARC v3.11.0 upgrade, following updates to their (RMID as) IRB# API configuration.

• They may explore using SPARC surveys, but will review needs since their recipients may be different than current survey programming.

1/17/2024

• Working on upgrade

Iowa

12/6/2023

• not in attendance

1/17/2024

• not in attendance

Case Western

12/6/2023

• Worked through the RedHat downgrade issue and continuing with upgrading servers and will test SPARC upgrade to 3.11.0.

1/17/2024

• Still working toward upgrading to SPARC 3.11.0. Current issue is that ldap isnt going to their institutional login page. Andrew was able to join to give some guidance that ldap is used for adding user to studies, not to present a login page He gave some code base location Jeremy should look at:

  • config/initializers/devise.rb, line 41

  • They may need to use GitHub - omniauth/omniauth-ldap: LDAP strategy for OmniAuth gem for authentication.

  • config/cas.yml file is a part of code base and a part of v3.11. This is a config file to read db so no need to add to settings.

• Asked if giving access to Reports allows users to run reports on all SPARC services or only those they can access. His testing showed global access. This should limit to only what they can access, so he’ll check permissions for other access like Super User or Overlord rights. Brigette will do some testing as well to confirm behavior.

  • Post meeting, testing shows SPARC design where being a super user at any Org level lets you have access to SPARCReports with ability to run reports for all. Worth a discussion to see if this should be limited, similarly to how SPARCForms limits to surveys and forms particular to orgs/services.

Children’s National

12/6/2023

• not in attendance

1/17/2024

• not in attendance

Stony Brook:

12/6/2023

• not in attendance

1/17/2024

• not in attendance

Morehouse:

12/6/2023

• On hold with SPARC full roll out so haven’t much work with SPARC.

1/17/2024

• They are picking SPARC back up for implementation and will reach out with any questions.