20230104-Technical Committee Meeting Minutes

Agenda:

Standup Round for institutional updates

Louisiana Clinical & Translational Science Center: 

12/21/22

• Three stories and three pull requests from Ying:

  • Diplay Involved External Organizations only if use_eeeexternal_organi… by ying-pbrc · Pull Request #3057 · sparc-request/sparc-request

  • Unable to change funding status from 'Not Funded' to others bug fix by ying-pbrc · Pull Request #3056 · sparc-request/sparc-request

  • Fixing undefined method for NilClass bug- sparc settings by ying-pbrc · Pull Request #3054 · sparc-request/sparc-request

• New story from Brian:

  • https://www.pivotaltracker.com/story/show/184082536

• What is eta for 3.10.0? ..and for 3.10.1?

1/4/23

• Not in attendance

MUSC:

1/4/23

• Working on SPARC Release 3.10.1 mini release - see current stories. Release date 1/26/23

• 3.4.0 SPARC Fulfillment stories as the next major release. Release date TBD.

Oregon Health & Science University:

12/21/22

• not on this week

1/4/23

• Will hold their upgrade until 3.10.1 is released.

• Followed up on SPARCCatalog And SPARC Admin - service appears in program in UI after being moved to Core in Catalog. MUSC will update story with previous MUSC-OHSU meeting info and ping Andrew for guidance on OHSU removing the services incorrectly appearing in program.

• Still exploring a Jira and SPARC API to track fulfillment.

• Interested in OS reports sharing and enhancements, including OHSU story of interest (SPARCReport) Add Optional Services Column On Service Requests Report

Iowa

12/21/22

• not on this week

1/4/23

• not on this week

Case Western

12/21/22

• not on this week

1/4/23

• SPARC is still running well for them.

• Working on SSL cert and dev server updates

Children’s National

12/21/22

• not on this week

1/4/23

• not on this week

Stony Brook:

12/21/22

• not on this week

1/4/23

• not on this week

Discussion

• In line with OS Operations discussions, MUSC will be requesting OS members customized reports data dictionary and summaries. This is a first step in gathering these details to share with the OS community. Technical reps should also consider any other data points that would be helpful to share.

• Members encouraged to consider previous Tech call format and data exchange, as well as new desirable information sharing topics to optimize these meeting.