20230315-Technical Committee Meeting Minutes

Agenda:

Standup Round for institutional updates

Louisiana Clinical & Translational Science Center: 

3/1/23

• Not in attendance

3/15/2023

• Ying reported (SPARCRequest, SPARCDashboard) Documents - Bulk Download and Edit Bugs and put in PR for the fix. Story updated to note MUSC also seeing the error as a non-administrative user.

• Had to install wkhtmltopdf package on server because clicking individual document links was throwing error

• When will MUSC update to rails 6?

MUSC:

3/15/23

• 3.4.0 SPARC Fulfillment stories as the next major release.

  • New story additions & development ends 3/24/23

  • Release Date 4/6/23

• Institutions can continue providing their customized report data on the PT story (SPARCReport) OS Community Customized Reports. MUSC will compile all info and release in the WIKI.

• Stories for SPARCRelease 3.11.0 is currently being planned (no date yet).

Oregon Health & Science University:

3/1/23

• Imogen asked if there are any existing reports that use SPARCRequest ‘Your Cost’ field. They are looking to add it into a custom report and were hoping it’s already been done and not as a calculated field. Brigette will get back to them on these details.

  • clarify data dictionary for cost analysis report

• SPARCCatalog And SPARC Admin - service appears in program in UI after being moved to Core in Catalog - checking on status of the code being promoted for SPARC. They have already implemented locally. Brigette reported it’s something Andrew will have to look at. He will be reminded of the updated story details.

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…

Iowa

3/1/23

• not in attendance

3/15/23

• not in attendance

Case Western

3/1/23

• Submitted PT story details of their customized reports

3/15/23

• Installed google analytics on SPARC

Children’s National

3/1/23

• not in attendance

3/15/23

• not in attendance

Stony Brook:

3/1/23

• not in attendance

3/15/23

• not in attendance