Already a member?
Sign in
Workflow basics
We want to simplify and modernize our system of publishing to the Web and print as much as possible while preserving the editing steps needed to ensure accuracy.
With information and some guidance from IT and APT, we have developed an initial queue structure and work flow plan. We can always make minor adjustments before going live in all sections, but it is a goal to have one workflow that generally works for all departments.
BASICS
The APT editorial system is a queue based system. Every user of the system has a personal queue.
All of the users included in the reporters training group have a reporter queue. These are users who edit their own work, but no one else’s. Stories in a reporter queue can be edited only by the owner of the queue. Copies may be created by dragging a story from the reporter queue into another queue.
All users included in the news or sports paginators groups should have an editor queue. These are users who edit their own work AND the work of others.
User queues were created with a single login point, meaning that after initial setup, APT should start up without entering a user name and password.
PRODUCTION AND WIRE
In addition to Reporter and Editor queues, APT editorial utilizes three other kinds of queues. The three other types of queues are Production queues, Public queues and Wire queues.
Production queues are used to store finished pages that are ready for production. Daily pages are created and stored by day of the week in production queues labeled Monday, Tuesday, etc. Other finished pages are stored in production queues such as Advance and Special Section.
We have defined production queues to match the pages produced. However, the workflow your newsroom follows to produce pages will change from the basket-based Harris system.
Public or Editing queues are also used to store finished stories that are ready for pagination. Finished stories filed by reporters to queues such as Daily Local, Sunday, Enterprise, etc. We defined these public queues to match the locations that finished stories should be stored according to departmental and newsroom workflow.
Other production queues are used during the design and copy editing. We have streamlined this process so that page editors/designer pluck stories from departmental queues and place them on page for copy editing, which automatically moves them to a production queue such as Jstory. When the stories are backread and marked final, they
Still another production queue is used for import from the Harris editorial system. And stories going to AP Carbon or Lee Carbon will also get stored in public queues.
Wire queues are used to display wire stories as they are pulled off the AP wire and handled by a process server. Users can select and copy stories from wire queues to reporter or editor queues in the same way that you coped stories off the wires from Harris.
The current wire structure mirrors Harris wire sorts. It is possible to define wire queues differently to match and/or improve upon the current wire story workflow in our newsroom. APT's superior search functions also may help you more effectively sift the wire.
Latest page update: made by tpkelley
, May 7 2007, 2:15 PM EDT
(about this update
About This Update
Edited by tpkelley
2 words added
1 word deleted
1 image added
view changes
- complete history)
Edited by tpkelley
2 words added
1 word deleted
1 image added
view changes
- complete history)
Keyword tags:
None
More Info: links to this page