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

Improve form deletion process. #15

Closed
amarder opened this issue Oct 4, 2011 · 2 comments
Closed

Improve form deletion process. #15

amarder opened this issue Oct 4, 2011 · 2 comments
Labels

Comments

@amarder
Copy link
Contributor

amarder commented Oct 4, 2011

  • Deletion should only hide a survey from the UI.
  • This will allow submissions for this survey to continue if a phone still the XForm on it.
  • This will prevent the user from creating another survey with this ID. This is actually a good thing so that old versions don’t get mixed in with a newer version with the same ID.
@amarder amarder closed this as completed Oct 7, 2011
@prabhasp
Copy link
Contributor

Hey Andrew, I have a comment on this, and I think we have to work on this a little more. Basically, I see the issue that you raised above, which makes this tricky. But right now, we aren't letting people iterate on surveys in a good way. In a real life use case, you'll need to go through a survey many times before its perfect (and even then...).

So can I propose the idea of a sandbox, where deletion works differently, in that forms can de deleted forever, and the data alongside with it?

Then, we have another set that is not sandboxed, and which we assume are in deployed in "real life".
Actually, the way I am thinking is that this second set would be either in a state of "deployment" or "archival." Deployed surveys can be archived, but can never be deleted, for the reason you mentioned above. (Plus, there is data associated with it!) Archived surveys just sit there, and can be brought back into deployment, but again, can never be deleted.

whatcha think?

@prabhasp
Copy link
Contributor

Okay, I'm going to make a new issue based on this idea of a sandbox, because needing to iterate on forms is a crucial thing that formhub should allow IMO. We can discuss on that issue how best to do it though.

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

No branches or pull requests

2 participants