Won't Do
Details
Assignee
Aliaksandr FedasiukAliaksandr FedasiukReporter
Olamide KolawoleOlamide KolawoleLabels
Priority
P2Story Points
3Development Team
FolijetRelease
Poppy (R2 2023)TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Aliaksandr Fedasiuk
Aliaksandr FedasiukReporter
Olamide Kolawole
Olamide KolawoleLabels
Priority
Story Points
3
Development Team
Folijet
Release
Poppy (R2 2023)
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created June 6, 2023 at 12:24 AM
Updated October 12, 2023 at 1:19 PM
Resolved July 27, 2023 at 9:40 AM
Purpose/Overview:
Shadow Instances are instances that live in a local tenant and share corresponding identifier with another instance in the central tenant of a consortium. Library staff will be able to creating holdings and items under a Shadow Instance but are not able to modify the Shadow Instance.
Requirements/Scope:
Shadow Instances have their source field set to CONSORTIUM-MARC or CONSORTIUM-FOLIO. This is dependent on the source field of the Shared Instance
Acceptance criteria:
When Shadow Instances are created, the Shared Instance's presence in the central tenant should be verified.