OpenSlides / OpenSlides/openslides-client

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

Open
#6,465 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement needs discussion Schrödinger
Dominant language
TypeScript
Stars
35
Forks
52
Avg merge
1d 9h
Merged PRs (30d)
52

Description

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.)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file or test is named; start by locating the CSV export and import handling for the forward_to_committees column. Verify that committee names containing commas round-trip without manual editing, and clarify whether the forward_to_committees_ids column is required before considering the work done.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
data
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
54/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.