You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As an admin, I want to export a custom CSV after searching in the backend so that I can use the backend’s search functionality to create targeted data sets.
#444
Closed
6 tasks done
rlskoeser opened this issue
Jul 27, 2022
· 3 comments
try exporting all records; should work similar to before, except that you'll have to choose which format you want
try selecting a subset of records from the list view and use the action to export
second round testing:
clusters are next to collections and output cluster id instead of database id
downloading all records should be a bit faster than before
Note: the field/column names in the new export are based on the field names in the code, which is a change from our previous export CSVs; I would prefer to keep them this way, because it will be much easier for anyone working with the exports in code. If you feel strongly about it I can add logic to override the labels so they match what they were previously.
dev notes
Remove old DigitizedWorkCSV view and links
configure and use django-import-export; use the same fields as the existing csv export
The text was updated successfully, but these errors were encountered:
Exporting all records works great (takes a few seconds to download, but lag time isn't too bad) - I tried xlsx and csv. I think it's fine to keep the name labels as is matching the code.
One thing: There's a cluster column, but instead of the alphanumeric IDs we gave them, they're all numbers. You mentioned this was because you forgot to exclude cluster, but it might be good to keep cluster on the export and show the alphanumeric IDs we input, if possible? And could we move it near collections?
Exporting a subset after searching is SO powerful! I tested with "ballad" and with "for use in schools." It successfully works via the action button and via the export button.
This looks great! Thank you for making the adjustments to the cluster column. I retested exporting the full set and a subset after search. (FYI, the speed still isn't great for the full set but it's not horrendous.)
testing notes
in django admin digitized work list view:
second round testing:
Note: the field/column names in the new export are based on the field names in the code, which is a change from our previous export CSVs; I would prefer to keep them this way, because it will be much easier for anyone working with the exports in code. If you feel strongly about it I can add logic to override the labels so they match what they were previously.
dev notes
DigitizedWorkCSV
view and linksThe text was updated successfully, but these errors were encountered: