From 1618e35ed4ec54a86cbc7aeae4e3c9cd73834724 Mon Sep 17 00:00:00 2001 From: bram-atmire Date: Sat, 12 Sep 2026 11:40:57 +0200 Subject: [PATCH] Document the maxSize attribute of submission upload configurations Name the attribute as the API returns it (maxSize, not max-size) and describe it as the configured limit capped by the REST server's multipart limit, absent when no limit applies, so clients can check a file before sending any data. Relates to DSpace/dspace-angular#2848. Claude-Session: https://claude.ai/code/session_01HtPYmqfFzg7fmZgovGWP5A --- submissionuploads.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/submissionuploads.md b/submissionuploads.md index ee600eb6..030c4c01 100644 --- a/submissionuploads.md +++ b/submissionuploads.md @@ -21,7 +21,7 @@ Provide detailed information about a specific input-form. The JSON response docu { "id": "default", "required": true, - "max-size": 536870912, + "maxSize": 536870912, "accessConditionOptions": [ { "name": "openaccess" @@ -50,6 +50,8 @@ The attributes of the objects in the accessConditionOptions arrays are as follow A null value for the accessConditionOptions attribute means that the upload step doesn't allow the user to set a policy for the file. The file will get only the policies inherited from the collection. +The *maxSize* attribute is the largest file, in bytes, that this upload step accepts: the `maxSize` configured for the upload configuration (or `upload.max`), capped by the REST server's multipart limit (`spring.servlet.multipart.max-file-size`). It is absent when no limit applies. Clients should check a file against it before sending any data; the backend also rejects a larger file with the section error `error.validation.filesize`. + Exposed links: * metadata: it is a link to the submission-form to use for the files metadata