Duke-GCB / Duke-GCB/bespin-api
Record result delivery state in job
Open
- Dominant language
- Python
- Stars
- 0
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Tracking/handling of result datasets after jobs run is now managed outside of Bespin. It relies on ddsclient and the D4S2 delivery workflow.
This means that from Bespin, users can only see that projects are completed. We should discuss how to track the result datasets in bespin and integrate that into the delivery workflow.
Some suggestions:
- Add states to the job to indicate the review process: **In Review**, **Delivered**, **Action Required**?
- On delivery, update the `JobOutputDir` model with the delivered project ID so that we can display that to users the UI.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.