Paid media: extend budgetType and status enums for Adobe DSP
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 69/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript
- Domain
- data
Research direction
Find the schema definitions for the listed Core Paid Media Metadata and Core Paid Media Campaign Details fields and read how their existing enums, meta:enum/meta:enumId labels, en-US localization, and examples are represented. Add weekly and monthly for both budgetType fields and scheduled for metadata.status, preserving existing values and the deprecated status of metadata.budgetType. Done when schema examples cover the new values and existing values remain unchanged.
Written by the indexing model from the issue text.
Description
Problem
Adobe DSP paid media data includes weekly and monthly budget types and a scheduled entity status, but the paid media field groups can't hold these values: budgetType and status are closed enums (hard enum), so records using them are rejected.
| XDM field | Missing values |
|---|---|
paidMedia.metadata.budgetType (Core Paid Media Metadata, deprecated field) |
weekly, monthly |
paidMedia.campaignDetails.budgetSettings.budgetType (Core Paid Media Campaign Details) |
weekly, monthly |
paidMedia.metadata.status (Core Paid Media Metadata) |
scheduled |
Proposal
Add the values above to the existing enums, with a label for each in meta:enum / meta:enumId, en-US localization, and example coverage. This only adds values: existing values and the deprecated status of metadata.budgetType are unchanged. Non-breaking.
- Dominant language
- JavaScript
- Stars
- 266
- Forks
- 385
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 12
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from adobe/xdm
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 70/100
521xueweihan/HelloGitHub#4133 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
c1overzz/dsh-bili-scroll#145 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
templates/plan.md lista o agente "Tracer", mas o pacote não inclui nenhum skill/agente com esse nomeOpen
Difficulty 2/5 1-3 hours Newbie friendliness 82/100