[EXTDAM-201] DOC: pageSize (S3 and Bynder) and bynderMaxNumberPerRequest props Created: 24/Nov/20  Updated: 02/Dec/20  Resolved: 02/Dec/20

Status: Closed
Project: External DAMs
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Julie Legendre Assignee: Julie Legendre
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File 2020-11-24_11-47-24.png    
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Sprint: Add-Ons 52
Story Points: 0.5

 Description   

Hide block exists on module page just before "Usage" (see screenshot attached).

Needs clarification:

  • Why would a user want to change the defaults?
  • Same purpose for both S3 and Bynder? Why different defaults?
  • What about the cache?

and reviewed.

 

Bynder work corresponds to EXTDAM-169 - not sure what release version it will be in.

Bynder

  1. pageSize(default value: 100): maximum number of elements per request from magnolia to bynder.
  2. bynderMaxNumberPerRequest (default value: 1000): maximum number of elements that bynder will return if you specify a limit (page size number) greater than 1000. This number is as per their documentation: https://bynder.docs.apiary.io/#reference/oauth-1.0a/retrieve-assets, limit parameter

S3

pageSize: It’s the number of objects we request to S3 in a single API call. All the assets would be shown regardless of the pageSize. Notice S3 only allows 1000 at most(default), minimum is 100

 



 Comments   
Comment by Julie Legendre [ 01/Dec/20 ]

asked for review in slack

Generated at Mon Feb 12 01:52:53 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.