Data export functionality mock-ups
| Dennis Bridges | - export functionality that would work across folio
- exporting objects from inventory
- A set of APIs within the export module that would be called from other apps
- if you started an export from somewhere, there would be a log
- Proposing to add another tab for other jobs
- Question from chat (I'm wondering if it might help to add a column containing a link to any associated error logs that are generated during the export?)
- Viewing errors, etc?
- The view of each log item would give some kind of details
- Q: What about showing in a quicker view if there were errors, or if they could be highlighted for quicker recognition of those errors ?
- An error file, perhaps?
- from chat (In the KB Local Admin we have job results “Success”, “Partial success”, “Failure”, “Interrupted” )
- from chat (“Success” means that it completed without any errors, “Partial success” completed with some errors, “Failure” means the job failed somehow, and “Interrupted” means that the job was prevented from finishing)
- Any module that uses export functionality, this tab would track that activity
- it could be searched and filtered
- More efficient way to export things (from a technical perspective)
- Mod audit, Mod finance, mod finance, etc, places to get information
- from wherever one use in the UI, a request would be made to use this application
- this app would need to be able to work with the other apps
- this would be thus less impact on the other apps since the activity is happening separately in its own app
- Springbatch tech for export
- what is the export file going to be?
- can the export be reduced to what is needed or will it pull everything that is preset in that export?
- Might the type of data need some kind of profile (blueprint for the export itself)
- How do we set up what to expect from the export, to better understand what is actually exported, or what was actually requested
- This interface is for showing the exports that happened
- the list would show those jobs that are done
- the export file would be sent to whomever is to receive it
- The file could also be downloaded, later, in the future, at the user's convenience
- Might an e-mail be sent that notifies a user that a job has run
- the data-export app is not where the export is being requested, but to log the activity (questioning the naming of the app, since no actual export is being requested in it)
- Is there an export queue?
- IN inventory, the CQL or the IDs have to be downloaded in one app and uploaded in another (the suggestion here seems to suggest that activity should be avoided)
- But this app is really a log
- from chat (having "set" functionality , which I have heard mentioned, would be a way to perform exports on a saved set of record created by a query or selection )
- from chat (I’m really aware that in Agreements we have both data import and export that doesn’t go via either of the “Data import” or “Data export” apps )
- want to be able to export orders based on a search that was done
- If an export request is made, the designers are asking that the page not be reloaded - if the tab is closed, the export will be stopped (current functionality)
- every row on the exported spreadsheet represents a POL level rowsPOL level rows
- There is a way to configure what is actually being tested (supplier, material, etc)
- it takes 30-40 seconds for around 1000 POLs in an export
- average volume of data being exported is in the 1000s (this takes quite a bit of time)
- If the data can't be used to search for orders, another way would be needed
- planned for inclusion in Iris
- Notes can be exported in this ?(one to many)
- still working on this export
- some concern about requesting notes about performance because it would take longer, but the goal would be to export notes with them
- all other notes in the POL are included
- each query would need to be chosen each time, as opposed to a specific export being set up in advance if it is a regular thing, but some set export jobs could be convenient
|