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

[UXPROD-4140] Allow user to promote a local Instance to be a shared consortial instance, plus shared/shadow instance logic (BE work) Created: 17/Mar/23  Updated: 27/Nov/23  Resolved: 27/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: Ann-Marie Breaux (Inactive) Assignee: Ann-Marie Breaux (Inactive)
Resolution: Done Votes: 0
Labels: LC1, at-risk, consortia, ecs, epam-folijet, inventory, metadatamanagement
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File UIIN-2460 After share.png     PNG File UIIN-2460 Before share.png    
Issue links:
Blocks
blocks UIIN-2504 Testing of UXPROD-4212, UXPROD-4265, ... Closed
blocks UIIN-2507 Testing of UXPROD-4138 - "Search and ... Closed
Defines
defines UXPROD-785 Inventory In Progress
is defined by KAFKAWRAP-38 Add Tenant Id To Every Produced Message Closed
is defined by MODDICONV-348 Create default hidden job profile to ... Closed
is defined by MODINV-817 Shadow Instances - add support for Co... Closed
is defined by MODINV-818 Add contributingTenantId to Instance ... Closed
is defined by MODINV-819 Handle Instance Sharing For Consortium Closed
is defined by MODINV-820 Implement sharing of Instance with so... Closed
is defined by MODINV-821 Implement sharing of Instance with so... Closed
is defined by MODINV-840 Adjust Create Instance handler to use... Closed
is defined by MODINV-866 Add deduplication mechanism for shari... Closed
is defined by MODINV-870 Refactor and add tests for Instance s... Closed
is defined by MODINV-874 Create shadow instance in member tena... Closed
is defined by MODINV-875 Create shadow instance in member tena... Closed
is defined by MODINV-877 Adjust assignment of Instance HRID Closed
is defined by MODINV-879 Unlink local MARC authorities from sh... Closed
is defined by MODINV-890 Unlink local MARC authorities from sh... Closed
is defined by MODINVSTOR-1073 Convert Local Instance to Shared Inst... Closed
is defined by MODINVSTOR-1076 Shadow Instance Synchronization Closed
is defined by MODINVSTOR-1103 Ad hoc Shadow Instance creation when ... Closed
is defined by MODSOURMAN-1011 Import An Instance With A Known Ident... Closed
is defined by UIIN-2682 Handle errors when sharing local inst... Closed
is defined by MODSOURCE-645 Delete Source Records from Member Tenant Closed
Relates
relates to UIIN-2460 Promote a local instance to become a ... Closed
relates to UIIN-2498 Consortial Central Tenant: Handling o... Closed
relates to UIIN-2571 Add permission to promote a local ins... Closed
relates to UXPROD-4331 Support work for sharing instances wi... Closed
relates to MODCON-59 Implement POST endpoint to initiate i... Closed
relates to MODCON-60 Implement GET endpoint to retrieve sh... Closed
relates to MODCON-61 Implement logic to pulling down a sha... Closed
relates to MODCON-62 Implement kafka producers and listene... Closed
relates to UXPROD-4209 Inventory UI changes needed for ECS Closed
relates to UXPROD-4258 When a shared consortial instance is ... Closed
relates to UIIN-2575 Confirmation modal: Unlink local MARC... Closed
Requires
is required by UIIN-2496 Derive new Shared MARC bib record fro... 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: Small < 3 days
Front End Estimator: Mariia Aloshyna
Front-End Confidence factor: 80%
Back End Estimate: XXL < 30 days
Back End Estimator: Kateryna Senchenko
Back-End Confidence factor: 90%
Development Team: Folijet
PO Rank: 109
Rank: Cornell (Full Sum 2021): R5

 Description   

Current situation or problem: Consortia members must have the ability to collaborate in contributing and managing cataloging records. 

In scope

  • User has the ability to "share" an instance record up to the consortia when creating the record
  • User has the ability to "share" an instance record up to the consortia when editing the record
  • User has the ability to "share" an instance with source FOLIO OR MARC
  • Once shared, user must have permission to edit shared instances to be able to edit the instance record further. Otherwise they can no longer edit the instance once shared

Out of scope

  • Ability to "Unshare" a record
  • UI changes: See UIIN-2460 Closed and UIIN-2571 Closed for those details, plus the BE behavior that is triggered by the "Share local instance" action

Proposed stories:

  • Create new options in the "Instance view" Actions menu
    • Share local instance
  • Create new options in the "Instance result list" Actions menu
    • Share selected local instances
      • NOTE: This is not currently accounted for in the UI stories. Mariia Aloshyna and Kateryna Senchenko how much extra work would it be if we allow a user to select several local instances in the instance result list and then Share them all via a batch action, instead of having to share each instance, one at a time, from the Instance detail action menu?
  • Create shared record in central tenant
    • Share local Instances with source = MARC 
      • promote Instance to consortial tenant with source = FOLIO
      • Overlay Duplicate of MARC record from local tenant
      • Update HRID of local instance
      • Deprecate local MARC record
    • Share local instances with source = FOLIO
      • promote Instance to consortial tenant with source = FOLIO
      • Update HRID of local instance

Links to additional info

Questions

  • What happens to any attached holdings/items from other libraries when the record is "unshared"? This will not be in scope of this feature. Ultimately it is not clear what use case would support allowing users to unsure a record that is being used by other libraries. Potentially a library deciding to "Unshare" a record would simply create a local duplicate of the record (And underlying source) and move the libraries holdings and items to that local copy. Other libraries using that record would still have a shared record. 
  • When shared, does every library have the ability to view all holdings/items attached to that shared record? Yes, all member libraries will see the shadow view of the shared instance and any holdings and item data that appears in the Consortium accordion
  • Do we only need the ability to share individual instances, or do we also need the ability to select multiple Instances from the results pane to share?  Yes, it would be helpful to have a bulk share action that would share all of the local instances selected in the result pane.


 Comments   
Comment by Khalilah Gambrell [ 14/Apr/23 ]

Hey Dennis Bridges and Ann-Marie Breaux, this work would be done by Folijet. Spitfire is responsible for quickMARC which is just the UI for creating/editing a MARC record. 

There may need to be a feature for quickMARC to display functionality that supports sharing record AND/or displaying member who owns record. 

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