Export - Formatter .CSV - features

yes. I agree. We will add it.

Кнопки нет. Это форматтеры. Что бы сделать экспорт надо просто активировать плагин форматера и добавить к урл

&formatter=json

или любой другой который есть.

yes. I agree. We will add it.

Any news about CSV formatter and security/restriction question that has been raised by "Sackgesicht"?

Bumping my own topic for notification. Any news?

pepperstreet Any news about CSV formatter and security/restriction question that has been raised by "Sackgesicht"?

Plugin parameter "Access" restricts execution of formatter/URL. :)

pepperstreet - Do not open in browser window - Limit field output

Added ideas to initial post.

pepperstreet Further ideas and feature requests

Topic status was changed to "solved"?

Actually a CSV exporter should be part of every list template. An optional button to export all the list result records with the respective displayed fields

pepperstreet Topic status was changed to "solved"?

Yes, because in generald CSV exporter is implemented.

Sackgesicht Actually a CSV exporter should be part of every list template. An optional button to export all the list result records with the respective displayed fields

You can apply CSV to any template already. What do you mean?

Sergey What do you mean?

If i apply a filter/search to a list, i would like to export only the result (listed articles) with only the fields of this list. Therefore an optional button, exporting only the article list would be a good addition to every list template.

Example: A list of cars, but i only want to export Volvo.

I think formatter=csv parameter is only view change. It means that it list the same article that would be returned in normal view. I mean if you apply filter and then add formatter=csv you will get filtered list there. Of course in custom template you can create a special button for that.

Sergey

pepperstreet Topic status was changed to "solved"?

Yes, because in generald CSV exporter is implemented.

;-) yes, i know. But i did't want to add a topic for the other (possible) features. Should I change the topic title then? And re-open it?

Sergey I think formatter=csv parameter is only view change. It means that it list the same article that would be returned in normal view.

One issue here is the pagination. It will only return the number of articles on the screen. Pagination allows only up to 100 records. Another issue is security. Anyone can export all intro fields (plus additional info like hits, rating etc) of ALL sections by just adding "&formatter=csv" to the URL (provided the plugin is activated).
A list of fields should be considered per exportable section to allow the inclusion of full view fields as well. I would suggest to add a parameter "Allow Export" under "General properties" of field parameters.

Beside this, the export is not working properly for some field types. Most target systems for import (like Excel) can not recognize the cobalt csv output. Output should be generated based on CSV specifications. I would recommend to follow the very simple rules of RFC 4180 for highest level of compatibility.

Sackgesicht A list of fields should be considered per exportable section to allow the inclusion of full view fields as well. I would suggest to add a parameter "Allow Export" under "General properties" of field parameters.

Or sections list parameter in plugin.

Sackgesicht Beside this, the export is not working properly for some field types

Thank you for RFC link. I have added changes and tested. It opens well in MAC version of Excel. And i update plugin.

Sergey It opens well in MAC version of Excel

I had problems with the old CSV plugin version ... Especially the gallery field (several pictures), upload field with several files ..

I would suggest to export the multi-level-field optional as only the field value, not the additional ids.

Example : HUGHES 369 HS -- not [{"427":"HUGHES","428":"369","429":"HS"}]"

A Radio button field should just contain the value (or escaped with ") not like "["F79GA"]"

Sergey Or sections list parameter in plugin.

With a section parameter in plugin it will still be the same regarding the fields (as of now it exports the intro fields plus additional core fields)., but with a field parameter we can easily define it when we add fields , or even just mark them in the field overview with all the checkboxes (intro, full view, searchable in compare view, etc) and it can also apply to all formatter plugins ...

I use JSON syntax for easie to use. When you create import script you can json_decode it.

I have added another parameter to insert fields values as string or JSON. And also string glue parameter for stringified values. And updated plugin.

Getting better ... ;-)

With a multilevel field, we would need control over the separator. Now it is the ",", but there are cases where we dont want it.

Example: Car --> Porsche 944 S2 -- and not Porsche, 944, S2

Another field to consider a different (optional) content, is the child field. Instead of the record ID, the title would be helpful here. I believe that most of the time, the exported data will be used in another application like Excel to better organize and present the data.

Field relations would not be helpful in this case.

Sergey When you create import script you can json_decode it.

the export should be as "flat" as possible .. no need to consider json_decode on it. In your import, you also dont expect json_decoded csv files, right?

Anyway, there is a JSON formatter as well... ,-)

Sackgesicht With a multilevel field, we would need control over the separator. Now it is the ",", but there are cases where we dont want it.

You mean difefrent glue for just this field?

MultiLevel Field I believe it should be exported the same way as it is displayed. The most logical approach would be to follow the field settings under "General Parameters"-> "Level Separator"