Changes for page Managing HDC Projects

Last modified by Dennis Segebarth on 2026/02/26 10:29
From version 4.1
edited by Susan Evans
on 2023/07/14 17:10
Change comment: There is no comment for this version
To version 24.1
edited by Dennis Segebarth
on 2026/02/26 10:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.sgevans
1 +XWiki.dsegebarth
Content
... ... @@ -2,6 +2,10 @@
2 2  {{toc depth="2"/}}
3 3  {{/box}}
4 4  
5 +{{warning}}
6 +**Disclaimer:** This article may contain screenshots from other Pilot-based deployments. Differences only apply to variations in branding and color schemes, not the functionalities covered in this article, though.
7 +{{/warning}}
8 +
5 5  This section of the User Guide describes the features available to Project Administrators to manage their Project.
6 6  
7 7  Each Project is owned by a Project Administrator, a role analogous to an academic Principal Investigator. More than one person can hold the Project Administrator role, allowing for role delegation and backup. Creation of your own Project can be requested by submitting an inquiry (see //Contact Us//).
... ... @@ -18,7 +18,7 @@
18 18  
19 19  When the Platform Administrator creates your Project, the Name and Code are assigned and other general information may have been initialized. The Project Code cannot be changed, but as a Project Administrator you can edit the other Project’s General Information in the Project **Settings **page (not available to regular Project members).
20 20  
21 -[[image:Manage Projects Settings v2.1.5 2023-01-30.png||height="19%" width="20%"]]
25 +[[image:1723654603707-412.png||height="269" width="282"]]
22 22  
23 23  
24 24  To edit your Project’s General Information (Project Administrator role),
... ... @@ -85,7 +85,7 @@
85 85  
86 86  Copying files from the //Green Room// to the //Core //can only be performed by users with the Project Administrator role in the corresponding Project, or by Platform Administrators.
87 87  
88 -[[image:Manage Projects Copy to Core v2.1.5 2023-01-31.png||height="10%" width="50%"]]
92 +[[image:1723654635472-816.png||height="184" width="886"]]
89 89  
90 90  1. In the Project File Explorer, open the **Green Room** and navigate to the folder where the file(s) are stored.
91 91  1. Select one or more files and/or folders to be copied by clicking the checkbox beside each one, then select **Copy to Core**.
... ... @@ -103,7 +103,7 @@
103 103  
104 104  Project Administrators are notified about pending Copy to Core requests with a red notification dot on the **Requests icon**. The following steps describe how to review, approve, and/or deny Copy to Core requests:
105 105  
106 -[[image:Projects Requests Left Menu v2.3.3 2023-04-26.png||height="16%" width="30%"]]
110 +[[image:1723654648402-919.png||height="301" width="558"]]
107 107  
108 108  (((
109 109  1. Click the **Requests icon** from the Project left menu bar and view the tab **Copy Data To Core Request**.
... ... @@ -113,7 +113,7 @@
113 113  1. When at least one file or folder is selected, two options become visible at the top of the file explorer table. Click one of the following:
114 114  1*. **Approve Selected** to copy the selected files/folders to be copied to the Core.
115 115  1*. **Deny Selected** if you do not wish to copy the selected files/folders to the Core.
116 -[[image:Manage Projects Approve or Deny Copy to Core v2.1.5 2023-01-31.png||height="16%" width="50%"]]
120 +[[image:1723654669740-995.png||height="273" width="853"]]
117 117  1. A confirmation code is randomly generated. Type the code in the entry box and then click **Approve **or **Deny** to confirm your intention.
118 118  1. Another popup confirms the action was completed. Click **Close** to dismiss.
119 119  )))
... ... @@ -124,7 +124,7 @@
124 124  
125 125  After Approving or Denying every file/folder in the request, it’s time to close the request and notify the user. To close the request,
126 126  
127 -[[image:Manage Projects Close Copy to Core Request v2.1.5 2023-01-31.png||height="10%" width="50%"]]
131 +[[image:1723654683455-327.png||height="170" width="865"]]
128 128  
129 129  
130 130  1. Click **Close Request & Notify User**.
... ... @@ -151,7 +151,7 @@
151 151  
152 152  Project Administrators have the flexibility to add or remove Project members, and change users' roles within the Project.
153 153  
154 -[[image:Manage Projects Members v2.1.5 2023-01-30.png||height="19%" width="20%"]]
158 +[[image:1723654696855-544.png||height="326" width="342"]]
155 155  
156 156  
157 157  To manage Project membership for your Project as Project Administrator role,
... ... @@ -164,7 +164,7 @@
164 164  
165 165  Project Administrators can add new members to the Project:
166 166  
167 -[[image:Manage Projects Add Member v2.1.5 2023-02-01.png||height="6%" width="50%"]]
171 +[[image:1723654713217-983.png||height="111" width="869"]]
168 168  
169 169  
170 170  1. Launch your Project and open the **Project Members** page, then click **+ Add Member**.
... ... @@ -199,6 +199,20 @@
199 199  |Upload and annotate files from from Workspace to Project Core (via Command Line Interface)|(% style="text-align:center" %)☑️ Allowed|(% style="text-align:center" %)☑️ Allowed|
200 200  |Download files from Project Core own folder|(% style="text-align:center" %)☑️ Allowed|(% style="text-align:center" %)☑️ Allowed|
201 201  |Download files from Project Core any folder|(% style="text-align:center" %)☑️ Allowed|(% style="text-align:center" %)☑️ Allowed|
206 +|(% style="background-color:#dcdcdc; text-align:center" %)**Activity**|(% colspan="3" rowspan="1" style="background-color:#dcdcdc; text-align:center" %)**Trash Bin File Operations**
207 +| |(% style="background-color:#edf1f4; text-align:center" %)**Project Administrator**|(% style="background-color:#edf1f4; text-align:center" %)**Project Collaborator**|(% style="background-color:#edf1f4" %)**Project Contributor**
208 +|View own files moved to Trash Bin from Green Room|(% style="text-align:center" %)☑️ Allowed|(% style="text-align:center" %)☑️ Allowed|(% style="text-align:center" %)☑️ Allowed
209 +|View all files moved to Trash Bin from Green Room|(% style="text-align:center" %)☑️ Allowed|(% style="text-align:center" %) |(% style="text-align:center" %)
210 +|Restore own files moved to Trash Bin from Green Room|(% style="text-align:center" %)☑️ Allowed|(% style="text-align:center" %)☑️ Allowed|(% style="text-align:center" %)☑️ Allowed
211 +|Restore all files moved to Trash Bin from Green Room|(% style="text-align:center" %)☑️ Allowed|(% style="text-align:center" %) |(% style="text-align:center" %)
212 +|Mark own files moved to Trash Bin from Green Room for deletion|(% style="text-align:center" %)☑️ Allowed|(% style="text-align:center" %) |(% style="text-align:center" %)
213 +|Mark all files moved to Trash Bin from Green Room for deletion|(% style="text-align:center" %)☑️ Allowed|(% style="text-align:center" %) |(% style="text-align:center" %)
214 +|View own files moved to Trash Bin from Core|(% style="text-align:center" %)☑️ Allowed|(% style="text-align:center" %)☑️ Allowed|(% style="text-align:center" %)
215 +|View all files moved to Trash Bin from Core|(% style="text-align:center" %)☑️ Allowed|(% style="text-align:center" %)☑️ Allowed|(% style="text-align:center" %)
216 +|Restore own files moved to Trash Bin from Core|(% style="text-align:center" %)☑️ Allowed|(% style="text-align:center" %)☑️ Allowed|(% style="text-align:center" %)
217 +|Restore all files moved to Trash Bin from Core|(% style="text-align:center" %)☑️ Allowed|(% style="text-align:center" %)☑️ Allowed|(% style="text-align:center" %)
218 +|Mark own files moved to Trash Bin from Core for deletion|(% style="text-align:center" %)☑️ Allowed|(% style="text-align:center" %) |(% style="text-align:center" %)
219 +|Mark all files moved to Trash Bin from Core for deletion|(% style="text-align:center" %)☑️ Allowed|(% style="text-align:center" %) |(% style="text-align:center" %)
202 202  |(% style="background-color:#dcdcdc; text-align:center" %) **Activity** |(% colspan="3" style="background-color:#dcdcdc; text-align:center" %)**User Management**
203 203  | |(% style="background-color:#edf1f4; text-align:center" %)**Project Administrator**|(% style="background-color:#edf1f4; text-align:center" %)**Project Collaborator**|(% style="background-color:#edf1f4; text-align:center" %)**Project Contributor**
204 204  |View, add, remove, manage Project members|(% style="text-align:center" %)☑️ Allowed| |
... ... @@ -213,6 +213,7 @@
213 213  | |(% style="background-color:#edf1f4; text-align:center" %)**Project Administrator**|(% style="background-color:#edf1f4; text-align:center" %)**Project Collaborator**|(% style="background-color:#edf1f4; text-align:center" %)**Project Contributor**
214 214  |Access Jupyterhub|(% style="text-align:center" %)☑️ Allowed|(% style="text-align:center" %)☑️ Allowed|
215 215  |Access Superset|(% style="text-align:center" %)☑️ Allowed|(% style="text-align:center" %)☑️ Allowed|
234 +|Access Guacamole VMs|(% style="text-align:center" %)☑️ Allowed|(% style="text-align:center" %)☑️ Allowed|(% style="text-align:center" %)
216 216  |Access XWiki|(% style="text-align:center" %)☑️ Allowed|(% style="text-align:center" %)☑️ Allowed|(% style="text-align:center" %)☑️ Allowed
217 217  
218 218  Note: Be reminded that Platform Administrators hold no Project specific role, and are, therefore, not listed in the table above. However, within each Project, they have - by default - the same permissions as a Project Administrator.
... ... @@ -258,7 +258,7 @@
258 258  
259 259  As Project Administrator, you can check the deployment status of Workspace tools by opening the Project **Settings** page and clicking the **Workspace** tab.
260 260  
261 -[[image:Manage Projects Workspace Deployment v2.1.5 2023-02-02 1517.png||height="24%" width="50%"]]
280 +[[image:1723654733035-792.png||height="409" width="869"]]
262 262  
263 263  
264 264  If you need a Workspace tool deployed for the project, please contact a Platform Administrator.
... ... @@ -267,6 +267,31 @@
267 267  
268 268  After Jupyterhub is deployed for the Project, members can click **Jupyterhub **in the Workspace icon group to launch their own Jupyter environment. Login is seamless with single sign-on - just click **Sign in with Keycloak**. See //Using Jupyterhub// for more details on how to use the application in the platform.
269 269  
289 +== Guacamole ==
290 +
291 +Apache Guacamole is a clientless remote desktop gateway that provides access to Project Virtual Machines (VMs). Guacamole is not automatically deployed when the Project is created. Project Administrators can submit a support request to have Guacamole and connected VMs deployed for their Project.
292 +
293 +After the Guacamole application and the VMs have been set up by a Platform Administrator, members can submit access requests for Guacamole-connected VMs (see //Using Apache Guacamole//) and Project Administrators can grant access to the requested VM(s) following the instructions below, //Granting Access to Guacamole VMs//.
294 +
295 +=== Granting Access to Guacamole VMs ===
296 +
297 +Project Administrators can grant access to Guacamole-connected Virtual Machines (VMs) requested by Project Members (including themselves).
298 +
299 +[[image:1723654749116-514.png||height="250" width="861"]]
300 +
301 +1. Launch your Project and click the **Requests** icon from the Project left menu bar.
302 +1. Click the **Guacamole VM Request** tab. The table displays Project members who have requested access. The Status column differentiates users whose VM access has been previously completed from those who are waiting for access.
303 +1. Please reach out to the Platform Admin by creating a support ticket and provide the following details:
304 +1*. The project code
305 +1*. The user who shall be granted access to a VM, including the associated email address
306 +1*. The VM for which access shall be granted
307 +1. Please wait for confirmation that the VM-specific account has been created before proceeding with step 5.
308 +1. In the VM column, select one or more connected VMs and click **Confirm Selection**.
309 +1. Click **Complete** to finish the setup.
310 +1. The requester will receive an email notification that their access was granted and they can launch Guacamole to access the selected VMs.
311 +
312 +See //Using Guacamole in HDC //for more details on how to use the application in the platform.
313 +
270 270  == Superset ==
271 271  
272 272  After Superset is deployed for the Project, members can click **Superset **in the Workspace icon group to launch their own Superset instance. Login is seamless with single sign-on, and users will have access to the visualization tools to design charts and visualizations, and the SQL lab to query the data in the project-specific database. See //Using Superset// for more details on how to use the application in the platform.
... ... @@ -279,7 +279,7 @@
279 279  
280 280  Project Administrators can use the **Announcements **page to send messages to all Project members to convey relevant Project news and information. Project Members can use this page to view Project announcements.
281 281  
282 -[[image:Manage Projects Announcements v2.1.5 2023-01-30.png||height="19%" width="20%"]]
326 +[[image:1723654770127-448.png||height="321" width="334"]]
283 283  
284 284  
285 285  To create a Project announcement as Project Administrator,
... ... @@ -296,7 +296,7 @@
296 296  
297 297  To create a new File Attribute template for your project as Project Administrator,
298 298  
299 -[[image:Manage Projects File Attributes v2.1.5 2023-02-01.png||height="7%" width="50%"]]
343 +[[image:1723654789441-207.png||height="114" width="864"]]
300 300  
301 301  
302 302  1. Launch your Project and click on the Project **Settings **icon.
... ... @@ -372,7 +372,7 @@
372 372  
373 373  Template created in the Project Settings menu:
374 374  
375 -[[image:Manage Projects File Attributes Example for JSON v2.1.5 2023-02-01.png||height="17%" width="50%"]]
419 +[[image:1723654813207-477.png||height="296" width="869"]]
376 376  
377 377  Corresponding JSON file format:
378 378  
... ... @@ -388,13 +388,9 @@
388 388  
389 389  ----
390 390  
391 -----
435 +Copyright © 2023-2026 [[Indoc Systems>>url:https://www.indocsystems.com]].
392 392  
393 -Copyright © 2023 [[Indoc Systems>>url:https://www.indocsystems.com]].
394 -
395 395  HealthDataCloud is powered by Pilot technology, a product of [[Indoc Systems>>url:https://www.indocsystems.com]].
396 396  
397 397  
398 398  
399 -
400 -
Manage Projects Add Member v2.1.5 2023-02-01.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.sgevans
Size
... ... @@ -1,1 +1,0 @@
1 -354.8 KB
Content
Manage Projects Announcements v2.1.5 2023-01-30.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.sgevans
Size
... ... @@ -1,1 +1,0 @@
1 -102.7 KB
Content
Manage Projects Approve or Deny Copy to Core v2.1.5 2023-01-31.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.sgevans
Size
... ... @@ -1,1 +1,0 @@
1 -549.4 KB
Content
Manage Projects Close Copy to Core Request v2.1.5 2023-01-31.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.sgevans
Size
... ... @@ -1,1 +1,0 @@
1 -298.8 KB
Content
Manage Projects Copy to Core v2.1.5 2023-01-31.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.sgevans
Size
... ... @@ -1,1 +1,0 @@
1 -188.8 KB
Content
Manage Projects File Attributes Example for JSON v2.1.5 2023-02-01.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.sgevans
Size
... ... @@ -1,1 +1,0 @@
1 -45.1 KB
Content
Manage Projects File Attributes v2.1.5 2023-02-01.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.sgevans
Size
... ... @@ -1,1 +1,0 @@
1 -289.0 KB
Content
Manage Projects Members v2.1.5 2023-01-30.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.sgevans
Size
... ... @@ -1,1 +1,0 @@
1 -94.5 KB
Content
Manage Projects Settings v2.1.5 2023-01-30.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.sgevans
Size
... ... @@ -1,1 +1,0 @@
1 -96.4 KB
Content
Manage Projects Workspace Deployment v2.1.5 2023-02-02 1517.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.sgevans
Size
... ... @@ -1,1 +1,0 @@
1 -667.4 KB
Content
Projects Requests Left Menu v2.3.3 2023-04-26.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.sgevans
Size
... ... @@ -1,1 +1,0 @@
1 -473.2 KB
Content
1723654603707-412.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.dsegebarth
Size
... ... @@ -1,0 +1,1 @@
1 +91.6 KB
Content
1723654635472-816.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.dsegebarth
Size
... ... @@ -1,0 +1,1 @@
1 +93.4 KB
Content
1723654648402-919.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.dsegebarth
Size
... ... @@ -1,0 +1,1 @@
1 +204.7 KB
Content
1723654669740-995.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.dsegebarth
Size
... ... @@ -1,0 +1,1 @@
1 +143.9 KB
Content
1723654683455-327.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.dsegebarth
Size
... ... @@ -1,0 +1,1 @@
1 +101.1 KB
Content
1723654696855-544.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.dsegebarth
Size
... ... @@ -1,0 +1,1 @@
1 +93.5 KB
Content
1723654713217-983.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.dsegebarth
Size
... ... @@ -1,0 +1,1 @@
1 +83.1 KB
Content
1723654733035-792.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.dsegebarth
Size
... ... @@ -1,0 +1,1 @@
1 +132.8 KB
Content
1723654749116-514.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.dsegebarth
Size
... ... @@ -1,0 +1,1 @@
1 +101.4 KB
Content
1723654770127-448.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.dsegebarth
Size
... ... @@ -1,0 +1,1 @@
1 +94.5 KB
Content
1723654789441-207.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.dsegebarth
Size
... ... @@ -1,0 +1,1 @@
1 +67.2 KB
Content
1723654813207-477.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.dsegebarth
Size
... ... @@ -1,0 +1,1 @@
1 +44.7 KB
Content