#521 Add Export to CSV for Queue Details and Enhance Admin Configuration

[hanzheg]

We add a feature to export selected Queue details to a CSV file, including associated Meeting and Attendee data, improving administrative functionality.

[zqian]

@hanzheg The PR works for me.

The downloaded csv file contains those fields:

Queue ID, Queue Name, Status, Created At, Hosts, Allowed Backends, Description, Meeting Count, and Attendee Count

vs if one uses the current Download feature inside the /manage page, the downloaded csv file contains fields of:

queue_id,attendee_id,attendee_user_id,attendee_uniqname,attendee_last_name,attendee_first_name,host_id,host_uniqname,host_last_name,host_first_name,meeting_type,meeting_url,agenda,meeting_created_at

Can you make the admin export be consistent with same fields?

[jonespm]

Thanks for the contribution but I don't think this is really what we were looking for here.

There's an existing method that was added to the views.py for ExportMeetingStartLogs.

To fix this one for admin I'd probably do a few things that I should have mentioned on the issue.

1. Probably refactor the database logic from that method either into the models.py MeetingStartLogsView proxy or into a separate utils file.
2. Rewrite this to be less memory intensive, avoid a fetchall and instead have a loop that does a fetchmany
3. Have a parameter for whether or not to do the filter by user. (To make it work for admins)
4. Call this method from where you are defining the admin action.

I can add some more detail to the ticket, some of these might be subtasks.