Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Export Manager - triggering export of Inventory instances by providing file with CQL query

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.

Priority

Labels

Fix versions

Development Team

Concorde

Assignee

Solution Architect

Parent

Parent Field Value

None

Parent Status

None

Checklist

hide

TestRail: Results

Activity

Show:

Magda Zacharska June 16, 2020 at 8:02 PM
Edited

- 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.

Kruthi Vuppala June 16, 2020 at 6:10 PM

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?

Cate Boerema March 24, 2020 at 11:02 AM

Hi we need estimates for this for the cap plan.

Done

Details

Reporter

PO Rank

105

PO Ranking Note

It would greatly expand functionality of data-export

Front End Estimate

Medium < 5 days

Front End Estimator

Front-End Confidence factor

High

Back End Estimate

XXL < 30 days

Back End Estimator

Rank: 5Colleges (Full Jul 2021)

R1

Rank: Cornell (Full Sum 2021)

R1

Rank: GBV (MVP Sum 2020)

R1

Rank: hbz (TBD)

R1

Rank: TAMU (MVP Jan 2021)

R1

Rank: Chicago (MVP Sum 2020)

R4

Rank: MO State (MVP June 2020)

R1

Rank: Lehigh (MVP Summer 2020)

R1

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created March 18, 2020 at 4:31 AM
Updated September 16, 2021 at 5:16 PM
Resolved October 19, 2020 at 6:50 PM
TestRail: Cases
TestRail: Runs