Metadata Record Export (UXPROD-652)

[UXPROD-2326] Export Manager - logs details Created: 17/Mar/20  Updated: 16/Sep/21  Resolved: 19/Oct/20

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q3 2020
Parent: Metadata Record Export

Type: New Feature Priority: P3
Reporter: Magda Zacharska Assignee: Magda Zacharska
Resolution: Done Votes: 0
Labels: data-export-q3-2020, export, inventory, metadatamanagement, po-mvp, q2-2020-spillover, round_iv
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File 1-data-export-landing-page(2).png     PNG File 2-data-export-view-all(3).png     PNG File Execution detailed log..png    
Issue links:
Defines
defines UXPROD-652 Metadata Record Export In Progress
is defined by MDEXP-259 Log errors for Holdings records export Closed
is defined by MDEXP-261 Create API GET/data-export/logs/{jobE... Closed
is defined by MDEXP-262 Create a link to the inventory record... Closed
is defined by STDTC-6 Spike: Explore view all logs page fro... Closed
is defined by UIDEXP-18 Data Export App - landing page - view... Closed
is defined by UIDEXP-62 Data Export App - landing page - add ... Closed
is defined by UIDEXP-63 Data Export App - landing page - ope... Closed
is defined by UIDEXP-97 Add Error column to the list of compl... Closed
is defined by UIDEXP-142 View logs - main pane Closed
is defined by UIDEXP-144 Render error log details Closed
is defined by UIDEXP-145 Change query for rendering jobExecutions Closed
is defined by MDEXP-107 Query completed export jobs by job's ... Closed
is defined by MDEXP-108 Query completed export jobs by file n... Closed
is defined by MDEXP-111 Query completed export jobs by job pr... Closed
is defined by MDEXP-112 Query completed export jobs by user w... Closed
is defined by MDEXP-113 Query completed export jobs date range Closed
Relates
relates to MDEXP-256 Modify status of the completed export... Closed
relates to MDEXP-257 Log errors for inventory Instance rec... Closed
relates to MDEXP-258 Introduce error codes for errors dur... Closed
relates to MDEXP-260 Log errors for Inventory Item records... Closed
Epic Link: Metadata Record Export
Front End Estimate: XL < 15 days
Front End Estimator: Viktor Soroka
Front-End Confidence factor: Medium
Back End Estimate: Large < 10 days
Back End Estimator: Kruthi Vuppala
Development Team: Concorde
PO Rank: 115
PO Ranking Note: This feature will allow user to see the details of the data export job and is crucial for troubleshooting
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R1
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R1
Rank: FLO (MVP Sum 2020): R1
Rank: GBV (MVP Sum 2020): R1
Rank: hbz (TBD): R1
Rank: Lehigh (MVP Summer 2020): R1
Rank: MO State (MVP June 2020): R1
Rank: TAMU (MVP Jan 2021): R1

 Description   

There are three elements of this functionality:

1. Landing page - Logs container
This functionality has been mostly implemented but will need to support a scenario when the export generates multiple files, with each file name being a link to the generated file. When user clicks each file name the files are downloaded.

2. View All option
This will display a new form that will contain list of all jobs. How long the logs are being preserved will be determined by tenant level settings. The jobs will be searchable by ID, generated file name, date of execution, job profile and name of the user who triggered the job.

3. Detailed log
This will be accessible by clicking the whole row of listed jobs on the landing page (for recently completed jobs) and View All form. The log will contain a list of all records that were exported (successful and failed) in their designated format. User should be able to filter by successful/failed records. Failure should be displayed in with details (missing or invalid data, for example). The initial implementation could be similar (if not identical) with data import detail log (see attached screenshot)



 Comments   
Comment by Magda Zacharska [ 20/Mar/20 ]

only error in detailed log

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