Part 3 of 3: Job Jackets and Project Files
Page 13

Resource Status: In Job Jacket vs. In Ticket vs. In Project

The bottom-right pane of the Advanced Settings mode includes a Status column, which shows the availability of each item. This column has three possible values: In Job Jacket, In Ticket, and In Project.

In Job Jacket

This status means that a resource exists somewhere in the job jacket. If you add a resource directly to a ticket, it is still available to the jacket because the jacket contains the ticket (i.e., everything in the ticket is also inside the jacket).

If you select a ticket in the left pane, resources added to the jacket are listed but show In Job Jacket status. Resources in a job jacket are automatically available to a ticket within that jacket, but are not automatically included. If you want to include a job-jacket resource in a job ticket, click the Status column menu and choose In Ticket.

For example, if you select a job ticket in the Job Jackets Manager and then select the Colors category, any color that exists in the job jacket will appear in the list for the job ticket. Those colors are not included in the ticket until you click the Status column and choose In Ticket.

Note: Working in Advanced Settings mode, any resource that exists in the job jacket will be available to — but not necessarily a part of — the job ticket. Once a resource is In Ticket instead of In Job Jacket, it is a part of that job ticket; when you create a new project based on that job ticket, In Ticket resources will be automatically included in the new file.

In Ticket

It is important to note that an In Ticket resource is also an In Job Jacket resource; what you see depends on what is selected in the left pane:

 

• If a ticket is selected, the Status column shows In Ticket
• If a jacket is selected, the Status column for the same resource shows In Job Jacket

If you specify an "In Jacket" resource (such as an output setup) in a layout, that resource is changed to "In Ticket". This makes good logical sense — calling it into a ticket makes it part of that ticket.

In Job Jacket

When a ticket is selected in the left pane, items listed as In Ticket will be included in a project created from the ticket. Because a resource is available in the project, you can change it (such as a color definition) in the project.

In addition to simply existing in the file, In Ticket resources are dynamically linked back to the job jacket. If you change the definition of an "In Ticket" asset in a linked project, the definition propagates back up the hierarchy; the asset definition is changed in the job ticket, which changes it in the job jacket, which changes it in any linked projects when those files update the link to the job jacket.

In Project

You'll only see this when a project (linked to a ticket) is selected in the left pane. You can create new assets (colors, style sheets, etc.) in a project file without affecting the associated ticket or jacket.

In the Job Jackets Manager, you can click the Status column menu and change an In Project item to In Ticket. This adds the resource item to the ticket, which in turn adds it to the job jacket.

Note: If you change an In Project item to In Ticket and an item with the same name already exists in the attached ticket, you will get a conflict warning dialog box where you have to choose which version of the item to maintain in the ticket. If any other project is linked to the same job jacket, the added resource will be available to those projects as well.

Assuming you've created a job jacket with all of the necessary information, it's now time to implement the job jacket in a QuarkXPress file.

You have two options:

• Create a new project from a ticket template.
• Attach an existing project to an existing ticket template.

1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19

If you enjoy our articles, click here to subscribe.
Free JavaScripts provided by The JavaScript Source

©2007 Against the Clock. All rights reserved. Reprinted with permission.