Material Flow Variations explained - Internal

Short Summary

1. PDF → WA → Prenly
2. PDF → FTP (rats) → WA → Prenly
3. PDF+XML → FTP (rats) → WA (no clicking) → Prenly

Option 1 - Standard procedure 

The customer uploads their publications to Webarch. The issue will then be clicked in by the operators. Depending on the number of newly uploaded publications, this can result in queues, which may cause delays. Once processed, the issue will be exported to Prenly.

It is recommended for the customer to upload the publication as early as possible. When uploading the publication ahead of time the date should be set to the preferred future date. When the publication has been imported from Webarch into Prenly, a future publication date will be indicated by a yellow arrow. The issue will automatically be published and the arrow will turn green on the set publication date. 

Ideal for: This procedure works fine for customers who publish less frequently than daily. 

Option 2 - PDF routing to Webarch 

The customer uploads their publications to an FTP server provided by the content conversion team. Publications can be sent either as a single PDF file or as individual page-by-page PDFs. The export to the FTP can be automated from the customers publishing tool. 

How to set it up 

• Fill in the Material sheet or ask the customer to fill it in (in case of just one Title or a simple setup, the sheet is not necessary, inform about the naming convention instead)
• Create a card in the Content Conversion board and attach it to the customers onboarding board, including the following information
• Include the Material sheet or the information about the naming convention
• Create checklist
• FTP created and sent to the customer
• Titles added in WA
• Material rigged & routed from FTP to WA by CC
• Final font review done by HD
• Import to Prenly / Import has been set up, operators are informed
• After CC has created a Rats FTP, send the credentials to the customer 
• Helpdesk: Add Titles in Webarch 
• The customer should now upload example material to the FTP for each title 
• Material rigged & routed from FTP to Webarch by CC
• Helpdesk: Final font review

Note: We do not advertise this solution however can offer it to clients if they request it. 

Option 3 - XML import to Prenly 

The third option can only be offered to customers who have four or more different titles with daily publications! This is due to the high amount of effort and time needed to set it up, which makes the implementation very costly. 

For newspapers publishing daily, delays caused by queues in Webarch can be problematic, due to tight publishing deadlines. For these customers we can set up an XML import. In this case the customer will upload both PDF and XML files to the FTP server. To the agreed upon time, these files will be directly imported to Prenly without having to be edited in Webarch. The XML files include information about headlines, images and text boxes, enabling the reading mode without any manual processing needed.

This can be beneficial if several people work on parts of the paper simultaneously. Whenever someone has completed their work, they can already upload their pages to the server. 

The set up for this material differs depending on the customer's publishing tool. So far we have created a flow with the tools Newspilot, Saxo, Aptoma, Roxen and Anygraaf. Setting up a flow for another customer using the same tool may be easier but could still vary heavily depending on the tool’s version.