GO Loader Aviation 1.2 is here! Take a look at what's new.
Skip to end of metadata
Go to start of metadata

What is GO Publisher Workflow?

GO Publisher Workflow is the enterprise data publishing system of the GO Publisher product suite and it can be easily orchestrated within a Service Oriented Architecture. As a configurable series of web services, GO Publisher Workflow can be run standalone or integrated into existing data ordering systems.

Capable of delivering large volumes (gigabytes) of XML and GML data to large numbers of data consumers, GO Publisher Workflow features:

  • Configurable data ordering parameters to customise published data (including data selection, data chunking, individual file compression, and archive generation),
  • Data validation (XML schema validation, and business rule (schematron) validation)
  • Metadata publishing,
  • XSLT transformation,
  • Multiple options for downloading and accessing published data.

System Integration and Set Up

GO Publisher Workflow is deployed as two WAR files on an application server. When integrated into an existing system, it can be controlled through Admin, Management, and Download Application Programming Interfaces (APIs). Alternatively, if GO Publisher Workflow is run standalone, it can be controlled using Admin and Management web browser user interfaces.

See GO Publisher Workflow Pre-Requisites for supported application servers and set up requirements.

See GO Publisher Workflow Deployment Steps for how to deploy GO Publisher Workflow on your application server.

GO Publisher Workflow Glossary of Terms

Product

Built on the core GO Publisher translation engine, GO Publisher Workflow uses the XML schema translations in your GO Publisher project (.gpp) file to transform the data in your database into XML or GML. A GO Publisher Workflow 'Product' refers to a directory which is set up based on your GO Publisher project file and publishing requirements. Products are uploaded to the system using the Admin Console or Admin API, and you can deploy products simultaneously. GO Publisher project files are created in GO Publisher GO Publisher Desktop.

Default publishing settings which can be configured in your product include:

  • Validation
  • Metadata

  • Data transformation
  • Compression

See GO Publisher Workflow Product Setup for how to set up and configure your products.

Job

Data ordering parameters are configured in GO Publisher Workflow 'Job' XML files. Each job references a 'Product', and can contain customised ordering parameters. Jobs are uploaded and run through the system using the Management Console or Management API.

Entire database exports can result in millions of features and gigabytes of data. To facilitate the export of such large data volumes GO Publisher Workflow can publish data according to three export parameters:

  • Data Selection – to identify which data is to be exported based on a geographic, attribute, feature ID, temporal, or SQL parameter query;
  • Data Chunking – to split a selection into manageable files for data exchange based on geographic, attribute, or file size;
  • Compression – of individual files (GZip compression), or all output files (ZIP archive generation).

By combining all export parameters, GO Publisher Workflow is capable of performing complex export scenarios. For example, GO Publisher Workflow is able to select all data in a user defined geographic area (geographic selection), where the result is written into files based on country geographic border (geographic chunking), and each with file size is no greater than 5Mb (file size chunking) after they have been WinZip compressed (archive generation).

See GO Publisher Workflow User Guide for how to set up and configure your products.

Data Download

Once you've uploaded and started your job (and the selection, chunking, compression, validation, transformation, and metadata generation is finished), you can download your published data and metadata from the Management Console, or Download API.

In addition to traditional download methods GO Publisher Workflow also supports a ‘push’ mechanism, whereby data can be pushed into a 3rd party content management system or database. Publishing to an external database can be configured in your product.

Further Reading

Now that you're familiar with the basic concepts of GO Publisher Workflow, continue on to GO Publisher Workflow Pre-Requisites to find out the necessary requirements for deploying GO Publisher Workflow.

  • No labels