Difference between revisions of "Statuses"
m |
(Marked this version for translation) |
||
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--> |
+ | 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. | ||
+ | <!--T:2--> | ||
Statuses are specific to [[object type]]s. Some statuses trigger actions or suggest an automatic [[routing]]. | 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. | *Article Draft: This article is being written. | ||
**Next status: Article Edit | **Next status: Article Edit | ||
Line 14: | Line 16: | ||
*Article Ready for Publishing: This is a web status that you can ignore for now. | *Article Ready for Publishing: This is a web status that you can ignore for now. | ||
+ | <!--T:4--> | ||
Note that at a certain point, Articles become Layouts and continue moving through the workflow using Layout statuses. | 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. | 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. | ||
+ | <!--T:6--> | ||
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. | 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. | ||
+ | <!--T:7--> | ||
(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.) | (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. | *Image Draft: This image has just come in. | ||
**Next status: none | **Next status: none | ||
Line 45: | Line 50: | ||
**Next status: none | **Next status: none | ||
− | ==Layout== | + | ==Layout== <!--T:9--> |
*Layout Draft: The designers have changed an approved article into a layout. | *Layout Draft: The designers have changed an approved article into a layout. | ||
**Next status: none | **Next status: none | ||
Line 63: | Line 68: | ||
**Next status: none | **Next status: none | ||
− | ==Publish form== | + | ==Publish form== <!--T:10--> |
*Twitter Draft: Someone has created a tweet. | *Twitter Draft: Someone has created a tweet. | ||
**Next status: none | **Next status: none | ||
Line 73: | Line 78: | ||
**Next status: none | **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. | *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. | ||
Line 86: | Line 91: | ||
*Web Recipe Approved: Recipe is approved and ready for web. | *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. | Audio, spreadsheets, and videos also have draft, edit, approved and ready to publish states specific to their types. | ||
+ | <!--T:13--> | ||
[[Category:How can I]]</translate> | [[Category:How can I]]</translate> |
Latest revision as of 20:23, 11 November 2015
<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 types. Some statuses trigger actions or suggest an automatic routing.
Article
- Article Draft: This article is being written.
- Next status: Article Edit
- Article Edit: Someone else from the team is editing the draft.
- Next status: none
- Article Approved: Editorial has approved the article for publishing. Permanent Version created.
- 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.
- Article Laid Out: Art has processed this article, but editors will continue to access it for editing.
- 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
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 Draft: This image has just come in.
- Next status: none
- Image Edit: This image is being edited by editorial.
- Next status: none
- Image Send to Corrections: This status triggers the system to send the photo elsewhere. Permanent Version created.
- Next status: Image Out for corrections
- Image Out for Corrections: The photo is not yet back and should not be edited at all.
- Next status: Image Back from Corrections
- Image Back from Corrections: The photo is back but has not been reviewed.
- Next status: Image Approved
- Image Approved: The designers have approved the new version of the photo. Permanent Version created.
- Next status: Image Conversion to web formats
- Image Conversion to web formats: Triggers the system to resize the image, reduce resolution to 72 dpi, and save as a jpg. Permanent Version created.
- Next status: none
- Image web versions created: The system has automatically created a web version The image may require cropping and other correction by editorial.
- Next status: none
- Image Conversion to print format: Triggers the system? Permanent Version created.
- Next status: none
- Image Print-Ready: The image is ready to go into the magazine.
- Next status: none
Layout
- Layout Draft: The designers have changed an approved article into a layout.
- Next status: none
- 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. 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.
- Next status: Layout PDF Review
- Layout PDF Review
- Next status: Layout PDF Corrections
- Layout PDF Corrections
- Next status: Layout Convert to PDF
- FryPDF: Sends the PDF to Fry for printing. Permanent Version created.
- Next status: FryPDF - Sent
- FryPDF - Sent: PDF uploaded to Fry InSite.
- Next status: none
Publish form
- Twitter Draft: Someone has created a tweet.
- Next status: none
- Twitter Ready to Publish: The tweet is ready to go and/or approved.
- Next status: none
- Web Draft: Someone has created a web story.
- Next status: none
- Web Ready to Publish: The story is approved and ready to go.
- Next status: none
Recipe
- 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.
- Next status: Photo Recipe Edit
- Web Recipe Draft: Recipe newly designated web-only. Katie is working on it.
- Next status: Web Recipe Edit
- Photo Recipe Edit: Recipe is ready for approval.
- Next status: Photo Recipe Approved
- Web Recipe Edit: Recipe is ready for approval.
- Next status: Web Recipe Approved
- Photo Recipe Approved: Recipe is approved and ready for print.
- Web Recipe Approved: Recipe is approved and ready for web.
Other media
Audio, spreadsheets, and videos also have draft, edit, approved and ready to publish states specific to their types.</translate>