-
Notifications
You must be signed in to change notification settings - Fork 11
Use case document collaboration
Where Use Case CommYou is focused on replacing CommYou within Querki, and is likely pretty trivial, this one is focused on pulling the best ideas from Wave into Querki. It's a good deal more complex.
The key notion here is that Querki can be used to develop a Thing, not just comment on it after the fact. This has one huge implication: we want to be able to have a comment thread that is clearly attached to a particular place in the Thing. Pretty much every document-collaboration system has come up with some version of this; even Word's comments system put comments in the right-hand margin, attached to specific text locations.
The UI for this is not at all obvious. We could do interstitial comments like Wave, or marginal ones like Word; we could also do comments as pop-over windows. In a sense, it doesn't matter a lot -- if we get the concept of an embedded thread right, we can experiment with UI options for displaying it, and possibly allow the user to choose which one she wants.
I often wrestle with whether comments should be integral to Querki, or implemented entirely separately. This Use Case is the main reason I'm leaning towards integration -- I can't see a really robust way to implement embedded comments without Querki at least knowing about them. My current inclination is that an embedded conversation has its data in a separate table, but we stick a marker into the Text in the right place so that the conversation shows up in the right place. This marker will be deleteable when you edit, so you can snip a conversation when it's no longer relevant, or move it around.
This Use Case is likely key to moving into the enterprise, if we ever choose to do so. It's the single thing I most often found myself wanting while at Memento, and we should be prepared to examine corporate requirements for it. Access controls, import/export and workflow are all clearly essential to doing this well within a corporate environment.
There will be quite a number of features implied by this Use Case; we'll need to break it down carefully.