File metadata: finding documents without remembering where they are
File metadata is the third way to find things, after names and folders. Which fields earn their place, who fills them in, and why most tagging schemes collapse.
Document archiving separates what you must keep from what you work with daily. How to decide what moves, what the archive must guarantee, and why deletion is part of it.
Document archiving is the deliberate move of material out of daily working storage into somewhere it stays findable but stops getting in the way. It is not backup, which protects against loss, and it is not deletion, which is the end of the line. Confusing the three is why so many organisations hold everything forever: nobody is sure which of the three they are doing, so they do none of them.
The trigger should be an event rather than a date where possible: a project closes, a contract expires, an employee leaves, a case concludes. Event-based archiving matches how people think and produces a complete set; time-based archiving produces a slice of whatever happened to be open that quarter. Where a date is the only available trigger, pair it with a completeness check — the question is not "what is old" but "is everything from that matter here".
Archive the context, not just the files. A folder of documents with no index, no dates and no record of who was involved is technically retained and practically useless. One summary page per archived matter costs ten minutes and is what makes the archive answerable.
Keeping everything indefinitely feels safe and is not. It raises the cost of every future search, enlarges the blast radius of any breach, and in a dispute hands the other side material you had no obligation to keep. The organisations that handle this well are not the ones with the biggest archives; they are the ones that can say what they hold, why, and until when.
Ettex Storage suits the archive side directly: folders by matter with a retention date and basis recorded per item, restricted access with an exportable log, and a summary page sitting alongside the files. The schedule itself belongs next to it as a records retention schedule rather than in somebody's memory.
No. A backup is a copy for recovery and is overwritten on a cycle; an archive is the authoritative retained version, kept deliberately for a defined period.
By category and by the basis for keeping them — statutory minimums, contractual terms, then business need. A single retention period for everything is always wrong in one direction or the other.
Deletion stops immediately for anything within scope, and the hold is recorded. Routine schedules must not quietly delete material somebody has asked you to preserve.
File metadata is the third way to find things, after names and folders. Which fields earn their place, who fills them in, and why most tagging schemes collapse.
A storage quota forces a decision most teams avoid. What actually consumes the space, how to clear it without deleting anything important, and when buying more is the right answer.
File recovery depends on decisions made before the loss: version history, how long deleted items are kept, and whether anybody has tested a restore. What to check now.