[Feature] Import/export LocalDocs data

[glocalglocal]

trafficstars

Feature Request

It would be good to be able to export/import LocalDocs data.

It takes my slow machine weeks working 24/7 to process a number of articles and ebooks. When I replace my device, I would want to migrate my GPT4All setup rather than start all over again. Ideally, we would be able to append LocalDocs data to a new or existing GPT4All setup on another machine.

That would also allow us to use temporarily a fast machine to do the processing and then to migrate the data to a slower machine for working with.

[SINAPSA-IC]

I second that. It is all files - the localdocs database with embeddings, the files in collections, the paths to the corresponding folders. They could easily be copied-migrated, and once in the new destination the User would have (be given) the option to link the program there to that new location, and reindex the files, if case may be; Backup LocalDocs From Folder(s)... and if those folders of old collections do not exist in the new location, that is if the program found nothing or only some of those folders, then it does nothing or displays a message (the latter would be something new indeed).

[Doug-K-DeBow]

Or if the localdocs collection points to a shared drive between multiple machines, it would be beneficial to complete the embedding on one machine then export and import the embedding to other machines. If there are 20 machines connected to a mapped drive, it can be a dealbreaker to have to repeat the indexing and embedding 20 times.