-
Notifications
You must be signed in to change notification settings - Fork 30
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
Provide a way for admins to export everything #521
Comments
Hello @jonespm, My partner and I are students in the EECS 481 course, and we would like to work on this ticket as part of our open-source project contribution assignment. Could you please assign this task to me? Thank you! |
Sure @hanzheg this might be a little harder one but you're welcome to try it. I think my idea was that we'd add a new custom action to the Django admin for queues. Right now there's 3 options, Delete, Hard Delete and Soft Delete. You'd be able to check the ones you also want to export and it would run it through the export code and provide an export. The ones that are a little easier are ones with the label off "Effort: 4" and/or "Good First Issue." |
I'm thinking maybe something like this for the refactored model method Then you'd pass like
|
It was requested that admins should be able to get a full export of the view. This may need to be something built in as a custom admin interface. I'm not sure the effort around this or if it would be worth putting in that time to complete this task as currently devs can export CSV's right from the view on the database.
Related to this was a way for department chairs and managers to export all of the reports for employees they manage. I'm not sure how that would be implemented and/or if it would be similar to this.
Originally posted by @jonespm in #97 (comment)
Some additional implementation details, these may be subtasks.
ExportMeetingStartLogs.get
either into the models.pyMeetingStartLogsView
proxy or into a separate utils file.fetchall
and instead have a loop that does afetchmany
The text was updated successfully, but these errors were encountered: