Import Pages - csv example file improvement

[vkrasnovyd]

Resolves #3822

1. Shortened the example csv for importing participants and accounts to 1 line, as was shown in the images.
2. Configured translating values in the selected columns to the current client language:

• in 'gender' column for account-example
• in 'gender' and 'groups' columns for participants-example

Notes in case at some stage example files are updated again:

• If example files are extended with extra lines, the translation will work for all the example lines. No further adjustments will be needed.
• Value in 'groups' column can be translated only if there's only one group name in a cell. Doesn't work for sample values like 'Delegates, Staff'.

[bastianjoel]

With custom translations it is possible to get a non injective set of genders. Therefore it might not be a good idea to allow users to use this. Especially with #4027 this will get much more complicated.

For groups this is a bit different. Those are translated in the backend and therefore guaranteed to be unique. Still the meetings language instead of the users language needs to be used there but I think it might be even better to use an actually existing group name from the groups repo.

@MSoeb please provide feedback on what you want here.

[rrenkert]

With custom translations it is possible to get a non injective set of genders. Therefore it might not be a good idea to allow users to use this. Especially with #4027 this will get much more complicated.

For groups this is a bit different. Those are translated in the backend and therefore guaranteed to be unique. Still the meetings language instead of the users language needs to be used there but I think it might be even better to use an actually existing group name from the groups repo.

@MSoeb please provide feedback on what you want here.

Talked to @MSoeb: We do not want client side translations for genders in the example file. For groups the group name exisiting in the groups repo is the correct value to use.

[vkrasnovyd]

As we discussed with @rrenkert, when the custom gender feature is finalized, I'm going to extend the export files with the gender option from the organization repo. Until then the issue should remain open.

[reiterl]

Ah @vkrasnovyd you need to assign @bastianjoel , if you want his review.

[reiterl]

Small remarks. Please wait for @bastianjoel review.

[vkrasnovyd]

Ah @vkrasnovyd you need to assign @bastianjoel , if you want his review.

Thanks. I may still need to add a couple more changes based on your custom gender implementation. So until it's finalized, I'll keep it assigned to myself.

[MSoeb]

One small adjustment needed:

• Participant csv: The value for the 'new' column 'locked_out' is currently 'false'. This should be changed to value '0' to fit more the other attributes.

[MSoeb]

Looks good.

[bastianjoel]

It would be better to subscribe this on the account/participant list.