About Synapse
...
| Expand | ||
|---|---|---|
| ||
Our Discussion Forum is a great place to reach out to the broader Synapse community to find others that may be interested in a collaboration. Depending on your plan level [link to offerings page](Synapse Offerings), you may have access to our help desk. |
| Expand | ||
|---|---|---|
| ||
The Terms and Conditions of Use fully describes the governance terms and conditions of Synapse. In order to register on Synapse, you must review and agree to the terms of the Synapse Awareness and Ethics Pledge. For more information, see /wiki/spaces/DOCS/pages/2004255211 Synapse Governance. |
| Expand | ||
|---|---|---|
| ||
Yes, Synapse is released under the Apache 2.0 License The source code is available on GitHub. Synapse is also offered free of charge as a hosted Software as a Service (SaaS) at https://www.synapse.org/. |
...
| Expand | ||
|---|---|---|
| ||
No, accounts and projects as of March 4, 2024 are grandfathered with their current will continue under the terms of their previous agreement with Sage. |
| Expand | ||
|---|---|---|
| ||
You can mint DOIs for projects and files uploaded to Synapse, extremely useful for citing data. Learn More |
| Expand | ||
|---|---|---|
| ||
These are the general storage limitations for each plan: up to 100GB for Basic Plans Hosting Plan and up to 500GB for the Self-Managed Plans. You may pay for additional storage if needed. Please see our Sage Offerings page [LINK] for more information. There are no data limits if you use Custom Storagein your own cloud bucket, and depending on the dataset uploaded, storage may be sponsored by an existing project. Contact us to learn more. |
| Expand | ||
|---|---|---|
| ||
You may create a User Project (or Workspace) where you have administrative control over who is granted access to the workspace. However, you cannot implement specific User Content restrictions for your User Content under a Basic Plan. You must have a Self-Managed Plan or Data Coordination Plan to implement such User Content restrictions. |
| Expand | ||
|---|---|---|
| ||
As a non-profit organization, Sage strives to keep our services accessible and affordable for all users. Maintaining a reliable and secure cloud storage infrastructure comes with significant costs, particularly when it comes to data egress. These costs can quickly add up, especially as the volume of data downloaded increases. To address this challenge, we implemented measures to monitor and control data downloads. By setting reasonable limits on data egress, we can manage our costs and ensure the long-term viability of our platform for the benefit of all users. In general, we advise to store and process user content in the cloud. Beyond cost efficiency, this provides greater data security, improved accessibility, faster insights, and better governance controls. There may be exceptions to these standard egress limits under the following circumstances:
|
| Expand | ||
|---|---|---|
| ||
Sage offers integrations with multiple cloud compute environments for customized Data Coordination Plans. Synapse is open source with standard interfaces and programming models <TBD Link to docs>(see API Clients and Documentation) |
| Expand | ||
|---|---|---|
| ||
You can manually add or remove Synapse users to your project spaces in the Basic Plan. In the Self-Managed Plan, Sage can set up User Content restrictions and require accessors to record their agreement to comply with such restrictions through a clickwrap agreement prior to accessing the User Content. For the Data Coordination Center Plan, we offer a complete data access committee service, either managed by you or by Sage to review/administer requests to controlled-access data. |
...
| Expand | ||
|---|---|---|
| ||
“Deidentified Data” refers to Personal Data from which all directly identifiable elements |
...