[EXTDAM-169] [Bynder] Make the status column filterable & [Bynder & S3] update config parameters Created: 14/Oct/20  Updated: 03/Dec/20  Resolved: 04/Nov/20

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

Type: Improvement Priority: Neutral
Reporter: Rabie Hayoun Assignee: Rabie Hayoun
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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
Epic Link: DAM Phase 2
Sprint: Add-Ons 49, Add-Ons 50
Story Points: 3

 Description   

AC

  • Add Filtering to the Status Column

Also addressed in this improvement are the following configuration parameters:

  • Bynder --> PageSize(default value: 100): maximum number of elements per request from magnolia to bynder
  • Bynder -->  bynderMaxNumberPerRequest (default value: 1000): maximum number of elements that bynder will return if you specify a limit (page size number) greater than 1000
  • S3 --> maximum value allowed by S3 is 1000


 Comments   
Comment by Rabie Hayoun [ 04/Nov/20 ]

we have added 2 configuration parameters for bynder as part of this ticket:

  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
Generated at Mon Feb 12 01:52:34 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.