Summary:
This article covers the concept of Hub Views and how they relate to the source table of data.
If you are not familiar with Postgres views, then we would recommend having a read of this
article, but as part of the Hub implementation we will work with customers to populate Channel views. Don't panic!
What is a Hub Channel View?
In our overview article on Hub you would have seen the basic concept of the Hub architecture. Demonstrating where data from Postgres is passed into an API and displayed on the Hub page.
Channel Views are a means to craft a source table, such as Planning Applications, into a neater and more content rich form of that data. Views allow users to construct a table of data that could join various columns from a source table together into a single column, or being in multiple tables of data together, into a single table.

Example View
The below is an example view as a SQL statement for the Planning Application Channel, and is based on the source data coming from IDOX Development Control. In this instance the source tables is called development_control_polygons in a schema called datastore_uniform.
CREATE OR REPLACE VIEW gx_hub.planning_apps_latest_view AS
SELECT refval AS pln_refval,
regexp_replace(address::text, '[\n\r]+'::text, ' '::text, 'g'::text) AS pln_address,
regexp_replace(description::text, '[\n\r]+'::text, ' '::text, 'g'::text) AS pln_proposal,
concat(' Reference number ', refval, ' is the application number. ') AS pln_additional,
FROM datastore_uniform.development_control_polygons a
WHERE datemodified >= (now() - '40 days'::interval);