Skip to content
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

Copy-edit - remove the “to”: “We recommend you export your dataset before deleting.” #2433

Closed
saleiva opened this issue Feb 23, 2015 · 7 comments · Fixed by #2499
Closed
Assignees
Milestone

Comments

@saleiva
Copy link
Contributor

saleiva commented Feb 23, 2015

No description provided.

@saleiva saleiva added this to the Guarrate milestone Feb 23, 2015
@saleiva
Copy link
Contributor Author

saleiva commented Feb 23, 2015

Also, include a warning that won’t be able to retrieve the dataset after delete it - permanently deleted from CartoDB.

@viddo
Copy link
Contributor

viddo commented Feb 23, 2015

But last week we changed the copy to not say anything about exporting since it cannot be done yet. Does this change make sense?

@saleiva
Copy link
Contributor Author

saleiva commented Feb 23, 2015

You can export datasets, not maps. This is for datasets.

@viddo
Copy link
Contributor

viddo commented Feb 23, 2015

Aha, I see, so there's a difference between datasets and maps, thanks for clarifying. However, I don't think it makes sense to mention anything about exporting until that is implemented, which was dropped/postponed in a earlier discussion, we probably need to revisit this again before doing this change.

@saleiva
Copy link
Contributor Author

saleiva commented Feb 23, 2015

Exporting datasets is already possible, not in batch, but yes one by one. Since it's a possible workaround and deleting is something very sensible from the user perspective I'd implement this change in the text now.

@viddo
Copy link
Contributor

viddo commented Feb 23, 2015

(Export dialog is not implemented for single items either yet](#1658), due to the previously mentioned decision it was postponed. So in that case I propose that we should implement it and fix the copy together with those changes.

@saleiva
Copy link
Contributor Author

saleiva commented Feb 23, 2015

Even if not being to export tables from the dashboard, it's possible from the table view.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants