You just pick the logical set of data and define the people it needs to be shared with, then we create the project for you and update the list of people as time goes on so that it's always correct. They're a secure, convenient way to share data.
Please note that only the PI who owns that data may apply for, or request modifications to, a collaboration project.
- Ask for a new person to be added to the project
- Request that the ownership of any data be transferred to another member of the project; this is especially useful when someone leaves the lab
- Ask for quota to be transferred from one project to another at no cost; this includes creating a new project from unused quota in another, as well as closing one project to increase the quota of another (assuming the data has been moved)
If you're the PI of a project and would like to do any of these, please contact us via help@imm.ox.ac.uk .
/project/ccbadmin/
/dtooke/
/emacmahon/
/shared/
/datashare/
Each project member gets their own directory - only the owner can add, remove or modify contents. Each project gets two additional directories: shared and datashare. Any project member can write data into shared; datashare is similar except its contents are publicly accessible from Internet - see datashare(7) for details. With the exception of datashare, all project data access is restricted to project members for confidentiality. Everything within a project is read-only readable by all other project members for collaboration.
If you're absolutely positive that you want to make data editable by more than one person, and you're happy to risk permanent and irreversible data corruption and/or loss , the owner of the data can change the permissions as normal using chmod(1).
Please ask the PI in charge of the project to contact us via help@imm.ox.ac.uk and ask for your username to be added.
- You should aim to create a collaboration project for a set of logically connected data, e.g. a specific research project. Creating a collaboration project for a list of people and then thinking about the data they may want to share will risk that you end up with poorly defined data boundries and have to unentangle the data at a future data.
- You should create a new collaboration project for each logically separate set of data. Adding different data to an existing collaboration project and then adding more people will likely lead to the same problems described above.
- Please tell us if the permissions on the data in your project aren't working for you. Trying to work around an issue on your own is more likely to make the problem worse and take longer overall.
- Please tell us if someone leaves the project and no longer needs access to the data. Leaving accounts with access to data they don't need is a security and privacy risk.
1. Decide the purpose of the project. Each project should be for a single requirement, e.g. data for a lab or data for a research project. If different people need access to different logical data sets, these should be multiple projects. Simmarly, if the same people need access to different logical data sets, these should also be multiple projects
2. Choose a name for the project that isn't already in use in /project/
3. Decide which user accounts should have access to the data
4. Decide how much space you think you'll need (in multiples of 1 TB)
5. Follow the steps detailed in accounts(7).
/home/some_directory/USERNAME/ : ideal for small private data such as documents or configuration files which are private to you
/project/project1/USERNAME/ : used to store data which is part of project1 but won't typically be used by other people
/project/project1/shared/ : used to store data which is part of project1 and is likely to be used by multiple people