Best Practices:

• Consider using a repository or cloud service that helps track data versions. For example, Amazon S3 and Dropbox (see other examples below) track data versions. Consider the level of HIPPA compliance for each repository and whether it meets your needs.
• Identify ways to explore data without downloading it (either open summaries, or platforms that support authentication and querying of data) Cloud providers will keep snapshots of version
• Work with cloud vendors to see if they can host valuable data for free 
• Consider whether you really need backups given the durability of the Cloud storage (i.e., many cloud providers have very robust redundant storage already, so data may be sufficiently protected through permissions and versioning)
• Make sure any policies on copies will allow necessary computing (permanent vs transient copies).

Things to Avoid:

• Do not store unnecessary copies.

Value Set Definitions: 

• 1: Single copy + backups, no downloading
• >1 copy: Data stored in cloud but must maintain single version of record for legal, ethical, or technical reasons
• >1 copy+: Copies can be made and distribution rights can be granted

Value of Use Case Example:

>1 copy+ - Jordan is planning to share the data through NDA or another repository, but they want the data to be reusable (i.e., interoperable) by other platforms.

Discussion of Use Case:

Jordan will benefit from planning prospectively for the cost of sharing data and providing multiple copies both through the NDA and other repositories, and will need to ensure sufficient resources.