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

Add delete administration capability #122

Closed
dgets opened this issue May 7, 2019 · 1 comment
Closed

Add delete administration capability #122

dgets opened this issue May 7, 2019 · 1 comment
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@dgets
Copy link
Owner

dgets commented May 7, 2019

It's time to add this as more than just a function of the admin panel. People do, after all, make mistakes sometimes.

When #90 is completed, it would be good to add this capability for other users, as well. Perhaps this should come after #90 is implemented.

@dgets dgets added the enhancement New feature or request label May 7, 2019
@dgets dgets added this to the next alpha milestone May 7, 2019
@dgets dgets self-assigned this May 7, 2019
@dgets
Copy link
Owner Author

dgets commented May 10, 2019

I think that the way we'll work this view is that without a POST value, we'll display a listing of all administrations for the particular user. They will be in a table, with checkboxes next to them, in order to select them for deletion. Of course there will be a select all option, as well, as the number of administrations may be huge.

There will also be a field (probably a drop-down selection) that will allow filtering of those results per-substance. If the POST value contains a hidden field value that is sent along with that particular separate form, then the views.py code will only display that particular substance's entries for the user.

Finally, of course, if any administrations or select all is checked, the following administrations will be confirmed for deletion and wiped from the database. A hidden field value may be used to determine this as well, though checking for null values within certain form elements may be possible, as well.

Upon addition of user groups (#90), this will be available for other users, as well as just the currently logged in one.

dgets added a commit that referenced this issue May 10, 2019
…e for deletion and the associated template en route to #122.
dgets added a commit that referenced this issue May 10, 2019
…st in the template properly displaying the previously selected administrations for confirmation of delete. En route to #122.
dgets added a commit that referenced this issue May 10, 2019
…n proper testing for conditions of view.py's display; en route to #122.
@dgets dgets closed this as completed in 06747a5 May 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant