## 5.11 May Cross Sync
### 1610 Follow Up from Backlog Refinement
* Once 1610.1 merges, the sub history table will populate a downloadable error report.
* F/U call to discuss approach to manage user experience ahead of deploying the feature, key notes:
1. Managing user experience, utilizing verbiage to convey messaging of beta feature and set expecations accordingly. Only presnting XYZ errors and will have more robust validation than legacy system, need to have clear messaging they need to continue correcting errors off the legacy reports and the downloadable TDP report will be incomplete until parsing finishes.
2. OFA aligned in low tech lift approach and managing comms via some form of wording in the column header/file name/file content itself - would love UX input here
3. Potential for some type of e-mail communication needed to introduce the beta feature / continue to keep up to date with roll outs as the report matures
4. ID a subset of users to target for further research

### 2509
* tagged UX in ticket for review, main takeaways from BR:
* Repurpose existing template, update CTA to reflect research prototype, migrate to figma or html
* Key note: replacing data submission confirmation email due to minute time gap between, Lauren is OK with latency
### Field Name follow up
* UX looking to confirm field names that are currently being generated for item numbers before proceeding with a mapping of preferred item number descriptors/field names.
* 132 looked to update formatting of a few field names but not alter any language
* Code base looks to be pulling descriptor which can be long
* Should be an easy lift to implement UX's research recommendations for field names post, assuming 1:1 mapping vs item number.

### UX Sprint Planning
* Priority items for Spring 72