Idea #9582
Updated by Brett Smith almost 8 years ago
Functional requirements: The only place Workbench should list expiring show the user expired collections (collections where the @expires_at@ @expired_at@ field is not null) for the user is in the trash view, where the user may undelete them by clearing their expiry. In any other listing, expiring collections view, an expired collection should not be shown. This can be accomplished by listing collections with the filter @["expires_at", "=", null]@. Filter expiring expired collections out of the following listings: * "Recent collections" on the Dashboard * The "Data collections" tab of projects * The "disambiguation" page you get when you go to a page for a collection's portable data hash, and more than one collection has that hash * Input choosers for Collections and Files * Provenance graphs (if you know the collection's portable data hash, you can still render an entry for that portable data hash in the graph, but you must ensure that the graph does not show any details of an expiring collection (e.g., its UUID), or link to it) * Work unit outputs and logs in their overview pane * Work unit logs in the Log tab If you find other listings in the course of working on this branch, do go ahead and exclude them from there as well. We do need to be able to list and show expiring expired collections to support trash view. The implementation should not make that unreasonably difficult. For example, the @Collection#list@ method should not always add the suggested filter.