forked from ave-dcd/dcd_mapping
-
Notifications
You must be signed in to change notification settings - Fork 0
Implement a mapped variant status taxonomy #88
Copy link
Copy link
Open
Labels
app: backendTask implementation touches the backendTask implementation touches the backendapp: databaseTask implementation requires database changesTask implementation requires database changesapp: mapperTask implementation touches the mapperTask implementation touches the mappertype: enhancementNew feature or requestNew feature or request
Metadata
Metadata
Assignees
Labels
app: backendTask implementation touches the backendTask implementation touches the backendapp: databaseTask implementation requires database changesTask implementation requires database changesapp: mapperTask implementation touches the mapperTask implementation touches the mappertype: enhancementNew feature or requestNew feature or request
Replace the binary mapped/failed outcome with explicit and consistent status strings. Proposed minimal taxonomy based on what we've seen so far:
Different status codes can route to different curator triage requirements, and the mapping table can aggregate counts per status to surface patterns across a target's variants.