Statuses - Revision history

Dani: Marked this version for translation

2015-11-11T20:23:39Z

Marked this version for translation

Dani at 20:23, 11 November 2015

2015-11-11T20:23:25Z

Dani: /* Dossier */

2015-11-11T20:23:09Z

‎Dossier

Dani: /* Recipe */

2015-09-21T17:57:54Z

‎Recipe

Dani: /* Recipe */

2015-09-21T17:56:27Z

‎Recipe

Dani: adding recipe statuses

2015-09-21T17:55:35Z

adding recipe statuses

Dani: updated to reflect new status and routing

2015-09-01T18:48:02Z

updated to reflect new status and routing

Dani at 13:47, 21 August 2015

2015-08-21T13:47:53Z

Dani at 13:47, 21 August 2015

2015-08-21T13:47:28Z

Dani: grammar

2015-08-19T21:49:04Z

grammar

@@ Line 1: / Line 1: @@
-<translate>Assets within [[Enterprise]] and [[Elvis]] do not actually move around. Statuses allow users to mark a file's progress through the workflow without physically moving the file.
+<translate><!--T:1-->
 Statuses are specific to [[object type]]s. Some statuses trigger actions or suggest an automatic [[routing]].
-==Article==
+==Article== <!--T:3-->
 *Article Draft: This article is being written.
 **Next status: Article Edit
@@ Line 14: / Line 16: @@
 *Article Ready for Publishing: This is a web status that you can ignore for now.
 Note that at a certain point, Articles become Layouts and continue moving through the workflow using Layout statuses.
-==Dossier==
+==Dossier== <!--T:5-->
 Editorial will not use dossier statuses beyond “Active," with one exception: Plate is using dossier statuses to note which stories have been sent to Art.
 Anything marked “PDF Collection” will be automatically routed to the marketing and production team; note that this status is only used by an automated part of our production process and should not be manually selected.
 (NOTE: Once an issue is out the door, production should manually move the dossier to the next status, which is “Inactive.” This will remove the PDF dossier from the inboxes of all team members.)
-==Image==
+==Image== <!--T:8-->
 *Image Draft: This image has just come in.
 **Next status: none
@@ Line 45: / Line 50: @@
 **Next status: none
-==Layout==
+==Layout== <!--T:9-->
 *Layout Draft: The designers have changed an approved article into a layout.
 **Next status: none
@@ Line 63: / Line 68: @@
 **Next status: none
-==Publish form==
+==Publish form== <!--T:10-->
 *Twitter Draft: Someone has created a tweet.
 **Next status: none
@@ Line 73: / Line 78: @@
 **Next status: none
-==Recipe==
+==Recipe== <!--T:11-->
 *Recipe Include in Packet: New recipe to be considered in photo meeting. Will be included in the recipe packet.
 *Photo Recipe Draft: Recipe newly designated as photo. Katie is working on it.
@@ Line 86: / Line 91: @@
 *Web Recipe Approved: Recipe is approved and ready for web.
-==Other media==
+==Other media== <!--T:12-->
 Audio, spreadsheets, and videos also have draft, edit, approved and ready to publish states specific to their types.
 [[Category:How can I]]</translate>

@@ Line 1: / Line 1: @@
-Assets within [[Enterprise]] and [[Elvis]] do not actually move around. Statuses allow users to mark a file's progress through the workflow without physically moving the file.
+<translate>Assets within [[Enterprise]] and [[Elvis]] do not actually move around. Statuses allow users to mark a file's progress through the workflow without physically moving the file.
 Statuses are specific to [[object type]]s. Some statuses trigger actions or suggest an automatic [[routing]].
@@ Line 89: / Line 89: @@
 Audio, spreadsheets, and videos also have draft, edit, approved and ready to publish states specific to their types.
-[[Category:How can I]]
+[[Category:How can I]]</translate>

@@ Line 17: / Line 17: @@
 ==Dossier==
-Editorial will not use dossier statuses beyond “Active.”
+Editorial will not use dossier statuses beyond “Active," with one exception: Plate is using dossier statuses to note which stories have been sent to Art.
 Anything marked “PDF Collection” will be automatically routed to the marketing and production team; note that this status is only used by an automated part of our production process and should not be manually selected.

@@ Line 76: / Line 76: @@
 *Recipe Include in Packet: New recipe to be considered in photo meeting. Will be included in the recipe packet.
 *Photo Recipe Draft: Recipe newly designated as photo. Katie is working on it.
-*Web Recipe Edit: Recipe newly designated web-only. Katie is working on it.
+**Next status: Photo Recipe Edit
 *Photo Recipe Edit: Recipe is ready for approval.
 *Web Recipe Edit: Recipe is ready for approval.
 *Photo Recipe Approved: Recipe is approved and ready for print.
 *Web Recipe Approved: Recipe is approved and ready for web.

@@ Line 74: / Line 74: @@
 ==Recipe==
-Recipe Include in Packet: New recipe to be considered in photo meeting. Will be included in the recipe packet.
+*Recipe Include in Packet: New recipe to be considered in photo meeting. Will be included in the recipe packet.
-Photo Recipe Draft: Recipe newly designated as photo. Katie is working on it.
+*Photo Recipe Draft: Recipe newly designated as photo. Katie is working on it.
-Web Recipe Edit: Recipe newly designated web-only. Katie is working on it.
+*Web Recipe Edit: Recipe newly designated web-only. Katie is working on it.
-Photo Recipe Edit: Recipe is ready for approval.
+*Photo Recipe Edit: Recipe is ready for approval.
-Web Recipe Edit: Recipe is ready for approval.
+*Web Recipe Edit: Recipe is ready for approval.
-Photo Recipe Approved: Recipe is approved and ready for print.
+*Photo Recipe Approved: Recipe is approved and ready for print.
-Web Recipe Approved: Recipe is approved and ready for web.
+*Web Recipe Approved: Recipe is approved and ready for web.
 ==Other media==

@@ Line 11: / Line 11: @@
 **Next status: Article Ready for Art
 *Article Ready for Art: Story is complete and dossier contains all art for the layout. Alerts art team that a story is ready to be laid out.
-**Next status: Article Ready to Publish
+*Article Laid Out: Art has processed this article, but editors will continue to access it for editing.
 Note that at a certain point, Articles become Layouts and continue moving through the workflow using Layout statuses.
@@ Line 49: / Line 50: @@
 *Layout Edit/Copyfit: The editors are taking a look at the new layout.
 **Next status: none
-*Layout Approved: The editors have signed off on the story and it is ready for prepress. Permanent Version created.
+*Layout Approved: The editors have signed off on the story and it is ready for prepress. Permanent Version created. Routes to art department.
 **Next status: Layout Convert to PDF
 *Layout Convert to PDF: Automatically makes a PDF version of each individual page and saves them in a dossier called “PDF_[issue name]” with a status of “PDF Collection.” This dossier is automatically routed to the marketing and production team.

← Older revision		Revision as of 21:49, 19 August 2015
Line 1:		Line 1:
−	Assets within [[Enterprise]] and [[Elvis]] do not actually move around. Statuses ~~are a tool that allows~~ users to mark a file's progress through the workflow without physically moving the file.	+	Assets within [[Enterprise]] and [[Elvis]] do not actually move around. Statuses allow users to mark a file's progress through the workflow without physically moving the file.

	Statuses are specific to [[object type]]s. Some trigger actions or suggest an automatic [[routing]].		Statuses are specific to [[object type]]s. Some trigger actions or suggest an automatic [[routing]].