adobe / adobe/xdm

Adding additional reporting attributes and group the another 2 we added recently together into a new object.

Open
#1,817 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
266
Forks
380
Avg merge
5d 8h
Merged PRs (30d)
9

Description

## What are the schemas that are affected by the issue
https://github.com/adobe/xdm/blob/master/extensions/adobe/experience/decisioning/option-detail.schema.json

We recently added selectionID and selectionType attribute under below issue.
https://github.com/adobe/xdm/issues/1806

As we realize we need to additional attributes (_selectionName_ and _selectionVersion_) and ranking information, we would like to create a new object **item selection detail** under __experience.decisioning.propositions.items_ to hold all the new decisioning information.

## What are examples of products that are impacted by the issue
Adobe Offer Decisioning.
These are the additional optional attributes for new reporting capability. There is no impact to the existing application.

After the changes, the schema under _items_ should be:

Parent Object node: _experience.decisioning.propositions.items
`
"xdm:itemSelection": // new schema object
{
"xdm:selectionDetail": { // new schema object
"xdm:strategyID": "xcore:selection-strategy:185c87454fb2e35a",
"xdm:strategyName": "most popular category",
"xdm:type": "selectionStrategy",
"xdm:version": "xcore:selection-strategy:185c87454fb2e35a_1"
},
"xdm:rankingDetail": { // reference the existing strategy-details object
"xdm:strategyID": "4ajr78banuUg4Og6or3LFa",
"xdm:algorithmID": "1",
"xdm:step": "rankingAIModel",
"xdm:trafficType": "random"
}
}
`

Contributor guide

Open the contributing guide

Research direction

Start with extensions/adobe/experience/decisioning/option-detail.schema.json and inspect the schema at _experience.decisioning.propositions.items. Compare the existing strategy-details object with the requested itemSelection, selectionDetail, and rankingDetail structure. Done means the optional selection and ranking attributes are represented there without changing existing application behavior.

Written by the indexing model from the issue text.

Assessment

Domain
data
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.