Features that will be implemented to enhance FOLIO's ability to support consortia (Phase 1)
(UXPROD-4049)
|
|
| 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: | Duplicate | Votes: | 0 |
| Labels: | LC1, consortia, data-import, ecs, epam-folijet, metadatamanagement, needs-be-estimate, needs-ui-estimate | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||||||||||||||||||
| 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: | 70% | ||||||||||||||||||||||||||||||||||||||||
| Back End Estimate: | Large < 10 days | ||||||||||||||||||||||||||||||||||||||||
| Back End Estimator: | Kateryna Senchenko | ||||||||||||||||||||||||||||||||||||||||
| Back-End Confidence factor: | 80% | ||||||||||||||||||||||||||||||||||||||||
| Development Team: | Folijet | ||||||||||||||||||||||||||||||||||||||||
| PO Rank: | 105 | ||||||||||||||||||||||||||||||||||||||||
| 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. It must be possible to manage the importing and sharing of bibliographic records at the consortia level Updates
Creates
Think through from the context of the consortia tenant vs from the context of the shared tenant In scope
What else to consider
Testing Non-consortial tenant (standard - Do not have consortium app enabled) - > No impact. Performance should not be impacted. Member library tenant (local) - Test based on scenarios/user stories documented. Need to measure performance and meets benchmarks. Central tenant (consortium app active in UI) - Test based on scenarios/user stories documented. Need to measure performance and meets benchmarks. Out of scope
Use case(s){} Proposed solution/stories Links to additional info Questions |
| Comments |
| Comment by Olamide Kolawole [ 06/Jun/23 ] |
|
Full design is located here https://folio-org.atlassian.net/wiki/x/PS8b |
| Comment by Christine Schultz-Richert [ 26/Jun/23 ] |
|
Hey Ann-Marie Breaux , my understanding was that if a record was imported into an individual member tenant that it would be local and if a record was imported into the central tenant it would be shared (this way there would need to be no additional option to indicate whether imported records were to be considered shared or local). Is that incorrect? |
| Comment by Ann-Marie Breaux (Inactive) [ 21/Aug/23 ] |
|
Hi Christine Schultz-Richert Yes, that is correct. However a user in a member library may be updating a mix of shared and local instances. As long as they have permission to import to central tenant and member tenant, they can trigger the import from the member library, but it will also update the shared SRS MARCs and Instances |
| Comment by Ann-Marie Breaux (Inactive) [ 21/Aug/23 ] |
|
Covered by
|