Inventory (UXPROD-785)

[UXPROD-133] Implement pane header dropdown Created: 18/Jan/18  Updated: 16/Sep/20  Resolved: 24/Jan/19

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q4 2018
Parent: Inventory

Type: New Feature Priority: P3
Reporter: Cate Boerema (Inactive) Assignee: Charlotte Whitt
Resolution: Done Votes: 0
Labels: Q42018-will-split, inventory, metadatamanagement
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to STCOM-353 Inventory: Implement Pane header drop... Closed
relates to STCOM-374 Requests: Implement Pane header dropd... Closed
relates to STCOM-396 Inventory: Implement Pane header drop... Closed
relates to UIU-754 Users App: Implement Pane header drop... Closed
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): R2
Rank: 5Colleges (Full Jul 2021): R1
Rank: GBV (MVP Sum 2020): R4
Rank: Lehigh (MVP Summer 2020): R1
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 (Instance, Holdings, Item)

Delete functionality will be implemented when introducing the refined UX of Inventory. A drop down menu in the top bar ( UIIN-354 Closed ).

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:

  1. InstanceStorageAPI.java
  2. HoldingsStorageAPI.java
  3. ItemStorageAPI.java

Out of scope:

  1. Mark for deletion ( UXPROD-1363 Open )
  2. Prevent delete-all (wipe all data in Inventory).


 Comments   
Comment by Cate Boerema (Inactive) [ 01/Oct/18 ]

Charlotte Whitt, it would be great if you could create some quick stories for this for the deletion of inventory records. I see you have a story linked to this feature ( UIIN-272 Closed ) but it covers way more than delete (which is the scope of this feature and all that is needed by Chalmers for Q4). I think we just need 3 simple stories: Delete instance, Delete holding and Delete item. The pane header itself should not be too complicated, as we already have a reference implementation in Requests.

Comment by Charlotte Whitt [ 01/Oct/18 ]

@ cate - yes, I'll do that

Comment by Cate Boerema (Inactive) [ 20/Nov/18 ]

Charlotte Whitt we may need to tag this as at risk.

Comment by Charlotte Whitt [ 20/Nov/18 ]

Today's Slack chat conversation with Lisa Sjögen, Chalmers:

Charlotte Whitt [1:00 PM]
Hi @Lisa - How are you :slightly_smiling_face: ... I have a quick Inventory question
We're working on defining Deletion and Mark for deletion of Inventory records (Instance, Holdings, Item)
And here I'm not sure, if Chalmers do: Mark for deletion. Or Deletion would be sufficient.
The idea with Mark for deletion is, that a cataloger, who do not holds the permission to do a deletion, is able to just do 'Mark for deletion' - set a boolean check mark. And then the cataloger with super power and the permission to perform deletion, will go in and filter on all records marked for deletion, and then delete them one-by-one, and later in bulk mode.

Lisa Sjögren [1:18 PM]
Earlier, we've used Mark for deletion for bib records: partly so that a super cataloger could control the records, partly because we needed to send the record marked for deletion to our Discovery before actually deleting it.

These days, however, we have another way of communicating deletions to our Discovery and trust the staff to delete responsibly, so just delete the records right away.

So the short answer is that yes, just being able to delete should be sufficient.

Maybe @Theodor could weigh in on whether this would work with EDS and OAI-PMH?

Comment by Cate Boerema (Inactive) [ 11/Jan/19 ]

Hi Charlotte Whitt, it's end of quarter and this feature looks incomplete. I think you will need to split it:

  1. Tag this feature with "split"
  2. Create a new feature for the unfinished work and make a note at the top of the feature that it was split out from this one (this was requested by the early implementers)
  3. Move any unfinished stories into the new feature
  4. Mark this feature complete
  5. Make a note explaining what was split out in the weekly status report: https://folio-org.atlassian.net/wiki/display/PC/FOLIO+Q4+2018+Weekly+Status+Report

Thanks!

Comment by Charlotte Whitt [ 21/Jan/19 ]

Hi Cate Boerema - Some backend development work is done, but the implementation of UXPROD-133 Closed is not done. I suggest we move the full story to Q1, 2019 or Q2, 2019. Please note this is ranked as 'Go live' by Chalmers.

Implementation of the drop down in the navigation bar, and mark records for deletion should be quite easy to fix.

CC: Niels Erik Nielsen

Generated at Fri Feb 09 00:06:01 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.