Inventory
(UXPROD-785)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Inventory |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Charlotte Whitt | Assignee: | Charlotte Whitt |
| Resolution: | Done | Votes: | 0 |
| Labels: | call_number, inventory, metadatamanagement, po-mvp | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||
| Epic Link: | Inventory | ||||||||||||
| Analysis Estimate: | Very Small (VS) < 1day | ||||||||||||
| Analysis Estimator: | Charlotte Whitt | ||||||||||||
| Front End Estimate: | Small < 3 days | ||||||||||||
| Front End Estimator: | Niels Erik Nielsen | ||||||||||||
| Front-End Confidence factor: | Low | ||||||||||||
| Back End Estimate: | Small < 3 days | ||||||||||||
| Back End Estimator: | Niels Erik Nielsen | ||||||||||||
| Estimation Notes and Assumptions: | Outstanding questions:
* Implemented as a search index or as a persisted field containing the normalized version of the call number? * Hard-code normalization rules or configurable? |
||||||||||||
| Development Team: | Prokopovych | ||||||||||||
| Kiwi Planning Points (DO NOT CHANGE): | 5 | ||||||||||||
| PO Rank: | 40 | ||||||||||||
| Rank: Chicago (MVP Sum 2020): | R4 | ||||||||||||
| Rank: Cornell (Full Sum 2021): | R4 | ||||||||||||
| Rank: Duke (Full Sum 2021): | R2 | ||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R2 | ||||||||||||
| Rank: GBV (MVP Sum 2020): | R2 | ||||||||||||
| Rank: hbz (TBD): | R2 | ||||||||||||
| Rank: MO State (MVP June 2020): | R2 | ||||||||||||
| Rank: TAMU (MVP Jan 2021): | R2 | ||||||||||||
| Rank: U of AL (MVP Oct 2020): | R2 | ||||||||||||
| Description |
|
*This feature capture enhanced work on Inventory search on Call number, normalized (in the Holdings and the Item segment). This is post-mvp work. The elements Call number, and Call number type are implemented in the Holdings and Item records. Use cases: Examples in scope:
Documentation:
|