...
Implemented the delayed email fix discussed with MUSC and jobs have been running successfully so far.
Working to have clean data in dev site with goal to copy database over and use in production to avoid rebuilds. Discussed it may be best to export tables you want vs the whole database. It will be a manual process but may get the best dataset and be an easier clean up. Can reach out to MUSC to take a look when they are at this clean-up point.
Asked how to contribute Stonybrook’s feedback into PT stories. Andrew described the process of adding their name to the task (with priority ranking in parentheses) and then checking the box after saving. Can also include comments within the story. Send new story ideas to MUSC, where it can be reviewed, discussed in Operations governance and story entered for prioritization. Brigette also shared there are SOPs being drafted describing some of these processes that will be shared when finalized.
08/17/22
Working on testing data copied from dev server to the test server before moving to production. Sent database for MUSC to look at as advisement. Andrew will take a look at it.
Confirmed if service providers can delete services. They cannot do this, but services can be hidden from appearing in SPARC.
...
Update:
Status of PT story SPARCRequest Step 2 and SPARCDashboard: Add Associated Organizations on Protocol Information Form - is OHSU interest in working on this one? recorded in OHSU’s Standup Round section.
MUSC SPARC team email sparcrequest@musc.edu. Also included on the OS Wiki page https://sparcrequest.atlassian.net/l/cp/WPoAaKP3.
Began MUSC began looking in using MSTeams for group communication
Discussion:
, per previous meeting inquiries.
Action Items:
Confirmed requirements for story SPARCRequest Step 2 and SPARCDashboard: Add Associated Organizations on Protocol Information Form
Review Stonybrook’s database for recommendations
Explore options to use MSTeams for group communication.