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

excel list out of existing vocabulary in cms #468

Closed
jennyharmslunes opened this issue May 4, 2023 · 2 comments · Fixed by #521
Closed

excel list out of existing vocabulary in cms #468

jennyharmslunes opened this issue May 4, 2023 · 2 comments · Fixed by #521
Assignees
Milestone

Comments

@jennyharmslunes
Copy link

Motivation

possibility to extract an excel list containing vocabulary already existing in the cms for each "berufsbild"

Proposed Solution

https://issues.tuerantuer.org/browse/IDEA-58

Alternatives

Additional Context

@JoeyStk JoeyStk added this to the 23Q3 milestone Jun 27, 2023
@JoeyStk JoeyStk self-assigned this Jul 18, 2023
@JoeyStk
Copy link
Contributor

JoeyStk commented Jul 18, 2023

@timoludwig I have tried a solution for this issue on the branch feature/export_to_excel. I didn't open a PR for it, because I'm not sure that what I have is the best solution for it. I tried using the csv library. After playing around with it for a while now, I'm not sure this is the best library for it, because of two reasons: a. the csv library only exports to csv files. I think in most cases this should be sufficient since Excel supports also csv, but there might be edge-cases in which we would need a .xls(x)-file and b. as far as I could tell it's not possible to create more than one CSV file. However I would expect, that if I select three disciplines that I get one csv file for every discipline (ideally also named after that discipline). But since the export works via the return of the response, I couldn't figure out a way to have more than one file. For now I appended all selected discipline in the same file (also not sorted).
Do you think it's worth the effort to spend more time on the csv library and try to fix the mentioned issues or do you think I should rather try a different library (for example import-export or pandas)

@timobrembeck
Copy link
Member

@JoeyStk Before trying to implement the export ourselves, I think we should first try to get this up and running:

https://django-import-export.readthedocs.io/en/latest/

If it doesn't work out for whatever reason, we can continue looking for alternatives that require more manual work.

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

Successfully merging a pull request may close this issue.

4 participants