You are viewing an old version of this page. View the current version.
Compare with Current ·
View Page History
cConnection with K4 Server
First of all the user need to set the parameters to connect TIMONE System with K4 Server.
In the Administration module, from System > Configurations (or Config. Publication if you want to set it just for a specific publication) > PRODUCTION, set the production software in use (K4).
Then in System > Config. Publication > K4 set:
K4_url, the full addres of your K4 installation;
K4_user, username enabled, with full accesses, in K4;
K4_password, the user password;
K4_version, the version of your K4 system.
Publication
Create the publication in K4 and call it as the "production name" of the one in TIMONE System that we want to synchronize.
Issue
To synchronize an issue in TIMONE System you must create a new issue in K4 (same publication and channel) called as the "Prod Code" of the already existent one.
 | It's possible to create a new issue from scratch or by duplicating an existing one:
|
 | the names of the issues must be configured identically in TIMONE System and Vjoon K4, to allow a correct synchronization of the information between the two systems. |
Workflow and Channel
Create the workflows layout, adv and file_adv 
in the workflow section of the Publication. The exact names must be written in the corresponding TIMONE System configuration in System > Configurations (Config. Publication) > K4 > K4_Layout_workflow, K4_Advertisement_workflow e K4_Advertisement_File_workflow.
Workflows in K4 consists in name, publication channel, tasks and statuses. To move between the statuses you have to finish the actual task and accept the next one to access the following status.
Each workflow can be enabled on a different publication channel, in our case to synchronize the objects they will be all set to the same one.
To create a publication channel open the "Edit Output Channel" window 
.
The name of the channel must be written in the configuration K4_pub_channel in the TIMONE System Administration.
The layout workflow ( K4_Layout_workflow) type need to be "Layout" 
.
The advertising workflow ( K4_Advertisement_workflow) type need to be "Layout" .
The advertising file workflow ( K4_Advertisement_File_workflow) type ned to be "Advertisement" 
.
To upload the advertising files is important to add the file extensions needed (like .pdf, .jpg and .jpeg) in the publication channel used.
The layout templates, ad templates and all the ads materials, they have to be associated in K4 to the relative workflow or else they won't be found.
Remember, every task and status in created in K4 workflows must be enabled to the category in wich the TIMONE System user (K4_user) is contained.
E' importante ricordare che ogni task e stato che viene creato nei workflow di K4 deve consentire tutti i diritti all'utente utilizzato da TIMONE System altrimenti non potrà essere seguito correttamente.
Editorial Status
K4 layout workflow statuses have to be synchronized through the TIMONE Administration page Production > Mapping of the Workflow statuses with the TIMONE System Editorial Statuses. This page allow you to match the statuses between the two systems whithout making any change to the original configuration.
Sections
Section names in TIMONE System must correspond exactly to the ones in K4.
One of the defined section will be dedicated to ads, this section name need to be written in the K4_AdvSection configuration.
Templates
All the layout templates created in InDesign have to be assigned to the right publication, issue and section and they must have the same name set in the TIMONE System Administration page Production > Layout Templates.
The advertisement templates are simple empty pages, but they have to be called in this specific way: "ADV_<materialformat>" where material format is the exact name of the material format used for the ad.
The user need to set the configuration K4_Advert_name that defines the rule used to build the name of the adv layouts in the production system.
The user can build the name using the following patterns:
#publication# - name of the publication;
#issue# - name of the issue;
#edition# - name of the edition (if enabled and the name is different than “*”);
#page# - number of the page where the ad placeholder is allocated (1 digit);
#page??# - number of the page where the ad placeholder is allocatedv (2 digit);
#page???# - number of the page where the ad placeholder is allocated (3 digit);
#jobticket# - job ticket number (just if the booking is placed on the adv format);
#pubCod# - publication ERP code;
#folio# - folio number of the page where the ad placeholder ad is allocated;
#idLayProd# - production ID layout (if present);
#customer# - booking customer name (just if the booking is placed on the adv format);
#product# - booking product name (just if the booking is placed on the adv format);
#format# - adv format code;
#formattext# - adv format notes (if present);
#uid# - univocal ID (suggested to avoid the creation of already existent names).
