Open dustymc opened 1 month ago
Chat with @mkoo
Option 1: Upload media
New Option 4:
elaborate on Large Batch Uploads
FYI at MSB workflows have for a long time involved students being able to load media using the UI file upload. This has worked well, but now they are running into file size limits for files of the same size that previously caused no problems. Shifting to media batch uploads could mean major changes to workflows and shift more burden to collections staff. ? @AdrienneRaniszewski @DerekSikes
Downsizing images to <1MB is not difficult (I use the built in Mac 'Preview' app - open all the images & use the tools therein to resize & then export [not save] as jpg). Smaller images are likely beneficial to downstream users who want to access the images later. If they want the full size image they will likely contact someone to ask for it. I am ok with this.
So to clarify, if we wish to upload high quality images we shouldn't plan on using this tool? I am reading through the handbook right now, trying figure this out.
Some of the factors involved in the file size issues are local network variations but also security issues-- in either case, the CMS has little control over these so extremely hard to mitigate without yanking the interface completely. Obviously no one wants that. We can work on making TACC batch uploads easier to figure out perhaps?
Yes, please! I tried to figure out the batch upload, but I think I need explicit step by step instructions in one place..
I'm planning on adding multiple page PDF files containing scans of archival files. Even using the reduce-file-size save in Acrobat, those will likely be closer to 10MB for each file. I've used batch uploads with bulkloader tools for the file metadata and I can say I did not enjoy it, comparatively speaking. I'll definitely need those step-by-step instructions if the UI upload tool is not going to be able to handle those files anymore.
Help us understand your request (check below):
Describe what you're trying to do
See https://github.com/ArctosDB/arctos/issues/8172, https://github.com/ArctosDB/arctos/issues/8102
There are currently no limits on file upload imposed, but various things can time out or get wedged (some perhaps cryptically for the user, and none of this appears in error logs). I don't think expectations are in line with resources, and various things not working is clearly a frustrating experience for users.
Perhaps a conservative and documented cap on filesize (eg 1MB) for the single-file UI upload tool would provide a better user experience.
Note that there are no limitations on actual filesizes; the SCP ("bulk upload") option will readily deal with multi-terabyte files.