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

Revision of the /data/ section to make it more useful #669

Open
rkdarst opened this issue Oct 11, 2023 · 2 comments
Open

Revision of the /data/ section to make it more useful #669

rkdarst opened this issue Oct 11, 2023 · 2 comments

Comments

@rkdarst
Copy link
Member

rkdarst commented Oct 11, 2023

This section was made a long time ago, and is barely even maintained. Many of the generic data-related things are now on aalto.fi and the version on scicomp.aalto.fi should be removed.

I propose that the /data/ section centralize data-related things focused on scientific computing: for example requesting data storage space on the cluster/in our departments and some of the tools necessary for processing large amounts of data efficiently.

I'd start with a clean slate and only transfer in content which is known to be useful.

@anttirousi
Copy link
Contributor

Yes, this is a good suggestion

@rkdarst rkdarst changed the title The /data/ section is old and outdated Revision of the /data/ section to make it more useful Oct 12, 2023
@rkdarst
Copy link
Member Author

rkdarst commented Oct 12, 2023

Pages which can be moved to /data/:

  • aalto/aaltostorage (storage places available)
  • aalto/aaltodata (how to use the storage to manage data. for example requesting space. This and the previous page should be remxied to make more sense)
  • aalto/datapolicy (science-IT data policy)
  • aalto/remoteaccess (the data parts)
  • aalto/opensource
  • triton/tut/{storage,remotedata} probably stay where they are, but some common parts (mounting or rsync or sshfs) could be moved to the new /data/ section.

Any comments on how to do a rearrangement well?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants