Let's use this discussion to talk about what our workflow process will be.

For the purposes of starting off this discussion, below is a high level workflow that I will propose. There are lots of areas that need to be defined: software tools, role details for each step, deadlines, etc. Please everyone feel free to add, subtract, or change from this starting point until we come up with a workflow that will hopefully work well for our magazine.

1. Authors draft their article, and are encouraged to ask others to perform an informal writer's review for style, voice, and grammar before submitting it to the sandbox site.

2. Authors submit articles to sandbox site and editor(s) get notified. I know of a 3rd party extension (JoomlaPraise SubmitMailer) that will trigger an automated email to designated recipients when an article is submitted.
When is a reasonable deadline (XX days before publishing target date)?

3. Peer Review. Editor(s) determine what section/category newly submitted articles fall under and notify relevant experts for that section/category. Experts review article and provide feedback to Author.
When is a reasonable deadline (XX days before publishing target date)?

4. Author revisions. Author revises article based on Peer Review. Author notifies Peer Review team of revisions.

>> Steps 3 and 4 may take multiple iterations.

5. Peer Review team approves article. Notifies Editor(s) that article is ready for additional editing.
When is a reasonable deadline (XX days before publishing target date)?

6. Editors edit the articles (for content, grammar, compliance), authors get notified when initial edits are complete.
When is a reasonable deadline (XX days before publishing target date)?

7. Authors provide feedback to editors regarding questions/concerns regarding initial edits or additional any other issues.
When is a reasonable deadline (XX days before publishing target date)?

>> Repeat steps 6 and 7 until Authors and Editors agree on approved final article.

8. Editors place approved articles into magazine's structure on sandbox site.
When is a reasonable deadline (XX days before publishing target date)?

9. Upcoming issue is tested on sandbox site. Any changes are made and then issue is retested.
When is a reasonable deadline (XX days before publishing target date)?

10. Webmaster is notified when upcoming issue is ready to publish.
Proposed deadline: XX days before publishing target date

11. Webmaster publishes upcoming issue on production website.

Tags: magazine, workflow

Views: 17

Replies to This Discussion

Also we need to check with Fotis re. the issue thing - can we pre-produce an issue (all its content, modules, ads, author bios..etc) and then publish as a whole? I'm not familiar with K2 so Fotis can you please guide us here?
thanks
Dex
We don't really use the sandbox that much on the Community site (at least I don't), since the site is pretty stable with not a lot of new types of content being added. For example people who submit blogs post them directly to the production site. The sandbox is primarily there if we want to test a new extension, upgrade J! there first to see if there are any problems, test any changes to the template, etc.

In the initial workflow that I wrote up, I had authors submitting their articles to the sandbox and I assumed edits would happen there too. I thought one advantage is it could be kind of a "cookie jar", in that whoever had time to edit from one day to the next could go to the sandbox and see what's in the "edit" category, then move articles to the "final" category when editing was finished. Of course it doesn't have to happen that way if you or someone else has another idea.
well that depends a bit on what Fotis says, I think. Thanks for your ideas - I'm not fixed, but keen to reduce workload as everyone is a volunteer and editing is a big job.
Agreed!

RSS

Badge

Loading…

© 2012   Created by Amy Stephen.

Badges  |  Report an Issue  |  Terms of Service