Metadata Record Export (UXPROD-652)

[UXPROD-2707] Data export permissions Created: 01/Oct/20  Updated: 07/Aug/23

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: Sunflower (R3 2024)
Parent: Metadata Record Export

Type: New Feature Priority: P3
Reporter: Magda Zacharska Assignee: Magda Zacharska
Resolution: Unresolved Votes: 0
Labels: LC4, data-export-needs-ranking, firebird-po-share, loc, requires-discussion
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Release: Sunflower (R3 2024)
Epic Link: Metadata Record Export
Front End Estimate: Large < 10 days
Front End Estimator: Magda Zacharska
Front-End Confidence factor: Low
Back End Estimate: Large < 10 days
Back End Estimator: Magda Zacharska
Development Team: Firebird
PO Rank: 85
Rank: Chicago (MVP Sum 2020): R3
Rank: Cornell (Full Sum 2021): R3
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R3
Rank: GBV (MVP Sum 2020): R4
Rank: Grand Valley (Full Sum 2021): R3
Rank: MO State (MVP June 2020): R3
Rank: TAMU (MVP Jan 2021): R4
Rank: U of AL (MVP Oct 2020): R2

 Description   

The existing implementation provides two sets of permissions: access to data export app and access to the setting pages. This feature will allow to make the permissions more granular.

Users having access to the data export app will have separate permission to:

  • access files generated by export
  • start export
  • see error logs
  • view all past exports

Users having access to data export settings pages will have separate permissions to:

  • View mapping and job profiles
  • Create a new mapping or job profile
  • Update an existing mapping and job profile
  • Delete an existing mapping and job profile

Additional information: https://docs.google.com/forms/d/1KCqxeMM6QcAtTim_ZqsxAp1STMRnKRHnex0is3CX1c8/edit#responses

Questions

  • How we can handle permissions to some specific exports?
  • How we can add permissions for exports for larger data than defined threshold?


 Comments   
Comment by Magda Zacharska [ 23/May/23 ]

Adding LC2 label based on prioritization during the LCAP MM meeting on May 17, 2023

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