Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

Exporting data sets from the Explorer #371

Closed
vforgione opened this issue Jul 19, 2018 · 0 comments
Closed

Exporting data sets from the Explorer #371

vforgione opened this issue Jul 19, 2018 · 0 comments
Assignees
@vforgione
Labels
ETL Work related to ingest and export pipelines. Front End Work related to the web apps. Task Work that is not bug related.

Comments

@vforgione
Copy link
Member

vforgione commented Jul 19, 2018 •
edited
Loading

Users should be able to export data set from the explorer. The exported results should be for a single data set, and should only include the records of the data set that match the fall within the selected time range and bbox. We should also add a notice to the user about these restrictions, and prompt them to visit the data source if they want the complete data set.

Story #373
@vforgione vforgione added the Story Organizes issues into a coherent deliverable. label Jul 19, 2018
@vforgione vforgione mentioned this issue Jul 19, 2018
Closed
@vforgione vforgione added Task Work that is not bug related. ETL Work related to ingest and export pipelines. Front End Work related to the web apps. and removed Story Organizes issues into a coherent deliverable. labels Jul 23, 2018
@vforgione vforgione added this to the Sprint 3 milestone Jul 23, 2018
@vforgione vforgione self-assigned this Aug 21, 2018
@vforgione vforgione removed this from the Sprint 3 milestone Aug 24, 2018
vforgione pushed a commit that referenced this issue Aug 24, 2018
Updated Data Set Export
5ecf9e1 
Since we don't really have all that great of an export strategy anymore
(we've made a lot of changes to our IO workers without giving any love
to the export process), it just makes sense at the moment to open a
blank tab and send the user to the source document.

I've updated the name of the link to _Download a Copy_ rather than
exporting to make it not seem like the users are going to just get a
view of the data set that matches their query -- the ideal export
functionality.

This still needs to fixed soon, but as we are rapidly approaching
release I don't want to screw around with big stuff like this.

Updates #371
@vforgione vforgione mentioned this issue Aug 24, 2018
Merged
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees

@vforgione vforgione

Labels
ETL Work related to ingest and export pipelines. Front End Work related to the web apps. Task Work that is not bug related.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@vforgione