-
Notifications
You must be signed in to change notification settings - Fork 354
[ENG-8740] Ability to delete a file from a registration via admin #11285
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
base: feature/pbs-25-25
Are you sure you want to change the base?
[ENG-8740] Ability to delete a file from a registration via admin #11285
Conversation
…nterForOpenScience#11246) * remove csrf protection from reset password endpoint * update test
[ENG-8656] Clean up password reset throttle error
…NG-8552 Fix/eng 8552
…x/ENG-8743 [ENG-8743] subscribe_osf_general_email settings is not updated
…#11271) * use same logic for admin and web password reset * fix tests
…x/ENG-8742 [ENG-8742] include ignored components when create a view-only link
…om user side to avoid inconsistency
|
@mkovalua Could you rebase this onto the latest |
1 similar comment
|
@mkovalua Could you rebase this onto the latest |
|
hi @adlius, I have resolved merge conflicts with |
|
LGTM |
ihorsokhanexoft
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
well done
|
@mkovalua Could you rebase this onto the latest |
|
@Ostap-Zherebetskyi I have rebased |
Purpose
Frequently users inadvertently include personal identifying information in files associated with Registrations. It becomes imperative for these files to be removed as soon as possible. While any solution to https://openscience.atlassian.net/browse/ENG-8547 would also solve this issue, the most important piece of that analysis is the removal of the file containing the personal identifying information. This function is currently only able to be completed by a Cloud engineer, enabling this function in the admin app would reduce Cloud engineer time and allow for faster resolution to user mistakes with including personal identifying information in files.
Changes
implementation of business logic and UI to delete specified file by guid
Screen.Recording.2025-09-09.at.17.06.41.1.mp4
QA Notes
What are the areas of risk?
Any concerns/considerations/questions that development raised?
not confident about
usage
it looks like
reg.registered_meta[reg.registered_schema._id]may be used properly only for DraftRegistration for nowand
reg.schema_responses.latest('created')will raise Not Exist error if there is no recordmaybe try: except approach is ok, maybe some additional logic is expected
Documentation
Side Effects
Ticket
https://openscience.atlassian.net/browse/ENG-8740