There are some books of particular interest. Either because we need them to analyze a bug, or they showcase an important milestone, etc ...
These backup books must continue to live no matter what happens to them due to the regular CMS lifecycle. We need for instance to backup a book which is in staging just like a book in production or even in quarantine.
Book needs hence to have a "backup" property which can be set from the UI ("Backup" button). When a book is backup, it is immediately copied to a new "Backup" area. Just like we already have "Quarantine" and "Staging", this area definition in terms of storage is done through specific env var. Backup also has a download + view URL to display in book details (just like any URL).
In the UI, when a user decides to delete a book the popup:
- informs when the book is already backup: "This book will continue to live in backup"
- propose to backup with a checkbox: "Preserve this book in backup"
Backup books are shown through a special list (once #293 is implemented) just like archived titles.
@elfkuzco I think this is ready to be implemented, do no hesitate to ask question / make suggestions
There are some books of particular interest. Either because we need them to analyze a bug, or they showcase an important milestone, etc ...
These backup books must continue to live no matter what happens to them due to the regular CMS lifecycle. We need for instance to backup a book which is in staging just like a book in production or even in quarantine.
Book needs hence to have a "backup" property which can be set from the UI ("Backup" button). When a book is backup, it is immediately copied to a new "Backup" area. Just like we already have "Quarantine" and "Staging", this area definition in terms of storage is done through specific env var. Backup also has a download + view URL to display in book details (just like any URL).
In the UI, when a user decides to delete a book the popup:
Backup books are shown through a special list (once #293 is implemented) just like archived titles.
@elfkuzco I think this is ready to be implemented, do no hesitate to ask question / make suggestions