Simplification of media schema
- 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
* advertisingdetails.schema.json
* advertisingpoddetails.schema.json
* chapterdetails.schema.json
* errordetails.schema.json
* playereventdetails.schema.json
* playerstatedata.schema.json
* qoedatadetails.schema.json
* sessiondetails.schema.json
* mediacollectiondetails.schema.json
* experienceevent-mediacollection.schema.json
* experienceevent-mediareporting.schema.json
* experienceevent-mediacollectiondownloaded.schema.json
## What are examples of products that are impacted by the issue
* Adobe Media Analytics
Internal JIRA issue: https://jira.corp.adobe.com/browse/VA-4808
High-level changes:
* create datatypes to be used in 2 fieldgroups: mediacollection and mediareporting
* deprecate the media.schema.json and use the new schemas for a better experience for our clients
Contributor guide
Research direction
Start by reviewing the listed schema files and the linked JIRA context; no tests or entry points are identified. Map the proposed datatypes to the mediacollection and mediareporting fieldgroups, then verify that media.schema.json is deprecated and the affected schemas use the new replacements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- data
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100