To manage Sections, log into the admin tool and navigate to Projects → Sections template.
The goal of section templates is to create models that organize Proofs into logical groups which can be reused as required.
Creating a Section template
Section templates are managed in the admin tool, under Project and then Sections Template. The left side of the screen shows the list of section templates and the right side shows the details of the selected template and allows you to create a new one.
To create a Section template, fill in the information on the right side of the screen and then select Add.
Once the model has been created, it is available for addition in projects and project configurations:
To add it to a project configuration, simply select the model from the dropdown and click "Add".
In the "User rights" tab, you can control access to the Section on a user-by-user basis.
Section Settings
1 Name - this will be visible in the production view
2 Color: the background color of the section helps differentiate sections.
3 Access - default access/visibility of the section. These settings are only applicable at section creation. Once pages have been allocated to it, it is no longer possible to edit access.
4 Override job's book settings - override the project's flipbook settings
5 Booklet - used to change the position of the binding for the section's flipbook settings.
6 Regular expression for name - regular expression to extract one or more words from the file name to dynamically create the section name
Example – create sections dynamically from the name of the chapter which is the second part (#2) of the file name:
7 Regular expression for pages - Regular expression which permits the dynamic allocation of pages to the section. This can be used in conventional and dynamic sections.
Example – For a dynamic allocation of the pages to a section, there is no need for a condition; matching is sufficient. In the example below, any filename starting with VERNIS, OR, JAQ or CV will be added.
Dynamic Sections (automatic creation)
Dynamic sections are recommended because they can be easily reused to manage groups of Proofs in a project.
In the example below we have created three dynamic sections in a project configuration.
1 There is a section (parent) that will create sections (children) in relation to the chapter name found in the file name of the project. The internal pages of the project will therefore be placed in the various chapters (one chapter = one section).
2 There is a second section (parent) that will create a section (children) in relation to a non-internal page type (covers, gloss, dust jacket, etc.). These types of pages will be placed in a single section.
3 The last section (parent) will create a section (child) in which the front and back fly-leaves will be placed.
Creating a Static Section
In Production view of the project config for the sample project below, there are 20 proofs (pages) contained in this project.
One user will review pages 1-10, and another user will review pages 11-20. The proofs can be organized into two sections (named S_1 and S_2). For each, simply type in the name of the Section and click "Add".
To allocate Proofs 1-10 to section S_1, start by selecting them. Click on Page 1, then Shift-Click on Page 10. All 10 pages should be selected.
Drag and drop the selection into the Proofs tab beneath the Save and Delete buttons.
The 10 selected Proofs will take on the color of the Section they were added to. In the Proofs tab of that Section, Pages 1-10 will now appear.
In the same way, add Proofs 11-20 to the S_2 Section.
In the User Portal, Sections can be seen within the Flat Plan of the Project Dashboard. Click on the Section to filter from all Proofs to only those in that Section.
Introduction
xxx
Project Type base settings
Once a new Project Type has gets created, the following base settings are available:
Project Options
Below are the available project options and their descriptions.
Processing Options
The processing options determine how the Agent server will render the files for viewing in the Review Interface. (Please note: Some of these values will change depending on which Provider gets chosen for the Project Type).
For the PDF Provider type, the following options are available:
For the Image Provider type, the following options are available:
ICC Settings
ICC profiles are used to manage the color rendering used when creating Proofs for viewing in the Proofing Viewer.
ICC source profile
The ICC source profile is a mandatory setting that determines how the Agent will render files for viewing in the Proofing Viewer. Depending on the files you intend to upload, you will need to set the ICC source profile to a CMYK or RGB profile. If an RGB file is submitted to a project that is configured for a CMYK source profile (or vice versa), it will error on the Agent.
ICC destination profile
The ICC destination profile is a mandatory setting determining how the Agent will render files for viewing in the Review Interface. We recommended that the destination profile is set to sRGB for viewing in your browser.
ICC Intent
ICC intent determines the rendering used, and the choice should depend upon whether or not your screen is colorimetric.
For a non-colorimetric screen, there are two options:
Perceptual: Colors are close to subjective reality, but colorimetry is inaccurate.
Saturation: Colors on the screen are saturated to force the tones.
For a colorimetric screen, there are two options:
Absolute colorimetry:
Color rendering in terms of measurement, with respect to the white point of the source profile (for example, a simulation of the white paper, in the case of a press simulation). Please note that the output profile must have a sufficient gamut (color capability as extensive as the source profile described).
Relative colorimetry:
Color rendering in terms of measurement, with respect to the white point of the destination profile (for example, disregarding the white paper in the case of a press simulation). Please note that the output profile must have a sufficient gamut (color capability as extensive as the source profile described).
ICC proofing profile
You can perform a simulation using an ICC profile other than the destination profile by configuring the ICC proofing profile.
In the example above, we want to view the photos in a project using a specific non-RGB profile from a publisher's press.
For comparison purposes, the image below left is processed from an AdobeRGB profile to an sRGB profile. The image below right is the result when using the printer profile without any out-of-gamut warning. As you can see that the colors are more matte.
The picture below left is an example of when the out-of-gamut warning is enabled. The diagram below right explains why any out-of-gamut color will be replaced by white.
Colors in the image get based on the rendering mode at the intersection of the source and destination profiles. In this example, the two modes are perceptual.
With the "Image" Provider, you can also indicate a secondary ICC profile:
This enables you to process images with different colorimetric profiles with a single project configuration (in the example above, quadri and RGB images get processed in the same project).
The JPEG Quality option is used to define the compression rate for these JPEG images. This setting is a percentage where the default value is 80, and the range of values extends from 1 to 100. When the value is 100, there is no destructive compression. The image format is no longer a JPEG. Instead, it has become a proprietary Aproove format which is more efficient than JPEG. The rate of 100 is therefore used to obtain a result without any loss of quality (lossless).
Below left, you can see a series of artificial pixels (visual artifact) resulting from an image compression of 80.
Below right, the value is 100. With the same zoom, you can see that the area does not present any visual artifact.
Booklet
The booklet option is an Agent setting to enable the creation of booklets. (Please note: For users to view the booklets, they will require user permissions). The display is also used in the Review Interface "Project view" area.
If the booklet option is chosen, you must define the position of the binding by selecting the appropriate display.
Below we explain the booklet options along with an example of how the selected view looks in the Review Interface "Project View" area:
.png?width=65&name=worddav112db6aa1f65c97b6781d0d440b7ee1b%20(1).png)
Please note: When the Booklet option is not checked, the proofs in a project will be displayed as follows:
Note: When the Booklet option is not checked, the pages of the project are displayed as follows:
Crop
The crop function is an Agent setting that will simulate the cropping that will be applied to a PDF proof. This setting is used independently for each page in each PDF file for the project. It is important to note that this setting does not apply any crops to the physical PDF itself. The cropping is simulated when the file is processed, and the view of the PDF inside the Review Interface will reflect what settings you apply here.
The Custom box option enables you to simulate any cropping that will be applied to the pages in the project. This physical crop helps highlight inappropriate technical choices with the help of the simulation, as opposed to the extracted settings of the PDF file (trim, crop, media, etc.).
In this example, the image on the left is viewed in regular size. The image on the right is cropped using the Custom box setting. Twenty (20) mm have been removed from each margin in this example. This feature allows you to define your PDF viewing preferences to view based on the media, crop, bleed, trim, or custom box.
Naming Conventions
Below is an illustration of the available naming convention options.
Ignore Part - Basic
This option tells the system to ignore certain parts of a filename when trying to match new versions of existing files. This enables you to manage most of the simple naming convention scenarios. The separator is a prefix or suffix to the part to be ignored within the file name.
You should select the separator and the position relative to the separator to use this functionality, which can appear several times in the name.
This option tells the system to ignore certain parts of a filename when trying to match new versions of existing files. This enables you to manage most of the simple naming convention scenarios. The separator is a prefix or suffix to the part to be ignored within the file name.
You should select the separator and the position relative to the separator to use this functionality, which can appear several times in the name.
In the example below, the underscore is the separator. The position relative to this separator must be defined.
Example: AAAAA_BBBBB_CCCC.pdf
Position 1: AAAAA
Position 2: BBBBB
Position 3: CCCCC.pdf
The position is used to specify the position of the part to be ignored within the file name. This allows Aproove to compare different versions of PDF files:
0001_AAAA_12345.pdf When the Ignore part option is enabled, the separator is _, and the position is 3:
0001_AAAA
0001_AAAA_32314.pdf would also get interpreted as 0001_AAAA.
This method enables you to ignore, for example, the unique serial number of the file often generated by workflows such as Dalim Twist or Prinergy. This avoids having to rename files before opening a newer version of a page in Aproove.
Ignore Part - regexp
You can use a regular expression to extract the page number or ignore a variable part of a file name.
Example: the page number is in the first three characters of the file name
Therefore, the naming convention is:
For example, when a file gets added bearing the name 003 – XXX.pdf, it will appear on the page 3 position:
With a regular expression, the position value represents the group's position that you wish to extract (use) within it.
For example, we have to extract the page number from files bearing the naming convention:
123_ABCDE_page123.pdf (the position of the page number is indicated in red)
The regular expression can be:
(^[0-9]{3,})
_((?<=).+?(?=))_page((?<=_page).+?(?=\.))
It consists of three groups of extractions, and the one that concerns us is the 3rd from the left. Therefore, we should enter position 3.
The same principle is used to ignore a part. A regular expression must be composed, which extracts the variable part of the file name.
For example, we want to ignore files that have a version number. The files will have the naming convention: 123_ABCDE_V123.pdf
The regular expression is: (.*)
(_V[0-9]*.)
Therefore, we are going to use position 2 to ignore group 2
By submitting in succession the files Briefing_V1.pdf and Briefing_V2.pdf, we obtain a single page in two versions:
Naming Conventions
Below is
