Add Box file size limit, and how to handle files too large
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 24
- Forks
- 15
- Avg merge
- 10d 3h
- Merged PRs (30d)
- 1
Description
What would you like to see added?
At this page: https://docs.rc.uab.edu/data_management/alternate_storage/#box-storage
What is the maximum allowed file size?
Describe the actual value for our description (150 GB)
Add a link to this page: https://support.box.com/hc/en-us/articles/360043697314-Understand-the-Maximum-File-Size-You-Can-Upload-to-Box
What if I have a file that is too large?
To upload, you'll need to split the file into pieces no larger than 150 GB each. To retrieve the file, you'll run the process in reverse. Linux has built-in tools for this.
How do I upload a file that is too large?
- Archive and split (
tar | split) - Create a Box folder with the original file name (
rclone, crosslink) - Upload the split file parts within that folder (
rclone, crosslink)
How do I retrieve a split file?
- Download the Box folder containing the split parts (
rclone, crosslink) - Concatenate the split file parts and unarchive (
cat <folder>/* | tar)
What if my file is on LTS?
If you have a file on LTS that is too large for Box, you'll still need to split the file. Because LTS has no capability for processing, such as archiving and splitting, you'll first need to copy the file from LTS to Cheaha, then follow the instructions (section above, crosslink).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open the Box storage section at https://docs.rc.uab.edu/data_management/alternate_storage/ and review the existing guidance. Document the 150 GB limit, link the Box reference, and add the split, upload, retrieval, and LTS workflows with their referenced tools and commands. Done when the page clearly covers files over the limit and all links and instructions are usable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 85/100