[MGNLDAM-1017] Endpoint for uploading assets Created: 13/Apr/22  Updated: 19/Apr/22  Resolved: 15/Apr/22

Status: Closed
Project: Magnolia DAM Module
Component/s: None
Affects Version/s: 3.0.14
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Richard Gange Assignee: Unassigned
Resolution: Won't Do Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLREST-359 Cannot put nodes with colons in the name Closed
supersession
is superseded by MGNLDAM-1018 Upload asset command Open
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Documentation update required:
Yes

 Description   

In the docs we have a tutorial for uploading assets via rest. This approach has a few problems.

  • It takes multiple calls to upload a single asset.
  • It's hard to calculate the size of the asset. If you don't send the size in the request (missing from the tutorial DOCU-2430) then using the asset becomes a problem. Size is required and it would be better if it would be calculated on the server like we do with the UI upload.
  • We made changes to our rest modules to restrict the use of certain characters in a node name. See MGNLREST-343 which causes MGNLREST-359. Since Magnolia 6.2.16 and rest 2.2.11 it's not possible to PUT a "jcr:content" node to store the binary data.

One solution is we provide the endpoint so that the upload can be made in one call, it can calculate the size and create the subnode. All this would make uploading assets via rest easier for the users.


Generated at Mon Feb 12 05:05:33 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.