Features that will be implemented to enhance FOLIO's ability to support consortia (Phase 1) (UXPROD-4049)

[UXPROD-4210] Duplicate a shared or local Instance (BE work) Created: 17/Apr/23  Updated: 08/Nov/23  Resolved: 08/Nov/23

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Poppy (R2 2023)
Parent: Features that will be implemented to enhance FOLIO's ability to support consortia (Phase 1)

Type: New Feature Priority: P1
Reporter: Dennis Bridges Assignee: Ann-Marie Breaux (Inactive)
Resolution: Done Votes: 0
Labels: LC1, consortia, ecs, epam-folijet, inventory, metadatamanagement, needs-be-estimate, needs-ui-estimate
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
defines UXPROD-785 Inventory In Progress
Relates
relates to UIIN-2458 Duplicate Instance Closed
relates to UXPROD-4329 Duplicate a local Instance as a share... Closed
relates to UXPROD-4209 Inventory UI changes needed for ECS Closed
Release: Poppy (R2 2023)
Epic Link: Features that will be implemented to enhance FOLIO's ability to support consortia (Phase 1)
Front End Estimate: Very Small (VS) < 1day
Front End Estimator: Mariia Aloshyna
Front-End Confidence factor: 90%
Back End Estimate: Small < 3 days
Back End Estimator: Kateryna Senchenko
Back-End Confidence factor: 80%
Development Team: Folijet
PO Rank: 107
Rank: Cornell (Full Sum 2021): R5

 Description   

This feature involves 2 Instance action menu options - duplicate as local and duplicate as shared. Duplicate as local is being covered by UIIN-2458 Closed .

For now, if a library wants to duplicate an instance and make it shared, they will first duplicate it to create a local instance, and then share it.

This feature would allow for the duplicated instance to be created as shared, instead of having to promote it to shared after creation.

Clean up the description of this feature and decide if we can park it for now and tackle in a future iteration

Current situation or problem: Consortia members must have the ability to collaborate in contributing and managing cataloging records. It must be possible to manage the importing and sharing of bibliographic records at the consortia level
Start on each of 3 tenant types, with each of 4 recod types; all will be created as LOCAL Source = FOLIO, then promote to shared or use Z39.50 to update to MARC

In scope:

  • Ability to duplicate either a Local or Shared Instance to create a new Shared or Local instance (new, separate actions?)
  • Promotion of Instance duplicated as Shared to consortial tenant (This may also be covered by UXPROD-4140 Closed )

Out of scope:

Proposed stories:

  • Create new options in the Instance Actions menu
    • Duplicate as local instance
    • Duplicate as shared instance
  • Duplicate as a local instance, create Instance with source = FOLIO:
    • Shared Instances with source = MARC - Create new local Instance with source = FOLIO
    • Shared instances with source = FOLIO - Create new local Instance with source = FOLIO
  • Duplicate as a shared instance, create new Shared Instance with source = FOLIO
    • Shared instances with source = MARC - Create new shared instance with source = FOLIO
    • Shared instances with source = FOLIO - Create new shared Instance with source = FOLIO
  • Upon duplication as a shared Instance, promote Instance to consortial tenant

Questions

  • Need to confirm whether there will be separate actions to duplicate as shared or duplicate as local, or if duplication will always create a local that will then have to be shared via a separate action

No UI changes; a couple BE tasks, plus test scenarios



 Comments   
Comment by Dennis Bridges [ 30/May/23 ]

Ann-Marie Breaux can you clarify whether this feature is meant to cover duplicating a shared instance as a local instance (Ie. copy cataloging) or that this will represent the work needed to create "shadow instances" for a shared instance? Thanks!

Comment by Olamide Kolawole [ 13/Jun/23 ]

Ann-Marie Breaux In the description of this story, you mentioned that there are no UI stories. The duplication functionality right now is made possible by the UI only. So there will be UI tickets only.

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