Sharing data: Difference between revisions

Jump to navigation Jump to search
clarify paragraph on ancestor directories
(Marked this version for translation)
(clarify paragraph on ancestor directories)
Line 147: Line 147:
In order for this method to work the following things need to be in place:
In order for this method to work the following things need to be in place:
* The directory, <code>/home/smithj/projects/def-smithj/shared_data</code> in our example, must be owned by you.  
* The directory, <code>/home/smithj/projects/def-smithj/shared_data</code> in our example, must be owned by you.  
* All parent directories of the one you are trying to share should allow public entry (i.e. o+x permissions), or at the least execute ACLs for the person you are trying to share with (i.e. <code>u:smithj:r</code> in this example). They do not need to have public read permission, unless the owner decides to allow it. In practical terms, this means that the project directory (/projects/def-<PI>) must give permission for either everyone, or at least the people you are trying to share your data with, execute permission on the project directory.
* Parent directories (and parents of parents, etc.) of the one you are trying to share must allow execute permission to the user you are trying to share with. This can be supplied with <code>setfacl u:smithj:x ...</code> in this example, or it can be supplied by allowing everyone entry, i.e. <code>chmod o+x ...</code>. They do not need to have public read permission. In particular you will need to grant execute permission on the project directory (<code>/projects/def-someone</code>) either for everyone, or one-by-one to all the people you are trying to share your data with.


=== Data Sharing Groups === <!--T:30-->
=== Data Sharing Groups === <!--T:30-->
Bureaucrats, cc_docs_admin, cc_staff
2,915

edits

Navigation menu