The aim of the study is to define the major implementation step by step that shall be done so that we can identify it doability and estimation.
This study will involve the WebUI team and the UX designer so that we can be coherent with the solution to implement and the actual relevance of the feature for end users.
Definition of Done:
1- Look at what is in JSF
2- Discussion between core team and WebUI team + UI/UX Designer to define good practice for CSV export feature
3- Have major implementation steps clearly defined
Meet on the 27th of march
On a Bulk operation to generate the cvs export:
- Could introduce status endpoint in order to retrieve the results
- We want to go through a stream processing way first, as an operation. So chaining can be done afterwards.
- Could read it using a batch of document or document by document. We want to use temporary storage to create the file we want to build. Ones done, we can have another computation to create the zip, and once we know that the job is done (by asking to the processor the key ID) we can provide the output to the user by pulling thanks to the token he has received. It would be completely async. We could then use the GUID in a such way that it could be possible to : inform the user to pull the file, or send a mail with the export attached (automation chain can be considered).
- The case where the file is stored somewhere, it could be seen as a chain where the output can be placed in a configured location that the user know he can find it there.
We could define the stream processing.
Important: design with the ability to run computation base operations.
Need to provide Helpers so it is easy to process documents