Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. We usually create the folders with the names group01, group02, group03, ... to ensure consistency in naming.

  2. The following permissions are used for the group folders:

    1. The instructor of the class is the owner of the folders and has rwx permissions to the folders. The instructor can view, copy and edit files inside the folders.

    2. For each group folder:

      1. The instructor can add specific students to each group folder using Access Management, as outlined in the section below. The students who are given access to the folder will have rwx permissions to that folder. Those students can view, copy and edit files inside the folder. (However, we do not recommend editing Jupyter notebooks or R script files in the group folders. Please see this section on suggested usage for the group folders.)

      2. Everyone else in the class will have no permissions to view files inside the folder. That way, only members of a group can view files inside their group folder.

  3. The group folders are created inside the classdata folder, because classdata is a shared location that can be accessed by more than 1 student in the class.

Infonote

Even though students in a group will be given rwx permissions to their group folder, we do not recommend editing Jupyter notebooks or R script files in the group folders.

Please see this section below:

Suggested usage for the group folders

Group folders can help students share files with each other. However, they have some limitations.

...

Limitations of the group folders:

  • We do not recommend editing Jupyter notebooks in the group folders can cause . Students may run into permissions issues.

    • Jupyter automatically creates a hidden folder called .ipynb_checkpoints. This hidden folder might not follow the permissions that were set when we created the group folders .

    • The .ipynb_checkpoints folder will be owned by 1 student, preventing the other students in the group from creating or editing notebooks in the group folder.

  • In Similarly, in RStudio, new .R files might not automatically follow the permissions that were set when we created the group folders.

  • Multi-user editing is not supported. If a student has a Jupyter notebook open in their account, another student will not be able to save changes to that same notebook. Similarly for .R script files.

Suggested workflows for these group folders:

  • Each student creates a copy of works on their own .R script scripts or Jupyter notebook notebooks in their IDAS home directory, outside of the classdata folder.

  • When students are ready to share their .R scripts or Jupyter notebooks with their team members, they can copy & paste the finished script file files or notebook notebooks into the group folder.

  • These example Linux commands may help troubleshoot permissions issues : in the group folders.

Add users to group folders using Access Management

...

Code Block
cd ~/classdata/group01
ls -al

It’s generally not a good idea for different group members to run the same Jupyter notebook in the shared group folder. Doing that can make everyone share the same hidden checkpoints file and can cause some issues. We suggest that each group member keep their own version of the notebook
Info
Note

Even though students in a group will be given rwx permissions to their group folder, we do not recommend editing Jupyter notebooks or R script files in the group folders.

Please see this section on suggested usage for the group folders.

Other support articles

...