adobe / adobe/xdm

Define metric details outside of the data schema

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

Description

We should remove the metric details like @type and the unit from the data schema and have that described outside in the descriptors like we are for other things like identity fields. This will reduce the size of the data schema and also allow us to consistently tag up fields as metrics without them conforming to the data/measure schema like data/order/xdm:priceTotal.

## What are the schemas that are affected by the issue
data/measure
all use of data/measure

## What are examples of products that are impacted by the issue
All Adobe solutions

@kstreeter & @cdegroot-adobe

Contributor guide

Open the contributing guide

Research direction

Start with the data/measure schema and trace all use of data/measure across the affected schemas. Compare the existing descriptor treatment for identity fields and the data/order/xdm:priceTotal example; the work is done when metric details are consistently described outside the data schema and affected uses are updated.

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
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.