Details
Reporter
Dennis BridgesDennis BridgesFront End Estimate
XL < 15 daysFront End Estimator
Mariia AloshynaMariia AloshynaFront-End Confidence factor
80%Back End Estimate
Out of scopeBack End Estimator
Kateryna SenchenkoKateryna SenchenkoBack-End Confidence factor
90%Release
Umbrellaleaf (R3 2025)Rank: Cornell (Full Sum 2021)
R5TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Reporter
Dennis Bridges
Dennis BridgesFront End Estimate
XL < 15 days
Front End Estimator
Mariia Aloshyna
Mariia AloshynaFront-End Confidence factor
80%
Back End Estimate
Out of scope
Back End Estimator
Kateryna Senchenko
Kateryna SenchenkoBack-End Confidence factor
90%
Release
Umbrellaleaf (R3 2025)
Rank: Cornell (Full Sum 2021)
R5
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created February 27, 2024 at 5:58 PM
Updated March 5, 2025 at 5:48 PM
Current situation or problem: Consortia members must have the ability to collaborate in contributing and managing cataloging records. It must be possible to edit local holdings and items of different affiliations without constantly switching affiliation.
In scope
User can edit shared or local instances in a member library tenant, without changing affiliation to the shared tenant
User can edit Holdings or Items from shared instances, without changing affiliation to the “Owning tenant”
User can view/create/edit the holdings and items for a member library tenant
User can view summary or detailed holdings and items for other member libraries, depending on user permissions
Out of scope
Changes for search, filter, and results display are being handled by Spitfire in a separate Jira
Creating/editing local instances for one library tenant in another library tenant (user has to change affiliations to do that)
Moving holdings/items for one library tenant in another library tenant (user has to change affiliations to do that) ***Review against Update Ownership***
Use case(s){*}
*
Proposed solution/stories
Links to additional info