[EPIC] Data Ingestion

[tclose]

Instructions

Hypothesis Statement

• Funnel Entry Date: The date that the epic entered the funnel
• Epic Name: A short name for the epic, should be the same as issue title
• Epic Owner: The name of the epic owner

Description

An elevator pitch (value statement) that describes the epic in a clear and concise way

For *customers*
who *do something*
the *solution*
is a *something – the ‘how’*
that *provides this value*
unlike *competitor, current solution or non-existing solution*
our solution *does something better — the ‘why’*

Outcomes

The measurable benefits that the business can anticipate if the epic hypothesis is proven to be correct

Leading Indicators

The early measures that will help predict the business outcome hypothesis.
For more on this topic, see the Innovation Accounting advanced topic article

Nonfunctional Requirements

Nonfunctional requirements (NFRs) associated with the epic

Features

• [ ]

[github-actions]

Features

• [FEATURE] Total Body PET data ingestion #273

[github-actions]

Stories

• [STORY] TBP staging server: automatically restore k8s after reboot #272
• [STORY] GH action to build XNAT-ingest #275
• [STORY] Configure XNAT-ingest workflow from TBP to AIS #278
• [STORY] Failure of TBP DICOM node (presumed after patch restart) #279
• [STORY] Configure USyd AIS k8s node to run "xnat-ingest" upload for TBP #284
• [STORY] Add support to logging via API to xnat-ingest commands #285
• [STORY] Test for presence of manifest file in upload stage of xnat-ingest #286
• [STORY] Loosen NFS permissions on TBP staging server dev VM #289
• [STORY] Monitoring of staging server processes #305
• [STORY] Complete staging server startup script - Ubuntu #306
• [STORY] Complete staging server startup script - Windows #307
• [STORY] Look into issue with large upload failures (>60GB) #310
• [STORY] Investigate S3 storage solutions #309