KHippolite wrote:really don't understand the clamor for having a forum for every work posted. Doesn't make sense; the majority appear, get little attention and then are never heard of again, so what would be the purpose in creating all these thousands of feedback forums above what is already available.
Yes... I see from this that my statement has been misunderstood so I'll rephrase it slightly.
What's needed is a way to attach a forum link to a particular work. For example:
[Body of Work]
[Inline Reviews]
[Reviews]
[Additional Feedback]
The additional feedback link would drop you into the forum thread associated with the work. You would be able to read & post in this forum thread without needing to join the group. You would not need to go hunt down the group / forum that was discussing this body of work. You would not need to randomly guess that there was a thread on it in the first place.
In general, I like this idea. Much better than people having to guess about an additional feedback thread, especially given the number of places where that thread could now exist (Additional Feedback group, Old Forums, Sci-fi group, etc.). If you post your work to multiple groups, as I believe most do, then there would be only one thread, not one per group.
However, such a capability would need to be able to associate the same thread with multiple chapters, otherwise there would be one per chapter, which would turn the group forums into a mess. Even one thread per work would probably be overload eventually. Everyone might create such a thread just in case and have it never get used. Then you have forums full of orphaned threads.
Another problem that would have to be addressed is what to do if an author has chosen not to create an additional feedback thread, but a reviewer wants to leave additional feedback. Then you get back to the current problem of not knowing where to put the thread and hoping the author sees it. If you allow reviewers to create that thread if there isn't already one, then you have to have to support notification to the author and, potentially, others about the newly created discussion.
On the other hand, using the existing chapter review mechanism as a means for discussion about a given chapter (as I think Sol is suggesting) also seems like a very logical thing to do, but it hides discussions from general visibility. If someone starts a discussion within a chapter that I've previously reviewed, how would I know about it unless I go back and check? There would need to be a way for the reviewer to subscribe to chapters in order to be notified about ongoing discussions about those chapters. Also, how would others who are not reading the book potentially participate in discussions if they have to search the bottom of each chapter for activity.
And, just to make everyone nuts, if there is a discussion going on inside an inline review, the only people who would know about it are the participants in the discussion. I don't read other's reviews in detail, clicking on each inline comment, so I'll never know about the discussion. Right now, even the author doesn't know if a third party is commenting inside an inline review left by someone else, although I presume that part will be addressed.
As I mentioned in an earlier post, the only ideal way to handle discussions would be to have a mechanism to browse/search/participate in discussions at the chapter level, work level, group level, or global level. That requires a very different architecture and a lot of work.
Dirk