Metadata Record Export (UXPROD-652)

[UXPROD-2333] Export Manager - triggering export of Inventory instances by providing file with CQL query Created: 18/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, round_iv
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by UIDEXP-11 Data Export App - landing page - file... Closed
is defined by MDEXP-281 POC: Export records using CQL Closed
is defined by MDEXP-294 Export records using CQL Closed
is defined by UIDEXP-2 Save the CQL query for instances search Closed
is defined by UIDEXP-10 Data Export App - landing page - sele... Closed
is defined by UIDEXP-155 Save CQL query for instances search i... Closed
is defined by UIDEXP-156 Data Export App - triggering the expo... Closed
Gantt End to Start
has to be done before UXPROD-2330 Scheduling export of inventory record... Open
Relates
relates to UXPROD-2065 Export Manager - data export landing ... Closed
Epic Link: Metadata Record Export
Front End Estimate: Medium < 5 days
Front End Estimator: Viktor Soroka
Front-End Confidence factor: High
Back End Estimate: XXL < 30 days
Back End Estimator: Kruthi Vuppala
Development Team: Concorde
PO Rank: 105
PO Ranking Note: It would greatly expand functionality of data-export
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R1
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): 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   

Current data export implementation requires user to provide list of the record identifiers in order to trigger the export job. This limits the export to a specific data set. Adding CQL query as an option will allow user to run the export job on different data sets. This functionality is needed for automated jobs that will run the same export jobs for changing data set. For example, if the library needs to do incremental export, the user it will provide the query that will include only newly added records: (metadata.createdDate > last-time-export-run) sortby title

When this feature is completed, the user will upload the file with the query the same way as the file with the unique identifiers. Submitting the file will trigger the export the same way as UUIDs file triggers it right now.



 Comments   
Comment by Cate Boerema (Inactive) [ 24/Mar/20 ]

Hi Magda Zacharska we need estimates for this for the cap plan.

Comment by Kruthi Vuppala [ 16/Jun/20 ]

Magda Zacharska Questions on this:
1) Does this feature also need a requirement to store and be able to retrieve the UUIDs returned by that query at the time of export?
2) Does the list of job Executions need to display that the job was triggered using a CQL query vs list of UUIDs somehow?

Comment by Magda Zacharska [ 16/Jun/20 ]

Kruthi Vuppala - none of those are required for this feature. The saving of cql query is already implemented. The reason for not saving UUIDs is that the user already has a cql statement and the list of the UUIDs will most likely change from one execution to another.

There is no need to know if the export job was a UUIDs or cql query triggered. If the user want to preserve this connection it can be handled by the file name or the name of the job profile used to execute the export.

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