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 dataset limitations for the to be registered datasets. #37

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

Comments

@Steffengreiner
Copy link
Contributor

What are you missing?

Currently, there are no limitations on the type of files or file sizes of the to be stored datasets. As long as the directory tree is linked correctly to the measurements, the users can freely register any kind of data to their measurements. While this is permissive and easy-to-use, it opens up multiple vulnerabilties.

Why do you need a solution?

1.) Users are able to upload personalized data, which would violate legal requirements.
2.) Users are able to misuse our service as a personal archive system, flooding our server with unusable data.
3.) Without some sort of file validation have no way to curate incoming datasets for completeness or accuracy.

Ideas

1.) Introduce a user based storage limit, within the upload server and datastore server which can't be exceeded.
2.) Introduce a policy within the data manager ecosystem which informs the user of the kind of data we support and don't support.
3.) Introduce dataset validators, which checks for file quality and file availability dependent on the domain requirements.

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