Excerpt |
---|
Many services allow sharing of files. Look here for guidance on which to use, and why. |
See also
Standard of practice
- Never have a unique, valuable file on a single storage or device.
- That is, make sure you have copies accessible elsewhere!!
Options:
- Back it up, of-site and with versioning. (Traditional desktop model)
- Store it elsewhere, and mount it so files easily accessed. (Typically a file server does this)
- Sync it elsewhere, with versioning. Access files via web browser (Typically cloud services do this)
...
Service | Files one expects to see there | Sharing characterizations | Backup-related comments Q no answered: What if account is hacked? | Versioning Providing access to prior versin os existing files, and last version of deleted files. | Enablers and barriers to use, and related considerations. | Cost ("Free" means free to departments/ users) | Notes | Comparison to other services |
---|---|---|---|---|---|---|---|---|
Staff person's work computer. (Cornell owned desktop or laptop.) | Work, and sometimes personal files. | No sharing directly.
| No. Backup encouraged if files deemed unique and valuable (fee-based, if via EZ-Backup). | No. |
| Sunk cost of provisioning a system. Fee-based service, if backups are being done. | Historical default. | |
A&S's file storage service | Work files. Best for static sharing arrangements. | ChemIT configures permissions, including sharing.
Sharing with those with CU NetIDs or publicly | Yes. Backed up off-site (EZ-backup) for disaster recovery purposes of the entire service. | ?Any file-level versioning? |
| Free | For departmental administration only. | |
CIT's SFS (file storage service) | The funder gets to specify files appropriate. | ChemIT structures permissions, including sharing.
Sharing with those with CU NetIDs or publicly | Yes. Backed up off-site (EZ-backup) for disaster recovery purposes of the entire service. | Yes, optionally. (Usually turned on!) |
| Fee-based service. Reasonable cost for up to 1-2TB of data. | University controlled & sanctioned. | |
Box.com | Work or personal files. | User controls sharing to others with CU NetIDs or publicly, so good for ad hoc sharing (usually beats emailing documents)
| Yes. Backed up off-site (CU contract) for disaster recovery purposes of the entire service. | Yes |
| Free | Limitations on single files size, but that's not a problem for most people. Limitations on path name length, file types, file names, etc. | |
MS OneDrive | Work or personal files. | User controls sharing to others with CU NetIDs or publicly, so good for ad hoc sharing (usually beats emailing documents)
| Yes. Backed up off-site (CU contract) for disaster recovery purposes of the entire service. | Yes. |
| Free | Limitations on single files size, but that's not a problem for most people. | |
MS-provisioned (cloud) MS SharePoint | Work files. | User controls sharing to others with CU NetIDs or publicly, so good for ad hoc sharing (usually beats emailing documents)
| Yes. Backed up off-site (CU contract) for disaster recovery purposes of the entire service. | ?Yes? |
| Free | Admin, tech, and training investments are required to enable effective use and maintenance of this service. | |
CU-provisioned (on-premise) MS SharePoint | Work files. | User controls sharing to others with CU NetIDs or publicly, so good for ad hoc sharing (usually beats emailing documents)
| Yes. Backed up off-site (EZ-Backup, usually) for disaster recovery purposes of the entire service. | ?Yes? |
| Free | Admin, tech, and training investments are required to enable effective use and maintenance of this service. | |
Cornell's Dropbox | Temporary storage of work files, for the purposes of sharing. | User controls sharing to others with anyone, so good for ad hoc sharing (usually beats emailing documents)
| ? (N/A really since just holds, temporarily, copies of files.) | No. (N/A) | Temporary sharing with anyone. CU-sanctioned tool for transferring sensitive university data. | Free | For temporary use of files. Limitations on single files size, but that's not a problem for most people. | |
Non-Cornell file sync services (ex. Dropbox, Google Drive, iDrive, etc.) | Personal files. Regarding work files: Backups encouraged if used for work files, and there may be other issues, especially regarding risk management. | User controls sharing to anyone with service account or publicly, so good for ad hoc sharing (usually beats emailing documents) | Yes. We hope! (No CU contract to enforce this.) | Yes. |
| Free and fee-based. | No institutional oversight, restoration, access, or path to service escalation. Limitations on single files size, but that's not a problem for most people. |
...