Changes for page Managing HDC Projects

Last modified by Dennis Segebarth on 2024/08/14 17:08
From version 5.1
edited by Susan Evans
on 2023/07/14 17:10
Change comment: There is no comment for this version
To version 1.16
edited by Susan Evans
on 2023/07/11 16:12
Change comment: (Autosaved)

Summary

Details

Page properties
Content
... ... @@ -1,7 +5,3 @@
1 -{{box cssClass="floatinginfobox" title="Table of Contents"}}
2 -{{toc depth="2"/}}
3 -{{/box}}
4 -
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//).
... ... @@ -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%"]]
102 +[[image:Projects Requests Left Menu v2.3.3 2023-04-26.png||height="27%" width="50%"]]
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**.
... ... @@ -191,7 +191,7 @@
191 191  |Download files from own Project Green Room folder|(% style="text-align:center" %)☑️ Allowed|(% style="text-align:center" %)☑️ Allowed|(% style="text-align:center" %)☑️ Allowed
192 192  |Download files from any Project Green Room folder|(% style="text-align:center" %)☑️ Allowed| |
193 193  |Request file copy from Green Room to Core|(% style="text-align:center" %)☑️ Allowed|(% style="text-align:center" %)☑️ Allowed| |
194 -|Copy files from Green Room to Core|(% style="text-align:center" %)☑️ Allowed| |
190 +|Copy files from Green Room to Core|(% style="text-align:center" %)☑️ Allowed|(% style="text-align:center" %)☑️ Allowed|
195 195  |(% style="background-color:#dcdcdc; text-align:center" %) **Activity** |(% colspan="3" style="background-color:#dcdcdc; text-align:center" %)**Core Room File Operations**
196 196  | |(% 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**
197 197  |Access own files in Project Core|(% style="text-align:center" %)☑️ Allowed|(% style="text-align:center" %)☑️ Allowed|
... ... @@ -215,6 +215,7 @@
215 215  |Access Superset|(% style="text-align:center" %)☑️ Allowed|(% style="text-align:center" %)☑️ Allowed|
216 216  |Access XWiki|(% style="text-align:center" %)☑️ Allowed|(% style="text-align:center" %)☑️ Allowed|(% style="text-align:center" %)☑️ Allowed
217 217  
214 +
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.
219 219  
220 220  == Viewing Project Member Profiles and Account Activities ==
... ... @@ -267,10 +267,6 @@
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  
270 -== Superset ==
271 -
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.
273 -
274 274  == XWiki ==
275 275  
276 276  After XWiki is deployed for the Project, members can click **XWiki** in the Workspace icon group to launch the application and be logged in seamlessly with single sign-on. See //Using XWiki// for more details on how to use the application in the platform.
... ... @@ -325,13 +325,20 @@
325 325  
326 326  1. Launch your Project and click on the Project **Settings **icon.
327 327  1. Select the **File Attributes** tab and locate an existing template.
328 -1. Click an available action:
329 -1*. **Rename**: When an Attribute template is renamed, all Files annotated with the template will show the new template name. Click **Save**, or **Cancel **to exit without making the change.
330 -1*. **Delete**: An Attribute template can only be deleted if it has not yet been used to annotate any files.
331 -1*. **Export**: Click to download the Attributes template as a JSON file.
332 -1*. **Add Attribute**: Attributes denoted as Optional can be added to the template, as described above in step 4 of the section //Creating a File Attribute Template//. Click the **checkmark **to save each addition.
333 -1**. Attributes denoted as Mandatory cannot be added.
334 -1**. Existing attributes cannot be edited or removed.
321 +1. (((
322 +Click an available action:
323 +
324 +1. **Rename**: When an Attribute template is renamed, all Files annotated with the template will show the new template name. Click **Save**, or **Cancel **to exit without making the change.
325 +1. **Delete**: An Attribute template can only be deleted if it has not yet been used to annotate any files.
326 +1. **Export**: Click to download the Attributes template as a JSON file.
327 +1.
328 +
329 +**Add Attribute**: Attributes denoted as Optional can be added to the template, as described above in step 4 of the section //Creating a File Attribute Template//. Click the **checkmark **to save each addition.
330 +
331 +1.
332 +1*. Attributes denoted as Mandatory cannot be added.
333 +1*. Existing attributes cannot be edited or removed.
334 +)))
335 335  1. The changes will be effective for any new File Attribute annotations.
336 336  
337 337  == Importing File Attribute Templates ==
... ... @@ -380,19 +380,10 @@
380 380  {"attributes":[{"name":"Group","options":["A","B","C","D"],"type":"multiple_choice","optional":true},{"name":"FaveMeal","options":["breakfast","lunch","dinner"],"type":"multiple_choice","optional":false},{"name":"FaveFruit","options":["apples","oranges","strawberries","bananas","other"],"type":"multiple_choice","optional":true},{"name":"OtherFaveFruit","type":"text","optional":true}]}
381 381  {{/code}}
382 382  
383 -= Deleting and Archiving Projects =
384 384  
385 -Please contact a Platform Administrator if you need to delete or archive your Project.
386 386  
387 387  
388 388  
389 -----
390 390  
391 -Copyright © 2023 [[Indoc Systems>>url:https://www.indocsystems.com]].
392 392  
393 -HealthDataCloud is powered by Pilot technology, a product of [[Indoc Systems>>url:https://www.indocsystems.com]].
394 -
395 -
396 -
397 -
398 398