We’re an example of a project with lots of collections, mostly because of what needs to be defined at the collection level instead of by book. We work with 3 related languages, so that’s the first reason for separate collections.
Then, for each of the languages, we have a separate collection for each of three formats:
- book layout (which has its own title/credit page),
- pamphlet layout (similar to the page-saver w/ title/credit info inside the front cover),
- and digital versions.
Additionally, some of these collections are divided by subject/theme, something we would do when using any other publishing tool as well.
These reasons all have to do with the things you mentioned above; another reason we also separate books into special collections is for the purposes of archiving. Since the way we archive Bloom books is to archive the whole collection (to preserve the collection-level configurations), we’ve been moving books from our working collections to a corresponding “archiving” collection when they’re ready for that step. I guess that could fall under your point about books in different stages. One other reason where we could divide collections further in the near future would be based on whether or not we need the new “Team Collection” features.
We don’t consider it a problem to have a lot of collections for the most part. Like I mentioned, we would divide publications into different folders in a lot of the same ways when working with Publisher or OpenOffice, etc, anyway. One thing that would simplify our collections in Bloom would be if the frontmatter layout were defined by book instead of by collection. Sometimes we start working with a book in a “pamphlet layout” collection and realize that it will need more pages than we originally thought. When it needs enough pages to be considered a book, we have to move it to a different collection, which means using the “Open folder on Disk” command from the original “pamphlet layout” collection, closing Bloom, moving the book’s folder to the corresponding “book layout” collection, and then re-opening that collection in Bloom.
So if we could just change the frontmatter for the book, we wouldn’t have to move it to a different collection. Or if there were a “Change collections” choice in the same menu where the “Open folder on Disk” choice appears, so that the collection change could be done in Bloom, it wouldn’t be such an issue for some of our teammates who aren’t so confident working in the file system.