Archiving moves content you are not actively working with out of the way, without deleting it. The asset stays in ioMoVo, stays findable, and comes back whenever you need it.
Why archive rather than delete
Most organizations end up with two kinds of content: the material in active use, and everything from finished projects that nobody wants to throw away. Deleting the second kind is uncomfortable, so it usually just sits in the working library making everything harder to search.
Archiving separates the two. Your day to day views get quieter, and nothing is lost.
Archiving a file
Archiving in bulk
For a finished project this is the one you want. Select the set and archive them together.
Bringing something back
Unarchiving returns an asset to the working library. Old projects have a way of becoming relevant again, so this is not an exceptional operation.
Archived content is still searchable
This is the part worth knowing, and the reason archiving is not a one way door. You can search archived content and filter to it, so material stays discoverable even when it is out of the way.
Making it a habit
The easiest moment to archive a project is the moment it finishes, while somebody still remembers what belongs to it. Left for later, it becomes an archaeology exercise nobody volunteers for.
Worth pairing with your portal review. When a project closes, archive its content and delete the portals that were sharing it.
In air gapped and on premise deployments
Archive is fully supported, including long term storage on LTO tape. If you have a retention requirement measured in years rather than months, that is a conversation worth having with your ioMoVo contact during planning.
Related
Monitoring and closing a portal covers the sharing side of closing down a project.