Feature Request: ability to disable traditional uploads

Overview of the Feature Request

Some installations use S3- or S3-compatible datastores as their sole storage, and available themselves of direct upload and download functionality. More advanced users always seem to find the traditional upload endpoints ( /add, /addFiles ) in the guides, and so we see the web application nodes bogged down processing traditional uploads..

The simplest thing to do, as suggested by @qqmyers might be to re-organize or re-label the guides to suggest direct upload-capable external tools and endpoints over traditional, and I'm therefore assigning this the DCM2025hackathon label.

If that doesn't work out, another idea might be a database setting to disable traditonal upload endpoints, which will allow installation administrators to insist on direct uploads, Globus, etc.

What kind of user is the feature intended for?

Sysadmins

What inspired the request?

End users seem to find the traditional upload API endpoints first.

Any open or closed issues related to this feature request?

I didn't find any.

Are you thinking about creating a pull request for this feature?

That would be nice, particularly with the docs during the DCM2025 hackathon. If not... maybe?

Review the guides that currently surface the /add and /addFiles endpoints alongside the direct-upload guidance. First determine whether the intended deliverable is documentation reorganization or a database setting to disable traditional uploads; completion requires one approach to be chosen and its behavior or guidance to be verified.