Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve organization/genders #2170

Open
jsangmeister opened this issue Feb 1, 2024 · 3 comments · May be fixed by #2485 or OpenSlides/openslides-meta#116
Open

Improve organization/genders #2170

jsangmeister opened this issue Feb 1, 2024 · 3 comments · May be fixed by #2485 or OpenSlides/openslides-meta#116
Assignees
Labels
Milestone

Comments

@jsangmeister
Copy link
Contributor

OpenSlides/openslides-client#3098 was closed as the prerequisites did not suffice. We need the ability to update a gender, e.g. in case of typos. Therefore, the gender should probably become its own model.

Also, we should provide a list of base genders which cannot be deleted (our current standard set of genders).

@jsangmeister jsangmeister added this to the 4.2 milestone Feb 1, 2024
@hjanott hjanott self-assigned this Jun 6, 2024
@Elblinator
Copy link
Member

Elblinator commented Jun 7, 2024

It should NOT be possible to update the base list of genders

@hjanott
Copy link
Member

hjanott commented Aug 16, 2024

The meeting export should export genders as strings while the meeting import should convert strings to ids. Thus a migration in memory is not needed.
Reasoning: the exported data can be processed in a better way by third parties.

@hjanott
Copy link
Member

hjanott commented Aug 16, 2024

During a meeting import existing users should not be updated with the gender field. Created users should get the imported gender.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants