Inventory (UXPROD-785)

[UXPROD-137] Move Holdings and/or Items Created: 18/Jan/18  Updated: 23/Mar/21  Resolved: 04/Nov/20

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q3 2020
Parent: Inventory

Type: New Feature Priority: P3
Reporter: Cate Boerema (Inactive) Assignee: Stephanie Buck
Resolution: Done Votes: 0
Labels: cf_candidate, inventory, metadatamanagement, mm-review, po-mvp, round_iv
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File 1-Instance-Resultlist (2).png     PNG File 10-Instance-Modal-Confirm (2).png     PNG File 11-Instance-Success.png     PNG File 12-Instance-Dropdown.png     PNG File 13-Instance-Left-Edit-Cancel.png     PNG File 14-Instance-Left-Close.png     PNG File 15-Instance-Full-Screen.png     PNG File 16-Instance-3-Pane.png     PNG File 2-Instance-Actions-Open (2).png     PNG File 3-Instance-Move-Items (2).png     PNG File 4-Instance-Drop-Items (2).png     PNG File 5-Instance-Dropped-Success (2).png     PNG File 6-Instance-Move-To-Another (2).png     PNG File 7-Instance-Modal (2).png     PNG File 8-Instance-Grab-Items (2).png     PNG File 9-Instance-Move-Items (2).png    
Issue links:
Defines
defines UIIN-1092 Spike: DnD for Transfer/Relink Holdin... Closed
is defined by MODINV-357 Can't move item between holdings on a... Closed
is defined by UIIN-1225 Error message when trying to view an ... Closed
is defined by MODINV-308 Create Move schema Closed
is defined by MODINV-309 API inventory/items/move for items Move Closed
is defined by MODINV-310 API inventory/holdings/move for holdi... Closed
is defined by MODINV-329 Move: endpoints invalid status code Closed
is defined by UIIN-1097 Move items between holdings Closed
is defined by UIIN-1098 Select and move holdings with items o... Closed
is defined by UIIN-1101 Move and confirm items and holdings o... Closed
is defined by UIIN-1103 Show two instance records as a split ... Closed
is defined by UIIN-1111 Continue working in Inventory after m... Closed
is defined by UIIN-1112 Action menu view source in split scre... Closed
is defined by UIIN-1116 Action menu edit in split screen inst... Closed
is defined by UIIN-1120 Moving holdings and items permissions Closed
is defined by UIIN-1127 Drag and drop accessibility Closed
is defined by UIIN-1140 Merge&Retest -> Select and move holdi... Closed
is defined by UIIN-1141 Merge&Retest -> Move items between ho... Closed
is defined by UIIN-1152 Move (right to left) and confirm item... Closed
is defined by UIIN-1186 Move items/holdings error message Closed
is defined by UIIN-1226 Confirm items before moving to differ... Closed
is defined by UIIN-974 Relink items between holdings or hold... Closed
Gantt End to Start
has to be done before UXPROD-1647 Theme: Ability to maintain relationsh... Open
Relates
relates to CHAL-96 Relink items between holdings and hol... In Progress
Epic Link: Inventory
Analysis Estimate: Medium < 5 days
Analysis Estimator: Charlotte Whitt
Front End Estimate: Jumbo: > 45 days
Front End Estimator: Niels Erik Nielsen
Front-End Confidence factor: Low
Back End Estimate: XXL < 30 days
Back End Estimator: Cate Boerema (Inactive)
Estimation Notes and Assumptions: Filip envision a rather advanced feature using drag and drop for bulk moving items between holdings. This UI feature has been partly implemented in the Request app. Develop of a dual screen look up will most likely be work which will involve John Coburn and his team.
Development Team: Firebird
UX Lead: Kimie Kester
PO Rank: 104.5
PO Ranking Note: Aligned PO rank with the Calculated Total rank.
Rank: Chalmers (Impl Aut 2019): R2
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): R4
Rank: GBV (MVP Sum 2020): R2
Rank: Grand Valley (Full Sum 2021): R1
Rank: hbz (TBD): R4
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R1
Rank: Leipzig (Full TBD): R4
Rank: Leipzig (ERM Aut 2019): R5
Rank: MO State (MVP June 2020): R4
Rank: TAMU (MVP Jan 2021): R1
Rank: U of AL (MVP Oct 2020): R1

 Description   

Goal: Ability to move (transfer) attached records and maintain existing relationships
When moving holdings to another instance, all associated items have to be transferred as well

Use Case: As a cataloger I want to move holdings and all associated items from a temporary record to the newly created full record.

Bulk moving items and holdings. Ease of linking/relinking bib/holdings/item data. Part of the refined UX design of Inventory. Drag and drop is one possible solution.

Spec and requirements - DONE (3/20/2020):
Slide deck with updated UX mock ups: https://docs.google.com/presentation/d/1E_tCI2zwUnJi9cCEJ9JBPR0SDZ8Z-ivQb5IXK8vSdEs/edit#slide=id.p
Working group established (2/6/2020): Lisa McColl (Lehigh), Lisa Furubotten (TAMU), and Natascha Owens (uchicago).
Dependencies with other apps; e.g. Request, Orders, Circulation module, MARCcat, etc - listed: https://docs.google.com/presentation/d/1E_tCI2zwUnJi9cCEJ9JBPR0SDZ8Z-ivQb5IXK8vSdEs/edit#slide=id.g7f18bee7d3_0_108

https://discuss.folio.org/t/card-file-box-arrow-right-card-file-box-bulk-moving-items-or-holdings/1401/4

Note:
FE high-level estimate: >50 man-days
FE high-level duration: ~4-5 sprints



 Comments   
Comment by Lisa McColl [ 20/Jun/18 ]

Is this referring to the system having the ability to transfer holdings and/or items from one bibliographic record to another, or does it refer to changing locations for holdings and items? The discuss post above references both cases. Each are distinct.

Comment by Cate Boerema (Inactive) [ 21/Jun/18 ]

Thanks for your question, Lisa McColl. This one covers the ability to transfer holdings and/or items from one bibliographic record to another.

We have a separate feature for bulk editing of records: UXPROD-120 In Progress

Comment by Cate Boerema (Inactive) [ 22/Mar/19 ]

Removing all but the essential features from the Q2 2019 Core Functional team backlog. After we've run the estimates through the cap plan, we may find we can pull in more.

Comment by Lisa Sjögren [ 22/Aug/19 ]

Hi! Is there a separate issue for relinking items between holdings (manually and/or in bulk), or would that be included in this one?

Comment by Charlotte Whitt [ 23/Aug/19 ]

Hi Lisa Sjögren - this is also covering relinking of items.

Transfer relink is a rather small feature while in the architecture, we have build in references between instance > holdings > items.
so if you move a given holdings record, the associated items will follow. Or you move items to another holdings record/or a new holdings record, then the new associated linking with ID references is build: instance > (new) holdings > item.

See also:

  • UXPROD-1625 Draft Order/sequence of items within a holdings record. Add and (manually) re-order Item records
  • UXPROD-1635 Draft Order/sequencing of holdings on an instance record. Re-order Holdings records
Comment by Charlotte Whitt [ 23/Aug/19 ]

Hi Cate Boerema - the estimates looks a bit weird?
They need to be revisited.

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

Hi Charlotte Whitt, there is a feature UXPROD-1647 Open which seems to relate to this. As I read that feature, it seems like it's basically saying "don't break FOLIO when implementing transfer/relink of holdings or items" Is that right? If so, I think we can probably just make a note in this feature to make sure that relationships are maintained when re-linking and close that feature as a duplicate. Thoughts?

Comment by Charlotte Whitt [ 08/Apr/20 ]

Hi Cate Boerema - what are the changes to get this feature in for Qs-2020.

As you know:

I can easily write up all underlying jira stories. But no point in doing this work, if this feature is not in the pipe line before 2021, 2022 ...

CC: Lisa Sjögren lew235 Kirstin Kemner-Heek Felix Hemme Mike Gorrell Mark Veksler

Comment by Charlotte Whitt [ 08/Apr/20 ]

UXPROD-1647 Open is incorporated into UXPROD-137 Closed - which means following dependencies to be addressed:

Ability to maintain relationships between other apps when holdings/items are moved from one instance to another, and Items (with all existing item states) can be moved:

  1. Request (also the Request statistics)
    • Item level request
    • Title level request
  2. Orders (this is important - will loop in Dennis. AppInteraction SIG - will loop in Martina Schildt)
  3. Existing loan, statistics for check out (Chalmers comment)
  4. MARCcat (check with Tiziana)
    • MFHD - moving holdings (Duke, Alabama ...)
  5. SRS (check with AM-B)
  6. Course Reserve (check with Kelly)

This require:
Review each item state, and make sure a correct context specific warning/action note etc. is populated, e.g. if the item is checked out, then a note for technical service staff

Comment by Marc Johnson [ 08/May/20 ]

Does this feature include managing the impact of transfers on (dependent) associated records like requests, orders etc?

Comment by Marc Johnson [ 08/May/20 ]

Use Case: As a cataloger I want to transfer holdings and all associated items from a temporary record to the newly created full record.

This question might reveal how naive I am about cataloguing practices in libraries. If the full record is newly created, could that information have instead been added to the temporary record, meaning no transfer is required?

Or does the temporary record often represent more than one bibliographic resource, and this process involves splitting up many heterogenous resources up?

Comment by lew235 [ 11/May/20 ]

That's not a naive question, Marc Johnson. In many cases yes, the new record can simply overlay the existing temporary record and no transfer would be required. But there are cases, as you describe, where the temporary record represents more than one bibliographic resource. There are also cases where a record was created for the order but the item belongs on an existing bibliographic record. And of course, the cases where the item has simply been attached to the wrong record and a correction needs to be made.

Short answer, yes, the associations to other records should be maintained.

Comment by Marc Johnson [ 12/May/20 ]

lew235

there are cases, as you describe, where the temporary record represents more than one bibliographic resource. There are also cases where a record was created for the order but the item belongs on an existing bibliographic record.

Thanks, that context really helps with my understanding.

Short answer, yes, the associations to other records should be maintained.

Cate Boerema Stephanie Buck lew235 Is that part of the scope of this feature?

Comment by Stephanie Buck [ 12/May/20 ]

Marc Johnson yes, that's in the scope of this feature.

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