Committee csv file - add new separation for 'forward_to_committees' column / add a new column

[MSoeb]

Current behavior
The forward_to_committees column is currently not usable, if committee name contains commas. The separator between the committee names is per default (and export) a comma. If a committee name now contains one or more commas, the column cant' handle this correctly and the exported csv file isn't usable on-the-fly.

Example of committee names:
A) Fachbereich Bildung, Pädagogik, Hochschulpolitik
B) Bezirk Erfurt, Fachbereich Bildung
C) Bezirk Thüringen

Output in csv file: Fachbereich Bildung, Pädagogik, Hochschulpolitik, Bezirk Erfurt, Fachbereich Bildung, Bezirk Thüringen

If this is used again for import and reference, the import would recognize a new committee after each comma. This is not correct. To make the exported csv file usable an additional and not intentional step is needed. The user needs to add single and double quotes via a text editor so the import will recognize the correct committee names.

Wanted behavior
The aim is to make the csv file output on-the-fly useable. The csv file should have a structure, that correctly separate committee names with commas and the user doesn't need to edit the csv file to make it usable.

• We've talked about this topic in ABS team and we think, that a Semicolon for separation should work.

Example with names from above: Fachbereich Bildung, Pädagogik, Hochschulpolitik; Bezirk Erfurt, Fachbereich Bildung; Bezirk Thüringen

• Additionally the csv should be able to handle meeting IDs for reference. Therefor a new column forward_to_committees_ids should be integrated in the csv file behind foward_to_committees. (This part needs to be reevaluated. Unclear if import and export relevant.)

[luisa-beerboom]

• We've talked about this topic in ABS team and we think, that a Semicolon for separation should work.

Why? All that would need to be done to fix this part of the issue, is to ensure the client puts titles containing commas into double quotes and everything would work again. If you just supplement commas with semicolons, you're just going to get the same issue again, just for a different set of committee titles.

We can discuss the option of making the CSV settings for the internal list interpretation selectable, sure, but I don't really see a need.

[luisa-beerboom]

• Additionally the csv should be able to handle meeting IDs for reference. Therefore a new column forward_to_committees_ids should be integrated in the csv file behind foward_to_committees.

I don't know what a column with a name forward_to_committees_ids would have to do with meeting ids, I have no idea what the field is even supposed to do, and I don't understand what "for reference" is even supposed to mean.

It sounds like you want to change something about how the meeting creation functionality works, or add some kind of meeting update functionality.
If that is the case, first of all, please add a feature label, because that is a feature.

I still can't even begin to fathom what the forwarding committees would have to do with that.

More importantly:
Please explain what you want. In detail.

[MSoeb]

For case 1 it's unclear, if we use always double quotes or semicolon for import. Further clearification is needed.

As first step, the export data can be exported with double quotes, so it can be reimported.

[luisa-beerboom]

I don't know what a column with a name forward_to_committees_ids would have to do with meeting ids, I have no idea what the field is even supposed to do, and I don't understand what "for reference" is even supposed to mean.

After discussing with @MSoeb
The original text was mistakenly using meeting ids when it should've said committee ids, which created the confusion.
This part of the issue was actually about having a second forwarding column that contains committee ids instead of committee titles.
Whether that column is necessary at all, whether or how it should be used or ignored by the import or whether it should just be permitted to use ids instead of titles in the regular committee fields will need to be discussed by ABS.

Anyway, the export part of all of this is definitely a client issue.

The part where the exported CSVs don't work with commas in titles can be fixed simply by ensuring the client puts any list element containing commas (and maybe double quotes) in double quotes during import.
Which is also a client issue.

Since all this ought to suffice to fix the initial problems, I'm moving this to the client.
@MSoeb if you decide you actually need configurable internal list interpretation delimiters or that the committee ids ought to be interpreted by the backend, please create a backend issue again

PS: There is the option of having a separate export button where the client simply uses ids instead of committee titles, allowing for the backend to just simply see if the thing, it is trying to interpret, is a number, interpreting all numbers as ids and throwing if said ids aren't found.