product-mapping

The product-mapping section of a cue-print processor performs two functions:

• It selects which incoming events will be handled, based on publication and content type

• It defines how to upload the content items referenced by these events, based on the same criteria

    product-mapping:
      - publication:
          - tomorrow-today
          - living-tomorrow
        content:
          - print
          - print-story
        assets:
          image:
            - picture
            - graphic
      - publication:
          - tomorrow-online
        content: []
        assets:
          image:
            - picture
            - graphic

The product-mapping section contains an array, each element of which contains the following entries:

publication (required)

An array of publication names. Only content from these publications will be processed.

content (required)

An array of content type names. Only content of these types will processed. You should only specify "text" content types here (i.e. stories not images, graphics, videos etc.)

assets (required)

Contains the asset type name image, which in turn contains an array of content type names. You should only specify image/graphic content types here. In future versions of CUE Zipline, other asset types such as videos, documents and spreadsheets may be supported.

If an event matches both a publication and a content entry in the same group, then the content item it references will be converted to a CUE Print text and POSTed to the CUE Print server. If an event matches both a publication and an assets entry in the same group, then the content item it references will be converted to a CUE Print asset of the appropriate type and POSTed to the CUE Print server. In the example shown above for example, print and print-story content items that belong to either tomorrow-today or living-tomorrow will be POSTed to the CUE Print server as texts. picture and graphic content items that belong to the same publications, however, will be POSTed to the CUE Print server as image assets.

If the product mappings are the same for all publications, then the array may have only one entry (as in the example shown above). If, however different groups of publications require different mappings, then multiple entries will be needed.