This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
xnat [2018/03/03 01:05] mgstauff |
xnat [2018/03/19 21:21] (current) mgstauff [Projects] |
||
---|---|---|---|
Line 32: | Line 32: | ||
XNAT organizes data by Project. Each Project has private control of its data and a user must be granted access to a Project to view or edit data. | XNAT organizes data by Project. Each Project has private control of its data and a user must be granted access to a Project to view or edit data. | ||
+ | ==== User Roles and Permissions ==== | ||
+ | |||
+ | XNAT users can have different permissions within a Project: | ||
+ | |||
+ | **Project Owners**: If you define additional project owners, they will have all of the permissions on your project that you do. They can read, insert, modify, and delete anything (and everything) associated with your project. They can also add additional users to your project and modify the data types associated with your project. | ||
+ | |||
+ | **Project Members**: Members have the ability to manage the data in your project. They can read, insert, and modify subjects and experiments in your project. They cannot modify the project users and data types. | ||
+ | |||
+ | **Project Collaborators**: | ||
+ | |||
+ | [[https:// | ||
==== Uploading Data ==== | ==== Uploading Data ==== | ||
Line 53: | Line 64: | ||
See below for handling anonymization. | See below for handling anonymization. | ||
- | === Pushing Data from PACS/Sectre | + | === Pushing Data from PACS/Sectra |
- | XNAT can receive data directly from PACS/Sectre | + | XNAT can receive data directly from PACS/Sectra, from clinical scanners, |
== Prearchive or Archive as Final Destination == | == Prearchive or Archive as Final Destination == | ||
- | Data can end up in either Archive or Prearchive at the completion of the upload/push process from a scanner or PACS/Sectre. This depends on project-specific settings. Namely, within a project' | + | Data can end up in either Archive or Prearchive at the completion of the upload/push process from a scanner or PACS/Sectra. This depends on project-specific settings. Namely, within a project' |
__We recommend__ setting this option to leave data in Prearchive, so your group knows it needs to be reviewed and probably have PHI removed before moving to Archive. The setting' | __We recommend__ setting this option to leave data in Prearchive, so your group knows it needs to be reviewed and probably have PHI removed before moving to Archive. The setting' | ||
Line 89: | Line 100: | ||
__Note on Accession Number__: XNAT generates its own Accession Numbers ('Expt ID') in the format '' | __Note on Accession Number__: XNAT generates its own Accession Numbers ('Expt ID') in the format '' | ||
- | The above ' | + | The above ' |
__It's up to the user to change these 'NA Fields' | __It's up to the user to change these 'NA Fields' | ||
Line 95: | Line 106: | ||
== Modifying NA Fields on the Research Scanner == | == Modifying NA Fields on the Research Scanner == | ||
- | When pushing data from the research scanner (which allows the user to modify the DICOM ' | + | When pushing data from the research scanner (which allows the user to modify the DICOM ' |
== Modifying NA Fields During Move to Archive == | == Modifying NA Fields During Move to Archive == | ||
If the user moves data manually from Prearchive to Archive (recommended), | If the user moves data manually from Prearchive to Archive (recommended), | ||
+ | |||
1) ' | 1) ' | ||
+ | |||
2) ' | 2) ' | ||