SPARCRequest Wiki

20230329-Technical Committee Meeting Minutes

Meeting:

SPARC OS Technical Committee

Meeting:

SPARC OS Technical Committee

Date:

03/29/2023

Time:

3:00 pm - 3:31 pm

MUSC

Greg, Brigette

Iowa

 

LA CaTS

 

Children’s National

 

Case Western

Jeremy

OHSU

Imogen, Erik

Stony Brook Medicine

 

Agenda:

Standup Round for institutional updates


Louisiana Clinical & Translational Science Center: 

3/15/2023

3/29/2023

  • SPARC v3.10.1 is live now.


MUSC:

3/29/23


Oregon Health & Science University:

3/15/23

  • Follow up on SPARCRequest ‘Your Cost’ field. OHSU would like to clarify data dictionary #5 for cost analysis report - why are there so many fields?

  • SPARCCatalog And SPARC Admin - service appears in program in UI after being moved to Core in Catalog - story updated to request OHSU putting in PR for their local coding that can MUSC review for potential application into SPARCRequest

    • split/notify - existing documentation doesn’t make it clear. Leila has concern about using “organization structure” the way OHSU has it setup be we’re not clear on why.

    • beef up split/notify documentation?

    • followup with Leila and Brigette about how to address this

  • Haven’t started upgrade but planning soon…

3/29/2023

  • Has SPARC v3.10.1 to dev environment to begin testing its application.

  • Still interested in Your Cost reporting, which will be considered.

  • (SPARCDashboard) Ability to Restore Modified Rates Back to Price on Pricing Map

    • Follow up from OS Ops call 3/17/23 is for Tech group to discuss dev approaches to accomplish this. Will be an ongoing discussion.

    • During Tech call Erik emailed Brigette their current script for routinely removing modified rates (admin_rates)

  • SPARCCatalog And SPARC Admin - service appears in program in UI after being moved to Core in Catalog

    • Instead of submitting a PR, will add coding info to story for consideration of its applicability within SPARC.

    • Looking to migrate mass amounts of catalog services between programs and cores. Is there a best practice, script, etc. to do this? Past issue experienced with this story would be resolved with their fix but want to make sure their plan for a rake task to do this is acceptable. MUSC usually makes archives services and enters as a new service, but Brigette will also check internally for other process and get back to OHSU.


Iowa

3/15/23

  • not in attendance

3/29/23

  • not in attendance


Case Western

3/15/23

  • Installed google analytics on SPARC

3/29/23

  • No new SPARC updates


Children’s National

3/15/23

  • not in attendance

3/29/23

  • not in attendance


Stony Brook:

3/15/23

  • not in attendance

3/29/23

  • not in attendance


Copyright © 2011-2019 MUSC Foundation for Research Development