While #293 will allow to edit book with bad flavours, we ideally want to ensure a regression in a scraper will not cause CMS to suddenly publish unexpected flavours.
We hence need to define in the title which flavours we expect this title to have.
And whenever a new book arrives in the CMS, the CMS will check if title is expecting this flavour.
If not, book will be forced to go through staging. It will hence already be associated with the title for convenience.
A book cannot be moved to production if title does not list its flavour, user need to either fix the title or the book.
UI must clearly indicate that a book has an unexpected flavour (e.g. with an exclamation mark next to the flavour in book list or book details).
@elfkuzco I assume this is ready to be developed, let me know if you have questions / suggestions
While #293 will allow to edit book with bad flavours, we ideally want to ensure a regression in a scraper will not cause CMS to suddenly publish unexpected flavours.
We hence need to define in the title which flavours we expect this title to have.
And whenever a new book arrives in the CMS, the CMS will check if title is expecting this flavour.
If not, book will be forced to go through staging. It will hence already be associated with the title for convenience.
A book cannot be moved to production if title does not list its flavour, user need to either fix the title or the book.
UI must clearly indicate that a book has an unexpected flavour (e.g. with an exclamation mark next to the flavour in book list or book details).
@elfkuzco I assume this is ready to be developed, let me know if you have questions / suggestions