Hi Owen, On 4 Feb 2013, at 14:10, Owen Winkler wrote:
> On 2/4/2013 7:54 AM, Philip Buckley wrote: >> >> I think that probably your suggestion, Chris Davis, of a plugin to >> control the assigning of posts to individual people is the *safest* way >> to go. It would be very smart if, in the case of a single country editor >> they would simply have a Finish button, whereas in the case of multiple >> country editors they would see either the Finish button or have >> the choice to, as it were, ‘pass the post on’ to one of the other 2 or 3 >> editors for that country - a Pass On button with a dropdown showing the >> other people responsible for reviewing that country’s material. That >> would be smart but maybe complicated to implement! > > This actually doesn't seem that complicated. Whatever the editorial > workflow, the most complicated part seems to be sorting out the workflow > itself. Implementing it is academic after you have that. In practice we are simply told by the client who in the countries needs to be notified when the files for that country are available. So we might be told that for Germany we are to notify Andreas, for Spain Pablo, for Norway Hedda and Helga. It might be that Hedda and Helga both want to review the Norwegian documents or it might be that they both need to be notified because one or other of them will do the review (perhaps whichever is available at the time will pick it up and act on it - from our end it doesn't matter and we don't really need to know). > In this case, you'd probably also want a thing that marks a post as being > edited by whoever first grabs it. So if you try to edit a post that you're > not "active" on, it'll throw a big warning up at the top of the page, telling > you something like, "Bob started editing this 50 minutes ago." That way, if > you see something like "Bob started editing this 4 days ago", then you know > that you should ask Bob if he's done or what. The message may not prevent you > from editing, just tell you to beware. Ah, I like that. That's a different and a potentially much easier way of doing it than I had thought about. I had thought it would need to be a hard "lock-out", so if person A started editing no-one else could edit until that first person had finished (which would raise the problem already discussed of the abandoned post or disconnected user and maybe require an admin user or the original editor intervening to "unlock" a post). But if it was simply that the second user was told by a message as soon as they started editing that the first user had started editing before - the "Bob started editing . . ." message - then they could make their own decision as to how to proceed: OK I'll come back in an hour's time when Bob has finished or OK, I know Bob has made all the changes he wanted to 4 days ago because I have spoken to him since then, so I'll just carry on. If the second user is not prevented from editing, then they are not held up and can use their discretion whether to edit or not. Very nice! :-) > The workflow would probably also track who has already edited it, so that you > know who is left and whether a review is complete. This would be pretty > simple with the new revisions functionality; I can think of a couple of > different ways to implement it. In the Hedda/Helga example we don't know (or need to know) whether actually both or just one of the two will do the review, therefore as far as knowing whether a review is complete, I think all that's needed is a clear "Finish and Stop" button (that they know means "all the revisions have now been made by everyone for this country in this round of revisions"). Where tracking would be very useful and important is, as sometimes happens, something goes wrong and it needs to be established who requested a change and when . . . Helga requested such and such a change on such-and-such a date. For that situation the revisions history would be great. I am getting very excited about the possibilities here! :-) Philip -- -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-dev --- You received this message because you are subscribed to the Google Groups "habari-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
