SPARCRequest Wiki

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Meeting:

SPARC OS Technical Committee

Date:

Time:

2:00 pm EST

MUSC

Iowa

LA CaTS

Children’s National

Case Western

OHSU

Stony Brook Medicine

Morehouse

Agenda:

Standup Round for institutional updates


Louisiana Clinical & Translational Science Center: 

11/22/2023

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.


MUSC:

11/22/2023

  • Next major release SPARC v3.12.0 - dev work Nov 30th; deployment Dec 14th

  • SPARCFulfillment - Late Winter 2024

12/6/2023

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

  • SPARCFulfillment - Late Winter 2024


Oregon Health & Science University:

11/22/2023

  • External Orgs Reporting - Do we want to add a column to protocols report (concatenate if more than one) or have separate report.

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.


Iowa

11/22/2023

  • not in attendance

12/6/2023

  • not in attendance


Case Western

11/22/2023

  • not in attendance

12/6/2023

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


Children’s National

11/22/2023

  • not in attendance

12/6/2023

  • not in attendance


Stony Brook:

11/22/2023

  • not in attendance

12/6/2023

  • not in attendance


Morehouse:

11/22/2023

  • not in attendance

12/6/2023

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


Discussion:

  • SPARC Release 3.12.0 Review

    • Highlight RMID-IRB data API work done with the release

  • Potentially making SPARC (drop down) labels configurable by allowing edits to values and leaving the key non-editable since key is used in code.

  • No labels