RDL-Share - Data Transfer Service
Description:
Secure file transfer service, managed by the UC Library Technology and Digital Experience group that is provided at no cost to the users of the UC San Diego community.
Link to application: https://rdl-share.ucsd.edu Link to Library Help page: https://libraries.ucsd.edu/research-and-collections/data-curation/rdl-share.html For additional assistance contact: rcd-support@ucsd.edu Blog post from March 2018: https://knit.ucsd.edu/researchit/2018/03/28/rdl-share-large-file-transfer-service/?_ga=2.114945487.972052912.1591644551-686450032.1516303595 | |
Collaborate with others at UC San Diego, or with individuals at other institutions Several ways to use: Compose a secure message to send files | |
Easy-to-use email-like interface Files are encrypted in transit File-size limit is 500 GB per message No limit on number of messages Ability to enable 2-factor authentication File types NOT permitted: exe, vbs, pif, scr, bat, cmd, com, cpl | |
No account setup necessary - log in with AD or Business Systems credentials Determine the means of expiration in one of two ways (up to 6 months out): Calendar date Determine the authentication restrictions to recipients: Authentication required OR not required Determine access restrictions to recipients: Recipients only | |
Zip files before uploading. Although not required, zipping can substantially reduce upload time, which depends on both the total size of files and the number of files being uploaded. For added security, encrypt files before sending them (use a compression utility such as 7zip), then share the key with the recipient in a separate communication. If possible, connect to an Ethernet cable to transfer the files. Data transfer on a hard-wired connection is much faster than with Wifi. If possible, upload files directly from your local machine, rather than from a networked drive which could slow down the transfer considerably. Make sure the box next to "Send a copy to myself" (when composing) is checked. During transfer, a checksum is performed on the file(s) to ensure that the file sent matches the file uploaded. If a file is missing a checksum number in the message transmitted to the recipient, then the file was not processed correctly. |
Last updated: 6/12/20