search

collective / collective.excelexport

Export dexterity contents in an excel file, one column by field
3 stars 9 forks source link

Question: explain differences to plone.importexport? #12

Open djay opened 6 years ago

djay commented 6 years ago

Not sure if this is the right place but it would be helpful to explain in your readme why to use this vs the soon to be included in core plone plone.importexport?

https://github.com/collective/plone.importexport

Perhaps also there are missing features of plone.importexport you can suggest as being needed in core plone?

tdesvenain commented 5 years ago

Hi @djay , this is not a product dedicated to export content in a format that will be imported, but a product to generate excel exports for end users.

btw the goal of the product is not to export "all" content but content from sources which can be a query catalog, a folder, a collection or an eea.facetednavigation query.

afaic i use 'excel' export more often than 'csv' export

djay commented 3 years ago

@tdesvenain Both usecases are indeed supersets of the functionality of plone.importexport. That product is NOT designed to export only in a format used for import. It is designed as an tool to get reports out in a common format that is easily read by excel or other tools. These can be for part of the site or even arbitrary queries of content (currently just types but will be based on query widget later). Adding excel instead of just CSV is certainly possible but I'm not sure the advantage given CSV is basically the same?

p.importexport also has the feature so you take any CSV you have and import that as new content or update existing content. And also include a zip of files too.