[Feature request]: Archiving assets and other database entries
Contact Details
Is your feature request related to a problem? Please describe?
I think it would good to implement archiving for assets and other database entries asap. Not the most exciting feature but an important foundation for upcoming features like Reports and not losing data in general.
Describe the solution you'd like
Option to 'Archive' assets from asset page and straight from index
Option to filter index on archived entries. We need to rework dropdown components first: https://github.com/Shelf-nu/shelf.nu/issues/215
Describe alternatives you've considered
No response
Additional context
No response
Very nice @jurrejansen can you provide the impact of this new feature for indexes, mobile, etc so we can make a bounty out of this?
@carlosvirreira wasn't completely done with the issue, added more stuff. We're also still blocked by https://github.com/Shelf-nu/shelf.nu/issues/215
I've also done a re-iteration of the asset index in general
https://www.figma.com/file/8RjvxGnNySRCYsgpSrK0M4/Shelf-App-%7C-Library?type=design&node-id=6434-27458&mode=design
I'm not sure if 'Archived' should be included in the 'Status' filter as you opted for the 'Status' filter to be in same hierarchy as the other filters. Another reason I've found to not do this is for other indexes e.g. Team members. There 'Status' filter would only have to show something in the likes of 'Active' and 'Archived'
Maybe it would be good to separate the 'Archived' status from asset statuses like 'Available', 'In custody', etc. and just do a filter that is global for all indexes so we can manage 'Active' and 'Archived' entries for all indexes like that.
For asset index it'll look like this in my head:
For e.g. Team members index (and other indexes) it'll look something like this:
@carlosvirreira @DonKoko Would be good to do this. Bounty? I guess it's more straightforward now we have the filter for states + reworked dropdown?
SCENARIO: https://www.figma.com/file/ykvc0MhPeNLsrJ4tJsKosQ/Shelf-%7C-UX-Scenarios?type=design&node-id=108-88431&mode=design
Thank you for the design @jurrejansen
have you considered how this interacts with other areas like bookings? For complete / archived bookings I guess we show the asset but show a tag that it has been archived?
Hmm yeah, good to get the conditions straight. Asset will indeed have the Archived badge showing that their status is now Archived and not Available.
Conditions for Archived assets:
- They do now show in asset index unless filtered on Archived
- They cannot be added to bookings (even if filters on Show all)
- They cannot be assigned custody
- Assets with In custody or Checked out status cannot be Archived
I think editing metadata like category, tags, description, etc. while asset is Archived is fine.
Anything else? Can't think of anything atm
Hmm yeah, good to get the conditions straight. Asset will indeed have the Archived badge showing that their status is now Archived and not Available.
Conditions for Archived assets:
- They do now show in asset index unless filtered on Archived
- They cannot be added to bookings (even if filters on Show all)
- They cannot be assigned custody
- Assets with In custody or Checked out status cannot be Archived
I think editing metadata like category, tags, description, etc. while asset is Archived is fine.
Anything else? Can't think of anything atm
Something I can think of is - can you un-archive? What happens then?
UNARCHIVING ASSET https://www.figma.com/file/ykvc0MhPeNLsrJ4tJsKosQ/Shelf-%7C-UX-Scenarios?type=design&node-id=4743-107304&mode=design
- Status will be Available again
- Can be used in bookings again
- Can be assigned custody again