Closed Bug 972414 Opened 12 years ago Closed 12 years ago

add export to analyzer search

Categories

(Input Graveyard :: Search, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: willkg, Assigned: willkg)

References

Details

(Whiteboard: u=analyzer c=search p=2 s=input.2014q1)

Analyzers need to be able to download the data in some structured form that they can use with other tools. This bug covers implementing a CSV download for analyzer search data.
Assignee: nobody → willkg
Blocks: 966425
Whiteboard: u=analyzer c=search p=2 s=input.2014q1
Tweaking subject to be clearer. It might be helpful/interesting to have export explicitly require you to state you want private information in the export.
Summary: add structured download to analyzer search → add export to analyzer search
Tossing this url in here. I think this is how I want to implement this: https://docs.djangoproject.com/en/dev/howto/outputting-csv/ However, I'm concerned about generating massive files which could stress the system. We probably want to limit the number of rows that can be exported at once to like 1000. If we do that, we need some way to denote that we limited the export. Could be as easy as adding a row at the end along the lines of "Truncating n rows...".
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Oops--meant to say "pushed to prod just now".
Product: Input → Input Graveyard
You need to log in before you can comment on or make changes to this bug.