[Feature Request] Make export accessible by wrapping manifest.json into a js file and adding a html document containing a static single-html document version of paperless that allows to access the documents metadata

[spaceChRiS]

Description

I can imagine that a lot of people are running paperless-ngx for their private documents. Typically, in such a scenario there's no 2nd server running in parallel which can takeover operations when the main server fails. Furthermore, the local network is often not remotely accessible due to CGNAT. At least it's the case for me.

Therefore, I think it would be a great feature to make the backup more accessible in case of error or as a mobile copy that can run without server. manifest.json holds all metadata anyway and would therefore allow tag filtering and text search. Wrapped in a js file would circumvent CORS restrictions with loading the metadata from a local html document. Eventually, displaying documents would not be possible, but links to the local documents would be sufficient in case of emergency. I would still be able to find all tax-related documents by tag in case the server fails the day before declaration deadline.

From my experience, manifest.json is about 150 MB per 10000 documents (zipped only ~20 MB), which seams manageable by modern computers, but for larger document stores, it might be beneficial to control the documents to be in the accessible part of the backup by a tag, such that archival-only documents are ignored in the js wrapper of manifest.json. Another option would be to split the metadata .js files by storage location to keep the per-file content low. With this, only one location would be searchable at a time, which would be sufficient for some use cases though.

The html document could be generic as all data could be read from manifest.json.js.

Maybe, something similar was already implemented and I did not notice? At least I was not able to find something here in the discussions or in the issues. I'd be thankful for any hint 😃. Thanks for reading anyway, was a long text already.

Other

No response