[Feature request] Add "archive/hide" flag to hide documents from search

Hi again, sorry for writing issues like on steroids.

I'm importing a lot of documents from my NAS and paperless-ng to docspell. Many documents are rather old and only archived, because I'm a digital native "messy" :-D. Anyway, I guess many users will have collected a lot of documents over time. But many documents become less relevant over time, without you then want to delete them. You could argue that documents will eventually disappear from the search list anyway due to the basic sorting, but if you search for certain document types or classifications, old documents will reappear.

I would be happy if you add an archive flag (bool) for this. I know you can also do this with Custom Fields, but they would be missing a feature that would still be important: An "archive flag" should work like the Trash flag in searches. If "archive" is not selected, we get only the "young" documents (not flagged). When the Archive checkbox is selected, the archived documents should be searchable.

Example in search:

^- as alternative: "Include archived items in search" - in this case the search will run over all items in the DB (excluding Trash)

Example in edit:


^- proposal, maybe a "Folder" icon, and toggle state between "Archive / Un-Archive"

Why this workflow may make sense?

Many documents have different dates when they are no longer relevant for daily use. Receipts are relevant for 6 months if you want to keep track of the legal warranty. Tax documents are to be kept for 10 to 15 years, but I would be interested in finding them in my search now for 1-2 years at most. Terminated contracts can then be archived immediately.

I don't always want to see all of these documents together in my full text search. But that happens because they simply have different time relevance (from a few weeks to several years).

A Custom Field would not be considered automatically (unlike Inbox or Trash) in the searches. In addition, the Custom Filed must first be added and then selected in each document, and you would always have to create bookmark queries for it.

I know that is a customization to the DB schema and always requires special consideration and thinking if the effort is worth it, but personally I think that just such a small field can clearly help to keep overview in the document clutter.