As already explained in a separate thread, I’m currently working on implementing a CSV export for Live Data (see there for technical details). At least the first version will be quite basic and most likely not include custom handling for fields of different types, in particular fields where the displayed data is HTML. Future versions might improve this and also introduce different export file formats.
What I’m asking here is: do we want this export to be in XWiki Standard as a feature that is always present and enabled in Live Data?
Having the export in XWiki Standard would mean that I could write a nice integration in the menu of Live Data and add an export panel similar to the advanced filters where the progress is displayed and the download link is available. Further, the feature would always be available and thus easily discoverable.
If the export feature should (at least initially) not be in XWiki-Platform, I would create a contrib extension. Unfortunately, we have currently no concept how Vue.js components can be extended in extensions and therefore, at least in a first version, there will be no integration in the Live Data UI. As I’m not familiar with Vue.js, I unfortunately also don’t see how I can create such an integration possibility for now. Providing such an extension possibility would also mean that the current Vue.js components become an API and an upgrade to Vue.js 3 will be more difficult if at all possible. Instead, the exporter I would develop would provide a separate macro that produces a button that triggers the export. From a short investigation, it seems possible to get the currently configured filters from LiveData by directly accessing the Vue.js component, so this won’t require any changes but will depend on APIs that should probably be considered internal.