Story #9587
Updated by Radhika Chippada almost 8 years ago
Use case: Provide a simple interface for users to review what collections are trashed, and undelete them if desired. Implementation: - Add a /trash index page "Trash" tab to the project view. It is based on the same table view that lists collections the "Data collections" tab uses, with is_trashed=true. - Display columns: checkbox, Name (with the following changes: * In place of the Trash button, there is an Undelete button. Use "fa-recycle":http://fontawesome.io/icon/recycle/ for this button. Clicking it updates the collection to set its @trash_at@ and @delete_at@ attributes to null, and wipes the collection from the Trash view. (The collection should now appear in the project's "Data collections" tab. If that doesn't happen correctly, file a link separate bug; fixing the way these tabs update should be done in a way that's effective for all of them, and is out of scope for this story.) * In place of the Description column, there is a column that shows the collection's delete_at time. Users can click the column header to object uuid), Trashed at (when sort the table based on this value. * The Selection menu does not have "Move selected" and "Remove selected" items. Instead, it was trashed at), Created at, Un-delete has "Undelete selected," which updates all the selected collections the same way the Undelete button would described above. - Selection drop down has one item We expect the Trash to "un-delete" include other kinds of objects besides collections in the selected items future. Because of this, do not put anything collection-specific in the checkbox - Search box - Infinite scrolling (rather than paging - desirable) interface. Do not add columns to the table that display attributes specific to collections; do not say "collections" in the Selection menu items; etc.