You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Migrated from Word to GH issue for easier tracking
These are loosely in order of priority determined by @llchristopherson , however, you can and should reshuffle their priority based on feasibility, @mjstealey .
Rename some of the roles:
Change "Project PI" to "Project PIs and Co-PIs" Change "Project PI" to "Co-PI"
Change "Project PI Admin" to "Project Management" Change "Project PI Admin" to "Lead PI"
Change "Project Member" to "Project Staff"
All other roles keep their names as is.
Alter User Privileges as shown in the table below
First four cells are either major revisions or new features, and are lower priority than all the other stuff.
X = is true now, has this privilege now.
Add = not currently a privilege, please add.
Remove = has this privilege currently, please remove.
Check when completed
Task
Proj Mgmt
PI & Co-PI
NS Admin
Enroll in NS (Start a project)
Add
Approve enrollment
Add
Add a project in NS
Add
X – via CoM ^
Add staff to a project
Add *
Add *
X – via CoM ^
Edit project metadata
X
X
Associate data/infrastructure with a project
X
X
View a list of projects you are associated with
X
X
X
Make attestations per project
X
X
X
See the Datasets tab and the datasets you are currently using
X
X
X
See the Datasets tab and a list of all datasets for browsing
X
Add
X
See the Templates tab
Remove
X
See the Infrastructure tab and all infrastructure
X
Add
X
See the Infrastructure tab and the infrastructure you are currently using
X
X
X
* The PI (Lead PI or Co-PI) should only be able to add their own staff from their own institution. ^ You are currently working to change these functions so they are not done through CoManage.
Data Provider Functionality
The DP should have a way to view his datasets and associated projects. He should be able to mark datasets as "off" (i.e., not available, invisible, something so that it doesn't appear to others that the dataset is available to them, says "no" in some way). This should be doable for a single project or all projects.
Please put Templates before Datasets in the navigation bar since the DP will need to interact with that before the Datasets tab. So in other words, Templates should be to the left of Datasets.
Lead PI and Co-PI Dataset and Infrastructure Browsing Ability
Both PI roles should be able to see a list of available infrastructure on the Infrastructure tab. This should be sorted or presented in some way so the infrastructure s/he is currently using is distinct from the infrastructure s/he is not using.
Both PI roles should be able to see a list of all datasets in NS (for browsing/shopping purposes). As with Infrastructure, this should be sorted or presented in some way so the datasets s/he is currently using are distinct from the ones s/he is not.
Institutional Governance Functionality
IGs should be able to unassign themselves from a project. Currently they can't.
An IG should have a way to distinguish between the projects he is assigned to so he doesn't have to page through them all or remember their names to find the ones that are his (in the eventuality that he might encounter a long list). Perhaps projects can be listed in 2 sections on the page: a section for the projects he is assigned to and a section for all the others. The ones he is assigned to should probably appear first.
Infrastructure Provider and Institutional Governance Functionality
IP and IG might should see a list of all datasets in the Datasets tab.
IP and IG might should see a list of all infrastructure in the Infrastructure tab.
General Notes
With all lists of things, the items that the person is currently using should appear first. The items he is not using should appear after. This can be in whatever way @mjstealey and @yaxue1123 want (e.g., tabs, sections on the page, etc.)
The text was updated successfully, but these errors were encountered:
Migrated from Word to GH issue for easier tracking
These are loosely in order of priority determined by @llchristopherson , however, you can and should reshuffle their priority based on feasibility, @mjstealey .
Rename some of the roles:
Change "Project PI" to "Co-PI"Change "Project PI Admin" to "Lead PI"Alter User Privileges as shown in the table below
First four cells are either major revisions or new features, and are lower priority than all the other stuff.
^
*
*
^
*
The PI (Lead PI or Co-PI) should only be able to add their own staff from their own institution.^
You are currently working to change these functions so they are not done through CoManage.Data Provider Functionality
The DP should have a way to view his datasets and associated projects. He should be able to mark datasets as "off" (i.e., not available, invisible, something so that it doesn't appear to others that the dataset is available to them, says "no" in some way). This should be doable for a single project or all projects.
Please put Templates before Datasets in the navigation bar since the DP will need to interact with that before the Datasets tab. So in other words, Templates should be to the left of Datasets.
Lead PI and Co-PI Dataset and Infrastructure Browsing Ability
Both PI roles should be able to see a list of available infrastructure on the Infrastructure tab. This should be sorted or presented in some way so the infrastructure s/he is currently using is distinct from the infrastructure s/he is not using.
Both PI roles should be able to see a list of all datasets in NS (for browsing/shopping purposes). As with Infrastructure, this should be sorted or presented in some way so the datasets s/he is currently using are distinct from the ones s/he is not.
Institutional Governance Functionality
IGs should be able to unassign themselves from a project. Currently they can't.
An IG should have a way to distinguish between the projects he is assigned to so he doesn't have to page through them all or remember their names to find the ones that are his (in the eventuality that he might encounter a long list). Perhaps projects can be listed in 2 sections on the page: a section for the projects he is assigned to and a section for all the others. The ones he is assigned to should probably appear first.
Infrastructure Provider and Institutional Governance Functionality
General Notes
With all lists of things, the items that the person is currently using should appear first. The items he is not using should appear after. This can be in whatever way @mjstealey and @yaxue1123 want (e.g., tabs, sections on the page, etc.)
The text was updated successfully, but these errors were encountered: