Issue system: Difference between revisions

Issue system (view source)

Revision as of 04:55, 6 October 2010

113 bytes added , 6 October 2010

→‎Features of this functionality

Maiphoang

18

edits

@@ Line 12: / Line 12: @@
 ==Features of this functionality==
-* In-line editing task annotations. Instead of waiting for the editor to complete editing a story, an editor can go and flag changes (tasks) that need to be made. For example, if the task is to fill holes of information, the editor can go ahead and make those edit requests. The reporter could begin editing those aspects of the story while the editor continues to edit the story. The reporter could also note when he or she completes the necessary edited tasks.  This creates more a collaboration rather than the traditional liner process of reporter hands in story - editor asks questions/revises - reporter makes the changes.
+* In-line editing task annotations. Instead of waiting for the editor to complete editing a story, an editor can go and flag changes (tasks) that need to be made. Here's the basic process:
-* Prioritization of editing. The system would provide a page for reporters and editors to see the priority of those tasks.
+** The editor receives the content.
-* The ability to directly import the information from the wiki to any content management system. (Ideally, it would be nice if the wiki and the content management system was one in the same, but there is an understand that this isn't always the case.)
+** The editor reads and begins editing. The editor can go ahead and cite necessary revisions (AP Style, reporting holes, writing issues, etc) within the text.
+** The edit request show up on a list that the reporter can access.
+** The reporter begins to complete those tasks while editing continues. The reporter could also note when he or she completes the necessary edited tasks or ask for follow up questions.
+* Prioritization of editing. As I mentioned, there is a page to view edit requests. Editors would also have the option of prioritizing those tasks. This would work great if the reporter is dealing with multiple types of content at one time.
 * The ability to document at the beginning of the reporting process what is desired for a story (story focus; people to interview; sides to cover). The system would also allow documentation of  necessary follow for a story or other piece of content.
+* The ability to directly import the information from the wiki to any content management system. (Ideally, it would be nice if the wiki and the content management system was one in the same, but we know that this isn't always the case.)
 * Eventually, we would like to develop a system that would also allow different areas of the newspaper (i.e. online departments, advertising, etc.) to bring up issues and tasks to each other. For example, if an editor has a problem with the CMS, the editor would be able to log into the system and flag a problem.