hi all, i'm after feedback on exactly what a "save revision as draft"[1] feature should look like in drupal. here are some initial thoughts: 1. make it be possible to save an existing node or revision as a draft by adding a save as draft button - if there is already a draft associated with the node, copy over it 2. make it possible to 'promote' an existing revision to a draft from the 'revisions' tab - if there is already a draft associated with the node, copy over it 3. drafts can be deleted, which sets the node draft column to 0 and deletes the revision 4. drafts can be updated without creating new revisions 5. changes to the published/unpublished status of a draft's 'parent' node has no effect on a draft's status 5. add a draft id column to the node table - one draft per node. the value in this column would correspond to the vid of the row in the node_revisions table for the draft. a value of 0 would represent 'no draft' for a node 6. add a 'draft' tab to the node view, alongside the 'view' and 'edit' tabs 7. add some draft node permissions, so a user can be allowed to edit a node's draft without effecting live content i'm not aiming for a full workflow, just to allow for basic draft functionality. ideas, comments, etc all welcome. cheers justin
Just so people know, the issue for this is at: http://drupal.org/node/48731 Justin, I see that you've already contributed to this thread, so I'm saying this for your benefit - this is just for the people that don't know about the issue thread. Cheers, Jaza. On 8/10/06, justin randell <justin.randell@gmail.com> wrote:
hi all,
i'm after feedback on exactly what a "save revision as draft"[1] feature should look like in drupal.
here are some initial thoughts:
1. make it be possible to save an existing node or revision as a draft by adding a save as draft button - if there is already a draft associated with the node, copy over it
2. make it possible to 'promote' an existing revision to a draft from the 'revisions' tab - if there is already a draft associated with the node, copy over it
3. drafts can be deleted, which sets the node draft column to 0 and deletes the revision
4. drafts can be updated without creating new revisions
5. changes to the published/unpublished status of a draft's 'parent' node has no effect on a draft's status
5. add a draft id column to the node table - one draft per node. the value in this column would correspond to the vid of the row in the node_revisions table for the draft. a value of 0 would represent 'no draft' for a node
6. add a 'draft' tab to the node view, alongside the 'view' and 'edit' tabs
7. add some draft node permissions, so a user can be allowed to edit a node's draft without effecting live content
i'm not aiming for a full workflow, just to allow for basic draft functionality.
ideas, comments, etc all welcome.
cheers justin
justin randell wrote:
hi all,
i'm after feedback on exactly what a "save revision as draft"[1] feature should look like in drupal.
here are some initial thoughts: Do you have initial user stories to motivate this? In other words, first put it into a user-based context. One obvious user story is "Joe User is writing a node but needs to break to pick up his kids. So he wants it saved, but doesn't even want it put into the moderation queue, since he knows it's not ready." I can't think of any off the top of my head that would motivate turning an existing revision into a draft, but perhaps you have one in mind. ... 5. add a draft id column to the node table - one draft per node. the value in this column would correspond to the vid of the row in the node_revisions table for the draft. a value of 0 would represent 'no draft' for a node This is an implementation strategy, not a feature description, and hence belongs in some other step of this design process. 6. add a 'draft' tab to the node view, alongside the 'view' and 'edit' tabs What would this do? 7. add some draft node permissions, so a user can be allowed to edit a node's draft without effecting live content The two choices that come to mind are a) only the person who created the draft is expected to edit it; b) anyone with permission to edit the node has permission to edit a draft of the node. Are there other cases? Do these two cases require an additional permission?
Gary PS "effect" is rarely correct as a verb. So the easy rule, avoiding the uncommon cases, is that "affect" is the verb, "effect" is the noun.
On Thu, 10 Aug 2006 22:27:51 +1000, "justin randell" <justin.randell@gmail.com> said:
hi all,
i'm after feedback on exactly what a "save revision as draft"[1] feature should look like in drupal.
here are some initial thoughts:
1. make it be possible to save an existing node or revision as a draft by adding a save as draft button - if there is already a draft associated with the node, copy over it
What about drafts for nodes not yet created? That is, can I create a draft when creating a node, or just when editing? You make it sound like if I've made a draft of changes to a node, then you start editing the node and save your own draft, your draft overwrites mine. Is that what you mean? Or are drafts per-node per-user? It might be better to work with the form api and add a mechanism to save the state of any form, not just the node edit form. That way any user (with sufficient privileges) could save their work in progress on any form in drupal. Later they could pull up the form again, continue working and submit (or save another draft). -Dave
participants (4)
-
David Cohen -
Gary Feldman -
Jeremy Epstein -
justin randell