Discuss our approach to managing CET run storage and planning for future growth.
Key points to consider:
Current approach: All CET runs (inputs and outputs) are currently stored indefinitely.
Problem: This leads to increasing storage demands.
Discussion points:
Should we remove test runs after a certain period?
Partial deletion:
Should we keep inputs only and delete outputs after a period?
Note: CET versions change, which may make old inputs unusable for reruns or audits.
Should we apply retention policies only to community users while keeping full data for PAs?
Position on file storage:
Reinforce that users are expected to track and store files internally.
CET is not intended to act as a long-term file repository.
Please authenticate to join the conversation.
In Review
Feedback
9 months ago

cedars team
Get notified by email when there are changes.
In Review
Feedback
9 months ago

cedars team
Get notified by email when there are changes.