EPIC: reports and dashboards for BIBFRAME
(UXPROD-4218)
|
|
| Status: | Open |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | EPIC: reports and dashboards for BIBFRAME |
| Type: | New Feature | Priority: | TBD |
| Reporter: | Doug Loynes | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | bf-alpha, loc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Release: | Ramsons (R2 2024) |
| Epic Link: | EPIC: reports and dashboards for BIBFRAME |
| Front End Estimate: | XL < 15 days |
| Front End Estimator: | Siarhei Karol |
| Front-End Confidence factor: | 100% |
| Back End Estimate: | Large < 10 days |
| Back End Estimator: | Punnoose Kutty Jacob Pullolickal |
| Back-End Confidence factor: | 100% |
| Development Team: | Citation |
| Report Functional Area(s): |
User Management
|
| PO Rank: | 0 |
| Description |
|
Current situation or problem: For the Thin Thread release, anyone can access and use the module. In production, FOLIO will need to support user accounts and permissions for a number of purposes, including for the individual cataloger to keep track of work completed and to set preferences in the UI. In scope
Out of scope Use case(s)
Proposed solution/stories Links to additional info Questions Since the application will be available as a stand-alone module (interoperable with the FOLIO platform), what architecture decisions should be made to support user account for an institution without FOLIO? Q: Is there information included in the bib record that shouldn't be displayed publicly? Could point to a requirement that prevents a user from unsuppressing the status Q. Suppress - any cataloger can set suppress |