Inventory
(UXPROD-785)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | Q2 2019 | Parent: | Inventory |
| Type: | New Feature | Priority: | P2 |
| Reporter: | Charlotte Whitt | Assignee: | Charlotte Whitt |
| Resolution: | Done | Votes: | 0 |
| Labels: | inventory, metadatamanagement, split | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||||||||||||||
| Epic Link: | Inventory | ||||||||||||||||||||||||||||||||||||
| Analysis Estimate: | Small < 3 days | ||||||||||||||||||||||||||||||||||||
| Analysis Estimator: | Charlotte Whitt | ||||||||||||||||||||||||||||||||||||
| Front End Estimate: | Medium < 5 days | ||||||||||||||||||||||||||||||||||||
| Front End Estimator: | Niels Erik Nielsen | ||||||||||||||||||||||||||||||||||||
| Front-End Confidence factor: | Medium | ||||||||||||||||||||||||||||||||||||
| Back End Estimate: | Medium < 5 days | ||||||||||||||||||||||||||||||||||||
| Back End Estimator: | Niels Erik Nielsen | ||||||||||||||||||||||||||||||||||||
| Estimation Notes and Assumptions: | The estimate considers data integrity checks and mark-for-deletion functionality. Hard to say how much these are general issues (solved in Raml Module Builder and stripes-components for example) and how much they are Inventory work | ||||||||||||||||||||||||||||||||||||
| Development Team: | Prokopovych | ||||||||||||||||||||||||||||||||||||
| Rank: BNCF (MVP Feb 2020): | R1 | ||||||||||||||||||||||||||||||||||||
| Rank: Chalmers (Impl Aut 2019): | R1 | ||||||||||||||||||||||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R1 | ||||||||||||||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R1 | ||||||||||||||||||||||||||||||||||||
| Rank: Duke (Full Sum 2021): | R1 | ||||||||||||||||||||||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R1 | ||||||||||||||||||||||||||||||||||||
| Rank: FLO (MVP Sum 2020): | R1 | ||||||||||||||||||||||||||||||||||||
| Rank: GBV (MVP Sum 2020): | R4 | ||||||||||||||||||||||||||||||||||||
| Rank: hbz (TBD): | R4 | ||||||||||||||||||||||||||||||||||||
| Rank: Lehigh (MVP Summer 2020): | R1 | ||||||||||||||||||||||||||||||||||||
| Rank: Leipzig (Full TBD): | R1 | ||||||||||||||||||||||||||||||||||||
| Rank: Leipzig (ERM Aut 2019): | R4 | ||||||||||||||||||||||||||||||||||||
| Rank: TAMU (MVP Jan 2021): | R1 | ||||||||||||||||||||||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R4 | ||||||||||||||||||||||||||||||||||||
| Description |
|
Implement component in top navigation bar. Enable the user to delete a metadata record (Holdings, Item) Slide deck from presentation at MM-SIG 2018-10-04: https://docs.google.com/presentation/d/1iv1qM2T1uHCOx8vLAAJfmX-439ENNP7uo4yQJM8mubE/edit#slide=id.g438c473a97_0_0 Technical backend note: The Inventory database has constraints defined on Instance, HoldingsRecord and Item to prevent deletion of entities with dependent records. The database will throw an exception if such a delete is attempted, as a last backstop - see:
Out of scope:
|
| Comments |
| Comment by Cate Boerema (Inactive) [ 18/Mar/19 ] |
|
I met with Chalmers today and they felt deletion of holdings and items would be really important for go-live, as that is the point at which they will be making lots of mistakes. Instance deletion was less important because they won't be maintaining those manually in FOLIO. |
| Comment by Theodor Tolstoy (One-Group.se) [ 19/Mar/19 ] |
|
I agree Cate Boerema, there will be limited access among the staff to edit instances anyway, so removal of Instances not connected to the Union catalog could potentially for some time be performed through the API. But for Items and Holdings being able to delete is absolutely needed for Go Live. |
| Comment by Charlotte Whitt [ 25/Mar/19 ] |
|
The original feature is now split into:
CC: Cate Boerema Theodor Tolstoy (One-Group.se) Lisa Sjögren |