[UXPROD-4162] Export User records to Single Page or CSV Created: 02/Apr/23 Updated: 30/Nov/23 |
|
| Status: | Draft |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | New Feature | Priority: | P3 |
| Reporter: | patty.wanninger | Assignee: | Tim Auger |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | stretch_goal_poppy, usermanagement | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
| Development Team: | Volaris |
| PO Rank: | 0 |
| Rank: Cornell (Full Sum 2021): | R4 |
| Description |
|
A library administrator would like to be able to select fields for an export of users and send the results of a User search through that job to create a report. Would like to be able to combine information from different accordions, such as fines/fees, loans, and proxy/sponsor. According to GDPR, patrons have the right to a information about their complete record - everything that is stored in the library system. This report needs to be executed from the action menu by somebody at the circulation desk, and printable in a way that a patron could parse. |
| Comments |
| Comment by patty.wanninger [ 02/Apr/23 ] |
|
Tim Auger This is the other new feature. Magda Zacharska and Dennis Bridges - this seems like it might be similar to https://folio-org.atlassian.net/browse/UIOR-632. Can you give me some pointers on who should take a look at this to flesh it out? |
| Comment by Tim Auger [ 03/Apr/23 ] |
|
Excellent, patty.wanninger ! |
| Comment by Dennis Bridges [ 03/Apr/23 ] |
|
patty.wanninger I can say that in acquisitions we took a Frontend approach to satisfy this requirement. The export module was much less developed than it is now. So the order export is actually entirely done by the UI module. The UI requests the data from the backend and displays it in search results. When a user clicks export result the UI packages all of that data, according to the users specification, as a csv file for the browser to download. Ie. nothing about the export is stored, every time the users wants to down load they must choose the settings again and if the results included a huge number of records it is possible the export would just fail. Also if the user navigates away from the app while it is trying to package the data the whole export just stops.
So definitely a light weight approach but for the amount of effort it provides a lot of value for certain apps. If users app is not exporting over 30,000 records at a time it may be a good solution. If the use cases demand more than that you could probably use the design pattern but consider using data-export-spring on the backend to actually run the export. |
| Comment by Magda Zacharska [ 04/Apr/23 ] |
|
Hi patty.wanninger this functionality is partially implemented in scope of bulk edit. When user starts bulk edit of user records based on the list of user records identifiers, the matching records can be saved in csv format. The file contains entire user record. |
| Comment by Tim Auger [ 23/Apr/23 ] |
|
patty.wanninger I'd love to talk this one through. Do you have time later in the week to talk? |
| Comment by Tim Auger [ 11/May/23 ] |
|
Still need stories to move forward. |