diff --git a/README b/README index 93a2a1d..6d793e8 100644 --- a/README +++ b/README @@ -29,15 +29,31 @@ python3 main.py offer to move parent/child series orders as well to match (think Thomas Covenant) ### TODO: + - consider created/modifed for all fields? but mostly are they set via ORM for new books? + - need to delete 1 sub_book from book + * swap the 'add sub book' for 'remove from parent book' button and then act on it (separate route, simple sql exec and route back to (no-longer) child book) + (noting that deleting a child book already removes the book_sub_book_link) - when remove a Parent book from a series, what do we do? (remove all sub books from series too?) - - need to delete 1 sub_book from book + - need to delete all classes (and watch for referential integrity) + * book (as long as no sub-books)... + NOT tested how this goes with deleting book that is in a loan, or book that is in a series + - can delete: + author, publisher, series, condition, covertype, owned, rating, genre, loan, + - should deleting really just ask if want to mark it as SOLD? - need to add books to loan (on loan page, and via a book search?) - need to delete book from loan - - need to delete all classes (and watch for referential integrity) - * book - - can delete: - author, publisher, series, condition, covertype, owned, rating, genre, loan - show books on shelf list - show books to buy view / printable + - show unrated books (with toggle to exclude those with missing in a series) + - show books missing from a series (I own only some of them) + - show books on wish list + - show books that need replacing + - show books I have sold + - show books with poor rating + - view list of possible duplicate books by title + - consider which of the 'books maybe not valid' reports make sense still + (can you even have an N/A publisher now for example, but the genre one is interesting) + + - with ORM: should I lazy load all books (ajax the 2nd->last pages in, or not use ORM, and do a quick db.execute()....)