UI Customization
(UXPROD-1732)
|
|
| Status: | Draft |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | UI Customization |
| Type: | New Feature | Priority: | TBD |
| Reporter: | Brooks Travis | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | acquisitions, erm, platform, resourceaccess, usermanagement | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||
| Epic Link: | UI Customization | ||||||||||||||||
| Development Team: | None | ||||||||||||||||
| PO Rank: | 0 | ||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R4 | ||||||||||||||||
| Description |
|
Current situation or problem: Addresses are hard. While highly-structured data is generally preferable, addresses are one data type that do not lend themselves to a one-size fits all approach. To account for address data that does not fit into the provided fielded data structure, we should provide a free-text field (presented as a text area form element in the UI) as part of all "address" records/record objects in FOLIO. In scope
Out of scope
Use case(s)
Proposed solution/stories
Links to additional info Questions
|