Hi @RN

According to the ADH installation guide, the key parameters for Publisher Augmentation are as follows:

*serviceName*enablePublisherAugmentation: Enables publisher augmentation for the service.
*serviceName*applyPostsToCache: Set to true if you want to let post providers augment items in the cache instead of sending the post to the interactive provider.

*serviceName*publisherAllowedFieldList: List of FIDs to which unmanaged publishers can augment. All other FIDs are dropped
*serviceName*augRemapRefreshUpdateType: If the incoming message from an unmanaged publisher is a refresh message and if the payload contains FIDs which already exist in the item cache, an update is sent. Use this parameter to configure the updateType on the update.
· *serviceName*augRemapUpdateType: If the incoming message from an unmanaged publisher is an update message and if the payload contains FIDs which already exist in the item cache, an update is sent. Use this parameter to configure the updateType on the update.

Details of Update type can be found in the RDMUsageGuide for your API.

However, I suspect only the the first two params above would apply to your situation.

Hope this helps.

From your description It sounds like you want to do Publisher Augmentation - is that correct?

Have you referred to the ADH and ADS installation guides? They have details of the configuration parameters required to enable Augmentation.

Have you actually implemented the recommended config settings yet?

In addition to publisher augmentation, Interactive Source Blending within TREP is another option, as well as static record augmentation if all you are interested in is adding static field values to cache.