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: | 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: |
|
||||||||||||||||||||||||
| 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
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 In scope:
Out of scope:
Proposed stories:
Questions
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. |