Workspace: Allocation vs. creation

General Documentation Issue

Issue Type

  • Error in documentation
  • Missing documentation
  • Outdated information
  • Other: Consistency in wording

Describe the Issue

Every time I create a workspace I first start typing ws_create until I realize it is ws_allocate. I don't know if that is sensible, but it at least trips me up.

Location of the Issue

git grep -e "create.*workspace"
doc.zih.tu-dresden.de/docs/software/tensorboard.md
60:Then, create a workspace for the event data, that should be visualized in TensorBoard. If you

doc.zih.tu-dresden.de/docs/jobs_and_resources/alpha_centauri.md
115:    As first step, you should create a workspace

doc.zih.tu-dresden.de/docs/data_lifecycle/workspaces.md
241:    This command will create a workspace with the name `test-workspace` on the `/horse` filesystem
632:When a workspace is created with the option `-g, --group`, it gets a group workspace that is visible
641:    Nevertheless, you can create a group workspace for any of your groups following these two
683:**Q**: I am getting the error `Error: could not create workspace directory!`

doc.zih.tu-dresden.de/docs/quickstart/getting_started.md
141:First, it is shown how to create a workspace, then how to transfer data within and to/from the ZIH
147:You need to create a [workspace](../data_lifecycle/workspaces.md) for your data on one of these
156:    The following command creates a workspace
246:**By default, workspaces are accessible only for the user who created the workspace.**
438:marie@compute$ cd /data/horse/ws/marie-number_crunch/ #go to your created workspace

doc.zih.tu-dresden.de/docs/access/jupyterhub_for_teaching.md
132:To provide a consistent Python environment, you can create a shared [workspace](../data_lifecycle/workspaces.md)

Expected Documentation

Use consistent wording in the documentation, i.e., "a workspace is allocated".

Suggested Fix or Improvement

Carefully check which "create"-phrase should be reformulated into a "allocated"-phrase.

Thank you for helping improve our documentation!

Nutzungsbedingungen | Datenschutzerklärung | Barrierefreiheitserklärung