This document covers issues with marking or unmarking assets for publish.

How do I set up asset activation using metadata?

Create a user-defined metadata field named activation. For more information, see User-Defined Fields.

  1. Make sure to set it as active, and upload an image or select existing image.
  2. Double-click the image, enter the activation date and time. Alternatively, select the images, choose File > Import Metadata, and then click Generate. 
  3. Copy the metadata to local text editor.
  4. Edit the document to contain the following:
    1. ipsid activation
    2. Sample line:
    3. Ipsid activation 
    4. myImageName 2016-07-25 16:00:00 
  5. Save as a tab-delimited text file and upload it to SPS.
    1. If the image was already published, and the activation time is in the future, SPS shows it as unpublished.
    2. If the image was unpublished already, mark it as published. SPS shows it as unpublished if the activation is in the future.

When I view the Last Published field for my asset in the detail view of SPS, it lists my asset as not published. Why is that?

The publish flag is not set.

If you are using Image Rendering, compare the upload or last modified time stamps for the asset to the time stamp of the last relevant publish. If the asset was uploaded or marked for publish after the last publish began, it would not have been included in the publish list. Make sure that the asset is marked for publish, and then run the IR publish job.

The asset is a non-Image Serving asset. The "Last Published" field uses a req=exists request to check for the asset's availability on the Image Servers. This request type is not supported for Image Rendering at this time, so IR assets, such as Vignettes and Material images, are always listed as Not Published, regardless of whether the asset is published.

The server name listed under SPS Setup isn't the correct host name for the servers your assets publish to. Contact Tech Support for assistance.

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy