EPIC: reports and dashboards for BIBFRAME (UXPROD-4218)

[UXPROD-4577] User Account & Permissions Created: 24/Nov/23  Updated: 04/Feb/24

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

  • Follow / inherit how user permissions are created and supported in FOLIO
  • Marva-specific settings at the user level
    • e.g. Permissions around editing and governance of resource descriptions

Out of scope

Use case(s)

  1. Cataloger
    • Ability to access the Marva editor application through FOLIO
    • Ability to create new resource descriptions in Marva 
    • Ability to update Instance entity
    • Ability to update Work entity
    • Ability to view / update / delete at resource level
    • Ability to view / update / delete at component level
    • Ability to view / update / delete based on source (e.g. CONSER)
    • Ability to access cataloger's own dashboard
    • Q: do catalogers authorized to catalog in Marva retain authority to edit in quickMARC
  2. Manager  
    1. Ability to run reports
    2. Ability to see output of cataloging for team
    3. Rules related to delete / staff suppress
    4. Ability to override changes made by a cataloger, including ability to change source type back to MARC (will likely be a new category)
  3. System administrator
    • Ability to define a set of resource descriptions for export via the data export module in FOLIO
      • Temporal (day, week, month, custom)
      • Bibliographic parameter
      • Status (e.g. exclude resource descriptions that are suppressed from patron view)
    • Ability to save export queries
    • Ability to create, modify, delete validation rules that apply to resource descriptions
    • Ability to create, modify, delete import and export profiles
    • Ability to conduct bulk edit jobs

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


Generated at Fri Feb 09 00:40:58 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.