Details
-
New Feature
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
None
-
-
Medium < 5 days
-
High
-
XXL < 30 days
-
Concorde
-
-
105
-
It would greatly expand functionality of data-export
-
R4
-
R1
-
R1
-
R1
-
R1
-
R1
-
R1
-
R1
-
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.
TestRail: Results
Attachments
Issue Links
- has to be done before
-
UXPROD-2330 Scheduling export of inventory records through an API
-
- Open
-
- is defined by
-
MDEXP-281 POC: Export records using CQL
-
- Closed
-
-
MDEXP-294 Export records using CQL
-
- Closed
-
-
UIDEXP-2 Save the CQL query for instances search
-
- Closed
-
-
UIDEXP-10 Data Export App - landing page - selecting file with Instances CQL query
-
- Closed
-
-
UIDEXP-11 Data Export App - landing page - file selection area
-
- Closed
-
-
UIDEXP-155 Save CQL query for instances search in cql file
-
- Closed
-
-
UIDEXP-156 Data Export App - triggering the export by Instances CQL query
-
- Closed
-
- relates to
-
UXPROD-2065 Export Manager - data export landing page
-
- Closed
-