search

NOAA-OWP / wres

Code and scripts for the Water Resources Evaluation Service
Other
2 stars 1 forks source link

As a developer, I want the algorithm applied to remove posted data to be more intelligent in selecting which data to remove #155

Open epag opened 2 months ago

epag commented 2 months ago

Author Name: Hank (Hank) Original Redmine Issue: 124775, https://vlab.noaa.gov/redmine/issues/124775 Original Date: 2024-01-04

As an example, data that is marked as being kept should be removed after data that not marked as being kept (i.e., data not removed because the evaluation failed). There may be other priorities that can be applied as well; for example, perhaps evaluation outputs are removed instead of kept input.

This ticket can be resolved once we identify the improvements to put in place, implement the change, and test it.

Hank

epag commented 2 months ago

Original Redmine Comment Author Name: James (James) Original Date: 2024-01-04T18:25:22Z

Just to add my 2c that we should aim for something minimally complicated that captures the additional user-declared priority/longevity attached to a dataset, but not try to implement our acceptable use policy in code, which is much more subjective/comprehensive and designed to guard against idiocy in the round. In short, we rely on users to behave well and that will always be true, so we need more emphasis on the terms of acceptable use, rather than over-complicating the guards we have in code to protect the service.