Skip to content
This repository has been archived by the owner on Jan 9, 2023. It is now read-only.

A separate screen for handling permanent deletion of archived data #384

Closed
tangollama opened this issue Mar 19, 2016 · 2 comments
Closed
Labels
🚀enhancement an issue/pull request that adds a feature to the application help wanted indicates that an issue is open for contributions wontfix indicates an issue/pull request will not be worked on

Comments

@tangollama
Copy link
Member

Once #380 and #381 are completed, we need a screen where:

[ ] archived items can be deleted in mass (i.e. delete all items that have been archived for 6 months or more
[ ] a specific archived item can be searched for a deleted permanently

@tangollama tangollama added 🚀enhancement an issue/pull request that adds a feature to the application Data integrity labels Mar 19, 2016
@tangollama tangollama modified the milestone: HospitalRun 1.0 Mar 19, 2016
@pete-the-pete
Copy link
Contributor

How will permissions for this page work? As in, are there restrictions around which type of users would have access to see the page, or delete certain records?

How should the data be organized? Would you want to filter or sort the data in anyway?

@tangollama tangollama added Hack Day help wanted indicates that an issue is open for contributions labels Sep 17, 2016
@stale
Copy link

stale bot commented Aug 7, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix indicates an issue/pull request will not be worked on label Aug 7, 2019
@fox1t fox1t closed this as completed Aug 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
🚀enhancement an issue/pull request that adds a feature to the application help wanted indicates that an issue is open for contributions wontfix indicates an issue/pull request will not be worked on
Projects
None yet
Development

No branches or pull requests

4 participants