-
-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
csv exporter #14
Comments
I do remember that Jackson, we already use with EMFJson also supports csv and may be worth looking into that first. I do remember that it needed an individually configured Thus I believe it would make sense to look at this first and see how this can be utilized. |
For now, two questions:
|
correct
Export only for now, as a csv is usually a result of an Excel export and I can hardly imagine that they will conform to our models. |
Both ZIP mode and flat mode exporters delivered in #23 |
Similar to the ODT Exporter, we need a csv Exporter registered with the content type "application/csv" (an others if more mimetypes for csv exist).
It should support 2 Modes (similar to ODT):
Flat Mode
All Contained Objects land in one flat csv file. An exported person could e.g. look as follows:
Zip Mode
The result will be a zip, containing a csv for each exported EClass, similar to the different Sheets in the ODT Export, plus a csv file with the metadata of the EClass.
We could use the URI to determine the mode (e.g if the URI ends in .zip) or an Option. I'm open for suggestions.
The delimiter should be
,
by default and should be additionally configurable via an Option.The text was updated successfully, but these errors were encountered: