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

Introduce a time limit on how long datasets are kept within a user directory #36

Open
Steffengreiner opened this issue Feb 12, 2025 · 0 comments
Labels
complex Implementation effort feature

Comments

@Steffengreiner
Copy link
Contributor

What are you missing?

Currently, there is no time limit on how long a dataset can be stored within the user directory. This is especially cumbersome, since erroneous uploads are redirected to the error directory, where they are stored until a user does (or forgets) manually delete it. This can accumulate if multiple failed uploads are provided.

Why do you need a solution?

1.) The uploaded datasets are not processed and take up space within the user home directoy and our system.
2.) Accumulation of error directories make it harder to track the current progress of an upload.
3.) Datasets should be linked and accessible to the correct metadata within the data manager, otherwise the FAIR principles are violated.

Ideas

1.) Introduce a cronjob/script checking if the modification date of a dataset within the users home directoy is above a certain time threshold.
Ideally inform the user automatically a week before the dataset will be deleted via email from the linked LDAP account.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complex Implementation effort feature
Projects
Status: No status
Development

No branches or pull requests

1 participant