We've had issues arise in the current version of Jaded, and unfortunately users have not backed up often enough, resulting in all their work to become lost.
Especially during this period of tidying, it will be worth automating this process just to reduce the chance of data-loss.
Given right now the BF is just a big fat blob of data, we'll just create one active back-up of the BF that we'll update every so often.
User Story
Again, users that are working heavily with the editor and don't have time to consider backing up the BF during their work.
Acceptance Criteria
[ ] BF is automatically backed up at a fixed interval to a secondary 'back-up' BF
[ ] Allow, if possible, the back-up interval to be configured via the UI
[ ] Provide an option to force a back-up if desired?
Mockups or Wireframes
N/A
Dependencies
N/A
Risks or Challenges
When we introduce the new I/O solution for the editor, much of this will probably need to be revised...
Summary
We've had issues arise in the current version of Jaded, and unfortunately users have not backed up often enough, resulting in all their work to become lost.
Especially during this period of tidying, it will be worth automating this process just to reduce the chance of data-loss.
Given right now the BF is just a big fat blob of data, we'll just create one active back-up of the BF that we'll update every so often.
User Story
Again, users that are working heavily with the editor and don't have time to consider backing up the BF during their work.
Acceptance Criteria
Mockups or Wireframes
N/A
Dependencies
N/A
Risks or Challenges
When we introduce the new I/O solution for the editor, much of this will probably need to be revised...