Open raindropsfromsky opened 3 years ago
There is another factor behind this suggestion: Qiqqa takes a very long time to OCR+Textify its file collection as a background process. When the laptop resources are not being used by any other software, Qiqqa resumes this background thread.
This means that Qiqqa may have done a substantial (OCR+Textification) work after the database was backed up last.
So, if we want to switch the database, then we must save the current work in OCR+Textification in the current database. Otherwise this hard-earned effort will be lost.
Conversely, when we switch back to this database, it must continue the OCR+Textify work from the point it had reached, and which was saved.
Is the facility provided by the "Tools" | "Qiqqa Configuration" | "System" | "Qiqqa data directory" sufficient to accomplish your request?
When we launch Qiqqa, it shows us a welcome screen that talks about backup+restoration of its database. If we press the "backup" button, Qiqqa names the file as QiqqaBackUp<currentDate+timeStamp>. qiqqa_backup
But there is no control to-
These facilities should be provided.
Further, when the user opts to start with a new database (or another existing database), he should be prompted to save (backup) the old one, or discard all changes since last saved.
This is useful, as the user may have multiple areas of interest, and each area should have a separate database, so that the user adds his files and web articles to the correct database. If each database contains files on only one single subject, the themes and autotags for each database will maintain their logical purity; and not contain mixed up subjects.