-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Resolve wording conflicts in data-sharing
- Loading branch information
Showing
6 changed files
with
60 additions
and
68 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -4,61 +4,54 @@ import Image from 'next/image' | |
|
||
# Data Access | ||
|
||
Data access for Gray Foundation corresponds to the general [data access types described for the Synapse platform](https://help.synapse.org/docs/Data-Access-Types.2014904611.html). | ||
The data access for Gray Foundation aligns with the general data access types described for the Synapse platform. You can find more details about these access types [here](https://help.synapse.org/docs/Data-Access-Types.2014904611.html). | ||
|
||
## Data Access Tags in the Portal | ||
## Data Access Tags in the Portal | ||
|
||
<Callout type="info" emoji="ℹ️"> | ||
This is a future visual labeling scheme to help represent access in a more user-friendly manner in the portal. | ||
This is an upcoming visual labeling system designed to represent access in a more user-friendly manner within the portal. | ||
</Callout> | ||
|
||
<Steps> | ||
### Phase 1 Datasets | ||
|
||
##### "PRIVATE" | ||
<Image src="/badge_phase1_PRIVATE.svg" alt="private data access" width={160} height={30} /> | ||
Phase 1 datasets will likely not appear in the portal at all. | ||
If they do, the pink "PRIVATE" tag will indicate that this data exists on Synapse, but is likely still under compilation/analysis, and there is no interest in sharing it at the moment. Do not contact the team regarding the data. | ||
Phase 1 datasets will most likely not be visible in the portal. If they do appear, the pink "PRIVATE" tag will indicate that the data exists on Synapse but is still undergoing compilation/analysis. At the moment, there is no intention to share this data, so please refrain from contacting the team regarding its availability. | ||
|
||
### Phase 2 Datasets | ||
|
||
##### "COLLABORATIVE ONLY" | ||
<Image src="/badge_phase2_COLLAB.svg" alt="collaborative data access" width={270} height={30} /> | ||
Phase 2 datasets MAY appear in the portal, but will be tagged with "COLLABORATIVE ACCESS ONLY". | ||
Researchers interested in collaboration **will have to request access through contacting the Team PI**. | ||
- Data is private and downloable only through the individuals or teams explicitly granted with those permissions. | ||
- Admins (PIs and Data Leads) for the team's repository can grant view or download access by adding individuals or teams to the folder or project. This allows data to be shared for collaboration without moving the data to Phase 3. | ||
- In conversational context, this data might also be referred to as "under embargo". | ||
Phase 2 datasets may be visible in the portal but will be labeled as "COLLABORATIVE ACCESS ONLY". Researchers interested in collaboration will need to request access by contacting the Team PI. | ||
- Data is private and can only be downloaded by individuals or teams explicitly granted permission. | ||
- Admins (PIs and Data Leads) for the team's repository can grant view or download access by adding individuals or teams to the folder or project. This allows data to be shared for collaboration without moving it to Phase 3. | ||
- In conversation, this data may also be referred to as being "under embargo". | ||
|
||
### Phase 3 Datasets | ||
### Phase 3 Datasets | ||
|
||
Phase 3 datasets are often data released with or after publication. However, there might still be conditions placed on access. | ||
Within Phase 3, data has several access classes: | ||
Phase 3 datasets often consist of data released concurrently with or after publication, although certain access conditions may still apply. Within Phase 3, data is classified into several access categories: | ||
|
||
##### "CONTROLLED ACCESS" | ||
<Image src="/badge_phase3_CONTROLLED.svg" alt="controlled data access" width={200} height={30} /> | ||
- Registered Synapse users can download this data as long as they fulfill additional actions such as accepting Conditions of Use, submitting a statement, or getting an approval from governance. | ||
- Since these controls are implemented through a different data access layer, for _certain_ controls, once they are applied, even individuals on the Access Control List with download permissions will need to complete the required action to download data. | ||
- This is usually applicable for raw sequencing data. | ||
- Registered Synapse users can download this data after fulfilling additional requirements such as accepting Conditions of Use, submitting a statement, or obtaining approval from governance. | ||
- For certain controls, even individuals on the Access Control List with download permissions will need to complete the required action to download data, as these controls are implemented through a different data access layer. | ||
- This typically applies to raw sequencing data. | ||
|
||
##### "PUBLIC" | ||
<Image src="/badge_phase3_PUBLIC.svg" alt="public data access" width={140} height={30} /> | ||
- Anyone on the web can view the data, but only registered Synapse users can download this data. Data can be downloaded without any restrictions or additional steps required. | ||
- This is usually applicable for processed data such as summarized gene expression and cell and tissue images. | ||
- The data can be viewed by anyone on the web, but only registered Synapse users can download it. There are no restrictions or additional steps required for downloading. | ||
- This usually applies to processed data such as summarized gene expression and cell and tissue images. | ||
|
||
##### "OPEN" | ||
<Image src="/badge_phase3_OPEN.svg" alt="open data access" width={130} height={30} /> | ||
- Anyone on the web can view and download this data, no account needed. | ||
- This is usually applicable for metadata. | ||
- Anyone on the web can view and download this data without requiring an account. | ||
- This usually applies to metadata. | ||
|
||
</Steps> | ||
|
||
For more information, reach out to our governance analysis team at [email protected]. | ||
For more information, please refer to the policies on our [Data Access](/help/data-access) page or contact our governance analysis team at [email protected]. | ||
|
||
### See Also | ||
|
||
For specific information regarding synapse governance - see https://help.synapse.org/docs/Synapse-Governance.2004255211.html | ||
|
||
|
||
|
||
|
||
For specific information regarding Synapse governance, please visit https://help.synapse.org/docs/Synapse-Governance.2004255211.html. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,6 @@ | ||
## Account Setup | ||
|
||
1. Please review the [account types here](https://help.synapse.org/docs/Synapse-User-Account-Types.2007072795.html). | ||
2. In most cases, you will need to be a **Certified User**, so make sure you complete that step. | ||
3. Once you have your account, let the DCC know so a team-specific invite can be sent. | ||
4. You must accept the invitation for a Team invite. This requires following an emailed link and accepting the invitation on a Synapse team page. | ||
1. Please familiarize yourself with the different [account types available](https://help.synapse.org/docs/Synapse-User-Account-Types.2007072795.html). | ||
2. In most cases, it is necessary to become a **Certified User** before proceeding. Make sure you complete this step. | ||
3. After creating your account, please inform the DCC so that a team-specific invitation can be sent to you. | ||
4. To join a team, you must accept the invitation by clicking on the link provided in the email and following the instructions on the Synapse team page. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters