SPARCRequest Wiki

20240327-Technical Committee Meeting Minutes

Meeting:

SPARC OS Technical Committee

Meeting:

SPARC OS Technical Committee

Date:

Mar 27, 2024

Time:

2:00 pm - 2:54 pm

MUSC

Greg, Brigette

Iowa

 

LA CaTS

 

Children’s National

 

Case Western

Jeremy

OHSU

Imogen

Stony Brook Medicine

 

Morehouse

 

Guests

University of Florida - Sandra Smith, Chris Barnes

Agenda

 

Discussion:

  • (SPARCCatalog) Select active services to hide from SPARCRequest - revisit topic for service provider adding administrative, active services that are not displayed in catalog. Discussion included:

    • Difference between Available and Active.

      • Available services are those for adding to SPARC cart

      • Active would be these new admin services along with current services that are available in the cart

    • Current ‘Display in SPARC’ Catalog field indicates ‘is_available’ in DB and code, for what is considered active and appearing in SPARC.

    • Tags can be explored

    • Role based access to these new admin services is also a possibility, where they are viewable only in SPARC Dashboard (verses cart items viewable to all in SPARCRequest.

    • May be best to leave ‘is_available’ term and logic as is and add a new property or function to tie to these admin services. Could be an admin service property alone that is exposed in Dashboard. Noted that the services should have all routine service functions and display in reports, just not exposed for users to request services via SPARCRequest.

Institutional Updates:

 

Louisiana Clinical & Translational Science Center: 

2/28/2024

  • Upgraded to SPARC v3.12.1

  • Working on annual review due in May. Reaching out to investigators so they cite grant support

3/27/2024

  • not in attendance


MUSC:

2/28/2024

  • SPARCFulfillment release still underway as planned for March

  • SPARC Ruby & Ruby Rails upgrades simultaneous to Fulfillment - still planning for March 2024

  • SPARC Release will follow the Ruby/Rails upgrade

3/27/2024

  • SPARCFulfillment release work ongoing

  • SPARC Ruby & Ruby Rails upgrades simultaneous to Fulfillment work ongoing

  • SPARC Release will follow the Ruby/Rails upgrade


Oregon Health & Science University:

2/28/2024

  • SPARC upgrade done

  • Will revisit their use of surveys/forms, considering their current SPARC users being admins vs research teams with the new SPARCForms authorized user group notification design (survey is live; forms will be implemented with next SPARC release).

3/27/2024

  • No SPARC updates


Iowa

2/28/2024

  • not in attendance

3/27/2024

  • not in attendance


Case Western

2/28/2024

  • Based on LACaTS model and discussions, implemented ‘cite the grant’ agreement as pop up when requests are submitted, and as text within recipient emails. Clicking the agreement button does not save the data. Will add PT story for this to be considered for SPARC implementation.

3/27/2024

  • April goal to upgrade server to RedHat Linux 8. Are also doing some SPARC Catalog service changes (moving among programs/cores, updating names, descriptions, etc.) and asked about any existing coding or experience for doing this. Imogen and Brigette recalled this being an action that had to be carefully planned per scenario, but there is no general code or script that does all this. They will look at past notes to share. SPARC does have provisions to change services between Programs and Cores, so Jeremey can explore that function as well.


Children’s National

2/28/2024

  • not in attendance

3/27/2024

  • not in attendance


Stony Brook:

2/28/2024

  • not in attendance

3/27/2024

  • not in attendance


Morehouse:

2/28/2024

  • not in attendance

3/27/2024

  • not in attendance

Copyright © 2011-2019 MUSC Foundation for Research Development