Closed DavidAJohn closed 3 years ago
I've updated the book specifications, which will be the limit of what I do with this issue. I won't be allowing admins to de-activate authors or categories - just individual books.
I'm not convinced there would ever really be a business case for a library disabling an entire author's work. It's possible that a particular book (or several books) by an author could be withdrawn from publication, but surely not an entire author's work. I would have thought each book would be reviewed and judged on its own merits.
De-activating a category also seems unlikely. It would mean forcing an admin to select a different category for each of the books in the category to be disabled. Surely an edge case at best, and quite awkward to implement.
Before allowing admins to de-activate items, several specification classes need to be changed to include the IsAvailable property.
Firstly, the respective SpecificationParams classes need to have the IsAvailable property added.