An automatic template workbook generation, to be used as a semi-automatic publication guideline, strikes as a middleground between a fully automatic pipeline (which could be really dangerous, when failing) and a fully hand-written one.

Thus, near field we have;

In a first simple script - take a couple of predefined template files, with arguments specifying

• publication number
• publication type
• smhi data directory
• node staging area
• node final path

and inject the output of the .out files from

• Receive checks
• Variable checks

Our end-game is thus;

• Generate from a template, based on http://localhost:4000/IS-ENES/2020-04-22-CMIP6_data_publication_request_70/
• Using results from receive and variable checks
• Suggesting a default staging area (into which to rsync the data)
  • Add option to specify
• Suggesting a default final path
  • Add option to specify it
• Possibly even parsing in an e-mail body supplied via sftp or the like to the node (to be done later, AI fun)

First steps are to create a .md template generator based on the receive and variable checks.

A later feature is that this could also be e-mailed from tetralith to the agent, when ready (if no errors resulted).